Penguin
Diff: LinuxVlanNotes
EditPageHistoryDiffInfoLikePages

Differences between current version and revision by previous author of LinuxVlanNotes.

Other diffs: Previous Major Revision, Previous Revision, or view the Annotated Edit History

Newer page: version 6 Last edited on Tuesday, July 4, 2006 12:44:34 am by AristotlePagaltzis
Older page: version 4 Last edited on Sunday, July 2, 2006 10:43:33 pm by CraigBox Revert
@@ -1,40 +1,40 @@
-VLANs under linux are fairly trivial to set up. There are some vlan tools you' ll need ('apt -get install vlan' on a Debian based system)
+[VLAN]s under [Linux] are fairly trivial to set up. You’ ll need to make sure your switch is passing [VLAN] -tagged frames to you
  
-You' ll need to make sure your switch is passing vlan -tagged frames to you. 
+There are some [VLAN] tools you’ ll need – on a [Debian] -based system, <tt>apt-get install vlan</tt> will fix you up . Once you have the tools installed, you can add a [VLAN] to a physical interface with the <tt>vconfig</tt> command:  
  
-Once you have the tools installed, you can add a vlan to a physical interface with the vconfig command:  
+ <verbatim>  
+ vconfig add eth0 1234  
+ vconfig add eth0 2000  
+ </verbatim>  
  
-<verbatim >  
- vconfig add eth0 1234  
- vconfig add eth0 2000  
- </verbatim
+These commands will add two [VLAN]s, 1234 and 2000, to the physical <tt >eth0</tt> device, and create two new interfaces, <tt>eth0. 1234</tt> and <tt> eth0. 2000</tt >. These interfaces still need to be configured with ifconfig(8).  
  
-Will add two vlans, 1234 and 2000, to the physical eth0 device, and create two new interfaces, eth0 .1234 and eth0.2000. These interfaces still need to be configured with ifconfig
+Note that you’ll probably have to stop using the raw physical device. Just use the [VLAN] interfaces. 
  
-Note that you'll probably have to stop using the raw physical device, and just use the vlan interfaces.  
+!! [VLAN]s and [Debian]’s interfaces file  
  
-!! VLANs and Debian's interfaces file  
+[ Debian] has some fairly nice integration with the [VLAN] tools. You have a choice of methods to use:  
  
-Debian has some fairly nice integration with the vlan tools. You have a choice of methods to use
+* This one will work out which [Ethernet] device you are using based on the stub of the device name (don’t get it confused with an aliased [IP] address though!)
  
-This one will work out which ethernet device you are using based on the stub of the device name. Don't get it confused with an aliased ip address though!  
- <verbatim>  
-auto eth0.1234  
-iface eth0.1234 inet dhcp  
-</verbatim> 
+ <verbatim>  
+ auto eth0.1234  
+ iface eth0.1234 inet dhcp  
+ </verbatim> 
  
-This one renames the interface to something easier to read, but you need to specify which ethernet device you are using:  
-<verbatim>  
-auto vlan1234  
-iface vlan1234 inet dhcp  
- vlan-raw-device eth0  
-</verbatim>  
+* This one renames the interface to something easier to read, but you need to specify which [Ethernet] device you are using: 
  
-Both formats also have an option to have the vlan zero -padded to four digits, eg: eth0.1 or eth0.0001, vlan1 or vlan0001.  
+ <verbatim>  
+ auto vlan1234  
+ iface vlan1234 inet dhcp  
+ vlan-raw-device eth0  
+ </verbatim>  
  
-__Note:__ You cannot mix differing formats within the same machine (even using one form in <tt>interface </tt> and a different form from some other configuration system)  
+Both formats also have an option to have the [VLAN] interface name zero-padded to four digits, eg: <tt>eth0.1</tt> or <tt>eth0.0001</tt>, <tt>vlan1</tt> or <tt>vlan0001 </tt>.  
  
-Read the vlan-interfaces manpage for more information
+__Note:__ you cannot mix differing formats within the same machine (even using one form in <tt>interface</tt> and a different form from some other configuration system)
  
------  
-You can find this page, and many others like it, in CategoryNetworking!  
+Read the <tt>vlan -interfaces</tt> ManPage for more information.  
+  
+ ----  
+Part of CategoryNetworking