Man page or keyword search:   man All Sections 1 - General Commands 2 - System Calls 3 - Subroutines, Functions 4 - Special Files 5 - File Formats 6 - Games and Screensavers 7 - Macros and Conventions 8 - Maintenence Commands 9 - Kernel Interface New Commands Server 4.4BSD AIX Alpinelinux Archlinux Aros BSDOS BSDi Bifrost CentOS Cygwin Darwin Debian DigitalUNIX DragonFly ElementaryOS Fedora FreeBSD Gentoo GhostBSD HP-UX Haiku Hurd IRIX Inferno JazzOS Kali Knoppix LinuxMint MacOSX Mageia Mandriva Manjaro Minix MirBSD NeXTSTEP NetBSD OPENSTEP OSF1 OpenBSD OpenDarwin OpenIndiana OpenMandriva OpenServer OpenSuSE OpenVMS Oracle PC-BSD Peanut Pidora Plan9 QNX Raspbian RedHat Scientific Slackware SmartOS Solaris SuSE SunOS Syllable Tru64 UNIXv7 Ubuntu Ultrix UnixWare Xenix YellowDog aLinux   14857 pages apropos Keyword Search (all sections) Output format html ascii pdf view pdf save postscript

IFCFG-VLAN(5)		     Network configuration		 IFCFG-VLAN(5)

NAME
       ifcfg-vlan - virtual LAN interface configuration

SYNOPSIS
       /etc/sysconfig/network/ifcfg-vlan*

Virtual LANs (802.1q)
       To  setup  a vlan interface you need a configuration file that contains
       at least the mandatory

       ETHERDEVICE
	      variable with the real interface used for the virtual LAN.

       Further, it may contain the optional

       VLAN_ID
	      variable that specifies the VLAN ID.

       By default and when the VLAN_ID variable is not set, the number at  the
       end of the interface name is the VLAN ID.

       Preferably  the	interface  name	 and the configuration file follow the
       VLAN interface name schemes (types), that is either:
	      ifcfg-name.<VLAN-ID> (e.g. ifcfg-eth0.42)

	      or

	      ifcfg-vlan<VLAN-ID> (e.g. ifcfg-vlan42)

       The ifcfg-name.<VLAN-ID> scheme is default on Linux.  Note  also,  that
       the  ifcfg-vlan<VLAN-ID> scheme makes it impossible to use same VLAN-ID
       on more than one interface (e.g. ifcfg-eth0.42 and ifcfg-eth1.42).

       The VLAN-ID  can	 be  also  0-padded  (e.g.  ifcfg-vlan0042  or	ifcfg-
       eth0.0042).

       Also  in case of custom names, trailing digits are interpreted as VLAN-
       ID by default (e.g. ifcfg-dmz42). When VLAN_ID is set  in  the  config,
       the interface name can have any name (e.g. ifcfg-foobar).

       Note: The drawback of custom interface names and VLAN_ID usage is, that
       a rename of the interface is required and that they  violate  the  vlan
       name scheme.

       The real interface will be set UP automatically and doesn't need a con‐
       fig file in case of a physical interface. But  without  a  config  file
       YaST will consider this interface as unused, if will not follow hotplug
       events and you're unable to apply any settings,	e.g.  ETHTOOL_OPTIONS.
       To avoid these problems, it is strongly recommended to provide a config
       file with at least STARTMODE='auto' for the physical interface as well.

       The rest of the VLAN interface IP and routes configuration do not  dif‐
       fer  from  ordinary  interfaces.	 See also man ifcfg and man routes for
       details.

EXAMPLES
       Sets up eth0.3 vlan interface on top of eth0:

	      ifcfg-eth0.3
		 STARTMODE='auto'
		 ETHERDEVICE='eth0'
		 IPADDR='192.168.3.27/24'

       Sets up vlan3 vlan interface on top of eth0:

	      ifcfg-vlan3
		 STARTMODE='auto'
		 ETHERDEVICE='eth0'
		 IPADDR='192.168.3.27/24'

       Sets up lan1 vlan interface with ID 42 on top of eth0:

	      ifcfg-lan1
		 STARTMODE='auto'
		 ETHERDEVICE='eth0'
		 VLAN_ID='42'
		 IPADDR='192.168.3.27/24'

BUGS
       Please report bugs at <http://www.suse.de/feedback>

AUTHOR
       Christian Zoz <zoz@suse.de>
       Michal Svec <msvec@suse.cz>
       Bjoern Jacke
       Mads Martin Joergensen <mmj@suse.de>
       Michal Ludvig <mludvig@suse.cz>
       Marius Tomaschewski <mt@suse.de>

SEE ALSO
       routes(5), ifcfg(5), ifup(8).

sysconfig			  August 2004			 IFCFG-VLAN(5)

Vote for polarhome