OpenSuSE Man Pages

Man Page or Keyword Search:
Man Architecture
Apropos Keyword Search (all sections) Output format
home | help
x SuSE Linux 13.1-RELEASE x
x SuSE Linux 13.1-RELEASEx
IFCFG-VLAN(5)                Network configuration               IFCFG-VLAN(5)

NAME
       ifcfg-vlan - virtual LAN interface configuration

SYNOPSIS
       /etc/sysconfig/network/ifcfg-*

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.

       It may contain the optional

       VLAN_PROTOCOL
              variable that may be set to  one  of  the  supported  protocols:
              "ieee802-1Q", "ieee802-1ad".

       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.

       An ifcfg- file for the interface specified by ETHERDEVICE must also  be
       provided.  In  the  most  basic case, it should at least contain START-
       MODE='auto'.

       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
       Mads Martin Joergensen <mmj@suse.de>
       Marius Tomaschewski <mt@suse.de>

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

wicked                           January 2014                    IFCFG-VLAN(5)

Want to link to this manual page? Use this URL:
<
http://star2.abcm.com/cgi-bin/bsdi-man?query=ifcfg-vlan&sektion=5&manpath=>

home | help