I already created another post about this issue, but now I have a new RUT140 out the box to test with.
My setup is really basic: laptop connected to LAN port - WAN port connected to Ubiquity switch => ISP router. The Ubiquity switch has RSTP enabled (no specific config as this is the only managed L2 device I have in my network)
Config LAN = Type Wired (no bridge) - ETH0.1 - Static IP (everything else just default)
Config WAN = Type Wired - ETH0.2 - DHCP (everything default)
From my understanding STP / BPDU packets are strictly L2 and shouldn’t leave the L2 subnet / vlan. But when I wireshark on my laptop, I immediately see the bpdu’s from my ubiquiti switch which means they are being routed (L3).
5 0.519378 Ubiquiti_d0:2f:06 Spanning-tree-(for-bridges)_00 STP 60 RST. Root = 32768/0/74:ac:b9:d0:2f:05 Cost = 0 Port = 0x8002
Frame 403: 60 bytes on wire (480 bits), 60 bytes captured (480 bits) on interface \Device\NPF_{BAAB2F59-A2DD-4C0B-9050-783D1CC28D8C}, id 0
IEEE 802.3 Ethernet
Logical-Link Control
Spanning Tree Protocol
Protocol Identifier: Spanning Tree Protocol (0x0000)
Protocol Version Identifier: Rapid Spanning Tree (2)
BPDU Type: Rapid/Multiple Spanning Tree (0x02)
BPDU flags: 0x3e, Forwarding, Learning, Port Role: Designated, Proposal
Root Identifier: 32768 / 0 / 74:ac:b9:d0:2f:05
Root Path Cost: 0
Bridge Identifier: 32768 / 0 / 74:ac:b9:d0:2f:05
Port identifier: 0x8002
Message Age: 0
Max Age: 20
Hello Time: 2
Forward Delay: 15
Version 1 Length: 0
Is this a bug? If yes, how can I report it?
Thank you for looking into this. Also, what would be an appropriate way to deal with this? I assume some kind of ACL to just drop these on the WAN?
Kind regards,
Tom