Re: 5.8 panic with vlan on bridge

* Martin Pieuchot [05.11.2015 11:12]: > I think I was confused, could you test the other way around, adding > the bridge before the vlan? > > # ifconfig em0 up > # ifconfig bridge0 add em0 up rule block on em > # ifconfig vlan10 vlandev em0 up Ok, doing it this way

Re: 5.8 panic with vlan on bridge

* Martin Pieuchot [03.11.2015 17:55]: > I'm not sure it applies on 5.8 though... Nope, but I found the following changes to be sufficient on 5.8. It just keeps the vlan tagged packets away from the bridge. Index: net/if.c

Re: 5.8 panic with vlan on bridge

* Martin Pieuchot [04.11.2015 12:53]: > I'd appreciate if you could test my diff and report back. Seems the bridge is working but tagged packets can still be blocked with a bridge rule. This is a current system with your diff and ifconfig em0 up ifconfig vlan10 vlandev

Re: 5.8 panic with vlan on bridge

* Martin Pieuchot [03.11.2015 13:51]: > > It seems the order of interface evaluation changed in 5.8. If a vlan > > parent interface is on a bridge, vlan tagged packets get blocked by > > bridge filter rules on the parent interface. > > Yes, as soon as a interface is part of a

Re: 5.8 panic with vlan on bridge

* Martin Pieuchot <m...@openbsd.org> [02.11.2015 16:28]: > On 30/10/15(Fri) 23:30, Armin Wolfermann wrote: > > The simplest way to reproduce: > > > > ifconfig em0 192.168.1.1 up > > ifconfig vlan10 vlan 10 vlandev em0 up > > ifconfig bridge0 add em0 ad

5.8 panic with vlan on bridge

The simplest way to reproduce: ifconfig em0 192.168.1.1 up ifconfig vlan10 vlan 10 vlandev em0 up ifconfig bridge0 add em0 add vlan10 up booting hd0a:/bsd: 6683804+2138976+254984+0+598016 [72+563184+374279]=0xa210c0 entry point at 0x1000160 [7205c766, 3404, 24448b12, 4060a304] [ using