Ethereal dump

Hi.
I've been monitored my network for 24 hours with Ethereal, and found
that a lot of frames like this one above, were generated. It's
generated since the beginning of the monitoring in every 2 seconds,
until the end.

Ethereal dump
--------------------------------
No. Time Source Destination
Protocol Info
75440 77271.422716 BayNetwo_9c:af:be
Spanning-tree-(for-bridges)_00 STP Conf. Root =
32768/00:0e:40:a9:6c:01 Cost = 2 Port = 0x8003

Frame 75440 (60 bytes on wire, 60 bytes captured)
Arrival Time: Nov 1, 2005 15:53:09.168254000
Time delta from previous packet: 1.355742000 seconds
Time since reference or first frame: 77271.422716000 seconds
Frame Number: 75440
Packet Length: 60 bytes
Capture Length: 60 bytes
Protocols in frame: eth:llc:stp
IEEE 802.3 Ethernet
Destination: Spanning-tree-(for-bridges)_00 (01:80:c2:00:00:00)
Source: BayNetwo_9c:af:be (00:e0:7b:9c:af:be)
Length: 38
Trailer: 360D360B36093607
Logical-Link Control
DSAP: Spanning Tree BPDU (0x42)
IG Bit: Individual
SSAP: Spanning Tree BPDU (0x42)
CR Bit: Command
Control field: U, func=UI (0x03)
000. 00.. = Command: Unnumbered Information (0x00)
.... ..11 = Frame type: Unnumbered frame (0x03)
Spanning Tree Protocol
Protocol Identifier: Spanning Tree Protocol (0x0000)
Protocol Version Identifier: Spanning Tree (0)
BPDU Type: Configuration (0x00)
BPDU flags: 0x00
0... .... = Topology Change Acknowledgment: No
.... ...0 = Topology Change: No
Root Identifier: 32768 / 00:0e:40:a9:6c:01
Root Path Cost: 2
Bridge Identifier: 32768 / 00:e0:7b:9c:af:be
Port identifier: 0x8003
Message Age: 1,00390625
Max Age: 20
Hello Time: 2
Forward Delay: 15
---------------------------------

Could you please help me to find out what is going on?

Greets,
Hugo

In article <(E-Mail Removed) .com>,
(E-Mail Removed) says...
> Hi.
> I've been monitored my network for 24 hours with Ethereal, and found
> that a lot of frames like this one above, were generated. It's
> generated since the beginning of the monitoring in every 2 seconds,
> until the end.
>
> Ethereal dump
> --------------------------------
> No. Time Source Destination
> Protocol Info
> 75440 77271.422716 BayNetwo_9c:af:be
> Spanning-tree-(for-bridges)_00 STP Conf. Root =
> 32768/00:0e:40:a9:6c:01 Cost = 2 Port = 0x8003

Issuing spanning-tree packets (BPDUs) every two seconds is a perfectly
normal thing for a network switch to do. It is looking for a possible
loop in your network. You could stop the packets by disabling spanning-
tree on the switch, but why bother?

http://www.zyxel.com/support/support...12/app/stp.htm

/Chris, UCLA

In the Usenet newsgroup comp.os.linux.networking, in article
<(E-Mail Removed) .com>,
(E-Mail Removed) wrote:

>I've been monitored my network for 24 hours with Ethereal, and found
>that a lot of frames like this one above, were generated. It's
>generated since the beginning of the monitoring in every 2 seconds,
>until the end.

Google would be a help here

>IEEE 802.3 Ethernet
> Destination: Spanning-tree-(for-bridges)_00 (01:80:c2:00:00:00)
> Source: BayNetwo_9c:af:be (00:e0:7b:9c:af:be)

01:80:c2 isn't a "standard" Ethernet address - first octet odd means it's a
multicast. WATCH THE LINE WRAP ON THE URL BELOW

Spanning Tree http://www.cisco.com/univercd/cc/td/...oduct/rtrmgmt/
sw_ntman/cwsimain/cwsi2/cwsiug2/vlan2/stpapp.htm
"Understanding Spanning-Tree Protocol: Spanning-Tree Protocol is a link
management protocol that provides path redundancy while preventing
undesirable loops in the network. For an Ethernet network to function
properly, only one active path can exist between two stations..."

[compton ~]$ etherwhois 00:e0:7b
00-E0-7B (hex) BAY NETWORKS
00E07B (base 16) BAY NETWORKS
125 NAGOG PARK
ACTON MA 01720
UNITED STATES
[compton ~]$

So, you have a Bay Networks device that is (mis)configured for doing
Spanning Tree.

Old guy