No. Time Source Destination Protocol Length Info; 1: 0.000000: Cisco_27:33:f3: Spanning-tree-(for-bridges)_00: STP: 60: RST. Root = 32768/456/00:24:14:1c:5f:00 Cost
c - No traffic bind on interface using SO_BINDTODEVICE tshark -i eth0 1 0.000000 Cisco_51:fd:09 -> Spanning-tree-(for-bridges)_00 STP 62 Conf. Root = 32768/78/00:24:50:51:fd:00 Cost = 0 Port = 0x8009 2 0.326720 192.168.78.1 -> 224.0.0.13 PIMv2 70 Hello 3 1.030538 Cisco_51:fd:09 -> Cisco_51:fd:09 LOOP 62 Reply 4 2.004544 Cisco_51:fd:09 -> Spanning-tree-(for-bridges)_00 STP 62 Conf. Root = 32768/78 Cisco 837 Bridge / Spanning Tree Protocol question 4 4.000129 Cisco_42:1d:14 Spanning-tree-(for-bridges)_00 STP Conf. Root = 32768/00:13:c3:42:1d:14 Cost = 0 Port = 0x8006 Cisco 837 config: Current configuration : 1298 bytes
Spanning Tree Protocol - Wikipedia
CS Personal on cloudshark.org No. Time Source Destination Protocol Length Info; 1: 0.000000: Cisco_27:33:f3: Spanning-tree-(for-bridges)_00: STP: 60: RST. Root = 32768/456/00:24:14:1c:5f:00 Cost Cisco 2960 & Alcatel - Cisco Community
Cisco 837 Bridge / Spanning Tree Protocol question
Netgear GS108E Sending Odd Broadcast Packets (Odd to me at Wireshark adds some information to those lines - interpreting what it sees. But these devices are not capable of spanning tree. Any help would be appreciated - I have two of these devices - when connecting two - they both seem to send out this packet on (2) second intervals. Edit: firmware 1.00.9 and the original gs108e assuming that means v1. Wireshark · Wireshark-bugs: [Wireshark-bugs] [Bug 9236 -- It appears that Wireshark is unable to further decapsulate the "nested" LLC payload from some packets (e.g. 19) within the attached trace file (generated by a generic 802.11 WDS bridging device on my home WLAN), in order to dissect the Spanning Tree Protocol data contained within.