On 3/6/18 5:27 PM, Lawrence Kreeger wrote:
> Using ETH_P_ALL instead of ETH_P_802_2, is causing mstpd to get 3
> copies of the same BPDU. One from eth0, one from eth0.100, and
> another from vlan100 (the bridge).
> mstpd will drop the one from vlan100, but since there is also an
> instance of
Using ETH_P_ALL instead of ETH_P_802_2, is causing mstpd to get 3
copies of the same BPDU. One from eth0, one from eth0.100, and
another from vlan100 (the bridge).
mstpd will drop the one from vlan100, but since there is also an
instance of spanning tree running on the native VLAN, there is now
On 3/6/18 3:02 PM, Lawrence Kreeger wrote:
> Hello,
>
> I'm trying to run mstpd on a per VLAN basis using one traditional
> linux bridge per VLAN. I'm running it on kernel version 4.12.4. It
> works fine for untagged frames, but I'm having a problem with VLAN
> tagged BPDUs arriving on the
Hello,
I'm trying to run mstpd on a per VLAN basis using one traditional
linux bridge per VLAN. I'm running it on kernel version 4.12.4. It
works fine for untagged frames, but I'm having a problem with VLAN
tagged BPDUs arriving on the socket with the ifindex of the bridge
itself, and not the
