Egregoros

Signal feed

API Docs
Timeline

Post

Remote status

Context

2
Peter Wemm

Peter Wemm

@karinjiri@soc.crashed.org remote
Open link
I'm not sure where the vlans_bridge0 parameter fits in but this is what I have:
ifconfig_ixl0="up -lro -txcsum -txcsum6 -tso4 -tso6 -mextpg"
cloned_interfaces="${cloned_interfaces} bridge0"
ifconfig_bridge0="vlanfilter addm ixl0 tagged 99-115 up"
# core network
cloned_interfaces="${cloned_interfaces} vlan100"
ifconfig_vlan100="vlan 100 vlandev bridge0 10.0.0.8/24"
# iot-snowflakes
cloned_interfaces="${cloned_interfaces} vlan112"
ifconfig_vlan112="vlan 112 vlandev bridge0 10.0.12.8/24"

The result looks something like this:
bridge0: flags=1008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,LOWER_UP> metric 0 mtu 1500
options=10<VLAN_HWTAGGING>
bridge flags=1<VLANFILTER>
member: e0a_wfe flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
port 96 priority 128 path cost 2000 vlan protocol 802.1q untagged 100
...
member: ixl0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
port 1 priority 128 path cost 55 vlan protocol 802.1q tagged 99-115
groups: bridge
vlan100: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1496
inet 10.0.0.8 netmask 0xffffff00 broadcast 10.0.0.255
vlan: 100 vlanproto: 802.1q vlanpcp: 0 parent interface: bridge0
vlan112: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1496
inet 10.0.12.8 netmask 0xffffff00 broadcast 10.0.12.255
vlan: 112 vlanproto: 802.1q vlanpcp: 0 parent interface: bridge0

Short version: bridge in hwtagging mode. Each member added identifies what vlans it wants and what's tagged/untagged. e0a_* is half of a jail epair.
Peter Wemm

Peter Wemm

@karinjiri@soc.crashed.org remote
Open link

I think what you're doing is closer to the old way. You've created a bridge and told it about vlans, but haven't enabled hwfilter mode. When you added the interface to it you didn't tell it what vlans it should be configured for. I think.

Replying to @karinjiri@soc.crashed.org

Replies

1
Replying to @karinjiri@soc.crashed.org