http://bering-uclibc.zetam.org/index.php?title=Bering-uClibc_4.x_-_User_Guide_-_IPv4_Networking_-_Configure_802.1Q_VLANs&feed=atom&action=historyBering-uClibc 4.x - User Guide - IPv4 Networking - Configure 802.1Q VLANs - Revision history2024-03-28T22:58:39ZRevision history for this page on the wikiMediaWiki 1.26.0http://bering-uclibc.zetam.org/index.php?title=Bering-uClibc_4.x_-_User_Guide_-_IPv4_Networking_-_Configure_802.1Q_VLANs&diff=634&oldid=prevDavidmbrooke: Created2011-04-05T18:54:32Z<p>Created</p>
<p><b>New page</b></p><div>{| summary="Navigation header" width="100%"<br />
! colspan="3" align="center" | [[Bering-uClibc 4.x - User Guide - IPv4 Networking - Configure 802.1Q VLANs|IPv4 Networking - Configure 802.1Q VLANs]]<br />
|-<br />
| width="20%" align="left" | [[Bering-uClibc 4.x - User Guide - IPv4 Networking - Configure Dnsmasq|Prev]]<br />
! width="60%" align="center" | [[Bering-uClibc 4.x - User Guide]]<br />
| width="20%" align="right" | <br />
|}<br />
----<br />
<br />
<br />
==Objectives==<br />
IEEE 802.1Q defines a standard for VLAN tagging.<br />
If your network switch hardware supports VLANs but does not manage routing between VLANs a [[Bering-uClibc 4.x]] router can be used to do that.<br />
<br />
One option is to install multiple physical network connections from separate Network Interface Cards to separate switch ports, with each connection carrying the traffic for an individual VLAN.<br />
<br />
An alternative option is to configure one switch port for "tagged" traffic for several VLANs and to use a single physical connection to carry all of the traffic, subject to any bandwidth constraints imposed by using a single physical interface.<br />
<br />
==Packages==<br />
The <code class="filename">vlan.lrp</code> Package is required. This installs the <tt>/sbin/vconfig</tt> command and some VLAN-specific scripts in directories under <code class="filename">/etc/network/</code>.<br />
<br />
==Modules==<br />
The <code class="filename">8021q.ko</code> kernel Module is required.<br />
This is included as standard in [[Bering-uClibc 4.x]] - listed in <code class="filename">/etc/modules</code> and hence loaded at boot time.<br />
<br />
==Configuration==<br />
Configuration is quite simple. In file <code class="filename">/etc/network/interfaces</code> the default entry for interface <tt>eth1</tt> looks like this:<br />
auto eth1<br />
iface eth1 inet static<br />
address 192.168.1.254<br />
netmask 255.255.255.0<br />
broadcast 192.168.1.255<br />
<br />
To use tagged VLANs instead, replace those lines with something like the following:<br />
auto eth1.123<br />
iface eth1.123 inet static<br />
address 192.168.1.254<br />
netmask 255.255.255.0<br />
broadcast 192.168.1.255<br />
vlan_raw_device eth1<br />
<br />
Note in particular the following:<br />
* The interface is specified as <tt>eth1.123</tt>. The "<tt>123</tt>" is the VLAN ID.<br />
* The <tt>vlan_raw_device</tt> configuration entry specifies which physical or "raw" interface carries this traffic.<br />
<br />
Additional similar configuration blocks can be added to define additional VLANs on the same physical interface.<br />
<br />
If <tt>eth1</tt> is also carrying "untagged" traffic then the default entry for <tt>eth1</tt> (no suffix) should be retained.<br />
<br />
<br />
----<br />
{| summary="Navigation footer" width="100%"<br />
| width="40%" align="left" | [[Bering-uClibc 4.x - User Guide - IPv4 Networking - Configure Dnsmasq|Prev]]<br />
| width="20%" align="center" | [[Bering-uClibc 4.x - User Guide - IPv4 Networking|Up]]<br />
| width="40%" align="right" | <br />
|}<br />
<br />
[[Category:Bering-uClibc 4.x]]<br />
[[Category:User Guide]]</div>Davidmbrooke