On 2026-05-29, Eivind Eide <[email protected]> wrote: > I had a vlan connection working that stopped working after upgrade. > Both boxes ran OpenBSD amd64 7.8-stable, now upgraded to 7.9-stable. > On one side there are veb0 (with link0 enabled) -> vport2 -> vlan20. > On the other side there are em0 -> vlan20. > As said, the two vlan20 sent packages back and forth with 7.8. No > connection with 7.9. The configuration of hostname.vlan20 on box1: > parent vport2 vlan 20 vnetid 20 > inet 192.168.20.1 255.255.255.0 192.168.20.255 > up > The same on box2, except IP being 192.168.20.2. I know there where big > changes made to veb in the 7.8->7.9 cycle. But I can't wrap my head > around how that affects my setup. Somebody seeing the obvious that I'm > missing?
veb(4) was made VLAN-aware, i.e. one bridge can be used to carry traffic from multiple vlans, ports are configured with information about which vlans they carry and whether that traffic is tagged or untagged. see https://undeadly.org/cgi?action=article;sid=20251029114507 for more details. I'm not 100% sure but i think you want something along these lines: ----- vport2: inet 192.168.20.1 255.255.255.0 192.168.20.255 up veb0: add <physical interface> -untagged <physical interface> +tagged <physical interface> 20 add vport2 untagged vport2 20 ----- and drop the vlan20 interface... alternatively, you could write a config which is conceptually closer to your previous one, but I think it would be a bit less efficient than the above: ----- vport2: up veb0: add <physical interface> -untagged <physical interface> +tagged <physical interface> 20 add vport2 -untagged vport2 tagged vport2 20 vlan20: parent vport2 vlan 20 vnetid 20 inet 192.168.20.1 255.255.255.0 192.168.20.255 up ----- we could do with something in upgrade docs for this ideally.
