rework how mpw(4) interacts with vlan(4)

previously mpw would walk around our interface hierarchy so it could
reinject vlan tags for packets that were received on a stack of
vlan interfaces. this got in the way of making vlan mpsafe, but is
also unecessary according to how i read RFC 4448 which describes
how mpls pseudowires should function.

the behaviour is now:

- in raw mode mpw(4) acts like a normal ethernet interface

it no longer injects a tag from a vlan interface that may be on the
same bridge as it, and it allows you to configure ip addresses on
the local interface and use them without panicking the kernel.

- in tagged mode it will only add tags from vlan interfaces on the
same bridge as it, but not any parent/child tags from interfaces
on top of that vlan. if the packet did not come from a vlan interface
on a bridge it will inject a tag for vlan 0.

this will also allow vlan to move forward.

ok mpi@ rzalamena@ claudio@

0 files changed, 0 insertions, 0 deletions