Talk:VLAN
Hello,
Using the following configuration Alpine 3.19.0 kernel 6.6.13-0-lts does not seem to work depsite the vlan package being present.
auto vlan8 iface vlan8 address 192.168.0.2/24 gateway 192.168.0.1 vlan-raw-device eth0
Has anyone tested this recently ?
— Preceding unsigned comment added by Nailko (talk • contribs) 10:02, 29 January 2024
- Hi there, looks like the very old examples in the article are using the wrong syntax for busybox's ifup... (the vlan package doesn't use ifupdown-ng)... The
addressandnetmasklines cannot be combined. Also good practice to explicitly specify if the interface is DHCP or static... See if something like this will work for you:
auto vlan8 iface vlan8 inet static address 192.168.0.2 netmask 255.255.255.0 gateway 192.168.0.1 vlan-raw-device eth0
- My testing only consisted of seeing if the networking service could be bought up successfully, I have no idea if the VLAN tagging is working or not.
- BTW, for clarity's sake, I set preformatting on for the config in your post to make it easier to see the differences, hope you don't mind!
- –zcrayfish (talk•contribs•send email) 19:07, 29 January 2024 (UTC)
- Hey, I just tested this on 3.21, looks good
lion:~# cat /proc/net/vlan/config
VLAN Dev name | VLAN ID
Name-Type: VLAN_NAME_TYPE_RAW_PLUS_VID_NO_PAD
vlan2360 | 2360 | bond0
lion:~# cat /proc/net/vlan/vlan2360
vlan2360 VID: 2360 REORDER_HDR: 1 dev->priv_flags: 81021
total frames received 8
total bytes received 1442
Broadcast/Multicast Rcvd 8
total frames transmitted 17
total bytes transmitted 2232
Device: bond0
INGRESS priority mappings: 0:0 1:0 2:0 3:0 4:0 5:0 6:0 7:0
EGRESS priority mappings:
lion:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback
auto bond0
iface bond0 inet dhcp
# will be eth0/eth1 for normal setups
bond-slaves onboard0 onboard1
auto vlan2360
iface vlan2360 inet static
address 192.168.236.1
netmask 255.255.255.0
vlan-raw-device bond0
lion:~# cat /etc/mactab
onboard0 18:c0:4dzzzzz1
onboard1 18:c0:4dzzzzz2
I'll try pinging soon and update if it were really broken.
I havent done larger changes to pags on the wiki in a decade but maybe we (the ominous 'someone' we should change the vlan page to primarily cover the current case and only reference a different page for the old setup with the vlan package)
--Darkfader (talk) 23:37, 24 March 2025 (UTC)
- Hi Darkfader, please take a look at the ifupdown-ng vxlan man page and see if this page can be suitably updated. Please feel free to update wiki page and we can always retain the busybox-ifupdown specific config as a seperate section. -- Prabuanand (talk) 04:04, 25 March 2025 (UTC)