vconfig changes?

Issues related to configuring your network
Post Reply
Posts: 1
Joined: 2008/04/20 16:28:45

vconfig changes?

Post by mojohost » 2008/11/15 02:45:52

Reading the home page for 802.1q, the oldest release posts the usage for vconfig:
Usage: add [interface-name] [vlan_id]
rem [vlan-name]
set_dflt [interface-name] [vlan_id]
add_port [port-name] [vlan_id]
rem_port [port-name] [vlan_id]
set_egress_map [vlan-name] [skb_priority] [vlan_qos]
set_ingress_map [vlan-name] [skb_priority] [vlan_qos]
set_name_type [name-type]
set_bind_mode [bind-type]

* The [interface-name] is the name of the ethernet card that hosts
the VLAN you are talking about.
* The port-name is the name of the physical interface that a VLAN
may be attached to.
* The vlan_id is the identifier (0-4095) of the VLAN you are operating on.
* skb_priority is the priority in the socket buffer (sk_buff).
* vlan_qos is the 3 bit priority in the VLAN header
* name-type: VLAN_PLUS_VID (vlan0005), VLAN_PLUS_VID_NO_PAD (vlan5),
DEV_PLUS_VID (eth0.0005), DEV_PLUS_VID_NO_PAD (eth0.5)
* bind-type: PER_DEVICE # Allows vlan 5 on eth0 and eth1 to be unique.
PER_KERNEL # Forces vlan 5 to be unique across all devices.

You'll notice set_bind_mode as an option. Running vconfig on any latest release Centos shows virtually the same output, but minus set_bind_mode (Except farther down in the explanations where it still erroneously defines the bind-types.)

# vconfig set_bind_mode PER_KERNEL
Unknown command -:set_bind_mode:-

It seems that Suse (don't want to go there) has maintained the per_kernel bind-type as instructed at

It doesn't make sense to me that I can't assign a vlan to multiple interfaces, is there another way to do this since it seems that RH/Centos don't have this functionality included in vconfig?

Site Admin
Posts: 875
Joined: 2005/01/03 21:30:54
Location: /country/belgium

vconfig changes?

Post by arrfab » 2008/11/25 13:10:45

I've never used vconfig to configure my vlan interfaces on CentOS ..
Just create a file in the /etc/sysconfig/network-scripts/ that contains vlan informations
example (136 being the VLAN number of course):

cat /etc/sysconfig/network-scripts/ifcfg-eth0.136

ifup eth0.136 and hop, vlan tagging on the fly
I've used (and i still use) the same technique on CentOS 4.x and 5.x without any problems ... even for bond* interfaces
I suggest you to read the sysinit doc : /usr/share/doc/initscripts-*/sysconfig.txt

Post Reply

Return to “CentOS 4 - Networking Support”