VCONFIG(8)
β¨ NAME β¨
okay so bestie, we're in section 8 of the System Manager's Manual, and this page is all about vconfig β the VLAN (802.1q) configuration program π
πΈ SYNOPSIS πΈ
vconfig [lots of long options]
that's it. that's the whole vibe. lots of long options, no cap π«Ά
π¦ DESCRIPTION π¦
so vconfig is the little program that lets you create and remove vlan-devices on a vlan enabled kernel β¨
and what even is a vlan-device, you ask? they're virtual ethernet devices β virtual ethernet devices which represents the virtual lans on the physical lan. like, the whole point. literally the entire point π
π OPTIONS π
add [interface-name] [vlan-id]β Creates a vlan-device on[interface-name]. The resulting vlan-device will be called according to the nameing convention set. π (yes we're keeping the original spelling, we don't gatekeep typos here, it's giving iconic)rem [vlan-device]β Removes the named vlan-device. bye bestie πset_flag [vlan-device] 0 | 1β When1(the default since2.6.18), ethernet header reorders are turned on. Dumping the device will appear as a common ethernet device without vlans. When0however, ethernet headers are not reordered, which results in vlan tagged packets when dumping the device. Usually the default gives no problems, but some packet filtering programs might have problems with it. β οΈ so like, know your filtering programs before you flip this oneset_egress_map [vlan-device] [skb-priority] [vlan-qos]β This flags that outbound packets with a particularskb-priorityshould be tagged with the particular vlan priorityvlan-qos. The default vlan priority is0. π€set_ingress_map [vlan-device] [skb-priority] [vlan-qos]β This flags that inbound packets with the particular vlan priorityvlan-qosshould be queued with a particularskb-priority. The default skb-priority is0. π₯set_name_type VLAN_PLUS_VID | VLAN_PLUS_VID_NO_PAD | DEV_PLUS_VID | DEV_PLUS_VID_NO_PADβ Sets the way vlan-device names are created. Usevconfigwithout arguments to see the different formats. β¨ (run it with zero args, it's basically a little fashion show of naming formats)NOTESβ VLAN will use Broadcom's NICE interface when the network device supports it. This is necessary, since usually the hardware of these devices already removes the vlan tag from the ethernet packet. Theset_flagoption on vlan-devices created on such a physical network device will be ignored. Dumping the network-device will show only untagged(non-vlan) traffic, and dumping the vlan-devices will only show traffic intended for that vlan, without the tags. π
π¨ real talk: on those NICE-interface devices, your set_flag is doing absolutely nothing. it's not broken, it's just being ignored. the hardware already ate the tag.
π FILES π
/proc/net/vlan/config/proc/net/vlan/[vlan-device]
go peek, it's giving receipts π§
π SEE ALSO π
π AUTHORS π
This manual page was written by Ard van Breemen <ard@kwaak.net> π«Ά
The vlan patch is written by Ben Greear <greearb@candelatech.com> π
and that's the whole page, bestie β VCONFIG(8), System Manager's Manual, section 8, closing out on that very same VCONFIG(8) footer line π
β¨ mwah, go configure some vlans π
π¦ where this page comes from
- debian bookworm: vlan 2.0.5 Β· GPL-2.0-or-later
- debian trixie: vlan 2.0.5+nmu3 Β· GPL-2.0-or-later
- ubuntu jammy: vlan 2.0.5ubuntu5 Β· GPL-2.0-or-later
- ubuntu noble: vlan 2.0.5ubuntu5 Β· GPL-2.0-or-later
- ubuntu questing: vlan 2.0.5+nmu3ubuntu1
- ubuntu resolute: vlan 2.0.5+nmu3ubuntu2 Β· GPL-2.0-or-later
- ubuntu stonking: vlan 2.0.5+nmu3ubuntu2 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms