Revision history  [back]

I have a failed router that is spitting out a constant stream of 60 byte packets on the LAN and WAN ports.
=All of it's ethernet ports=
They are coming from a source address completely different than what the device's known and printed label Mac address is.

I've never seen this type of packet before and the face the this device died and is spitting these out continuously Is very interesting.

The Hardware is an XBlue X-50 Phone IP PBX all-in one box with a NAT router.

Anybody know where these type of packets would normally be used or show up?
First time I've seen these ever.
Or noticed them anyhow.

Thanks!

Steve

Frame 1: 60 bytes on wire (480 bits), 60 bytes captured (480 bits) on interface \Device\NPF_{E99B9D26-C0CB-4C1F-BA28-62A94F6D740D}, id 0
Ethernet II, Src: 02:50:c2:3b:70:00 (02:50:c2:3b:70:00), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
    Destination: Broadcast (ff:ff:ff:ff:ff:ff)
        Address: Broadcast (ff:ff:ff:ff:ff:ff)
        .... ..1. .... .... .... .... = LG bit: Locally administered address (this is NOT the factory default)
        .... ...1 .... .... .... .... = IG bit: Group address (multicast/broadcast)
    Source: 02:50:c2:3b:70:00 (02:50:c2:3b:70:00)
        Address: 02:50:c2:3b:70:00 (02:50:c2:3b:70:00)
        .... ..1. .... .... .... .... = LG bit: Locally administered address (this is NOT the factory default)
        .... ...0 .... .... .... .... = IG bit: Individual address (unicast)
    Type: CSM_ENCAPS Protocol (0x889b)
CSM_ENCAPS
    Opcode: Control Packet (0x0001)
    Sequence Number: 7
    Channel Number: 0x0000
    Length: 0
    Index: 0
    Class: 32
    Type: 4
    Function Code:   (0x0000)
Control: 0x00
    0... .... = Packet Bit: Message Packet
    .0.. .... = ACK Suppress Bit: ACK Required
    .... ...0 = Endian Bit: Big Endian

I have a failed router that is spitting out a constant stream of 60 byte packets on the LAN and WAN ports.
=All All of it's ethernet ports= ports
They are coming from a source address completely different differnet than what the device's known know and printed label Mac address is.

I've never seen this thsi type of packet before and the face the this device died and is spitting these out continuously Is very interesting.

The Hardware is an XBlue X-50 Phone IP PBX all-in one box with a NAT router.

Anybody know where these type of packets would normally be used or show up?
First time I've seen these ever.
Or noticed them anyhow.

Thanks!

Steve

Frame 1: 60 bytes on wire (480 bits), 60 bytes captured (480 bits) on interface \Device\NPF_{E99B9D26-C0CB-4C1F-BA28-62A94F6D740D}, id 0 Ethernet II, Src: 02:50:c2:3b:70:00 (02:50:c2:3b:70:00), Dst: Broadcast (ff:ff:ff:ff:ff:ff) Destination: Broadcast (ff:ff:ff:ff:ff:ff) Address: Broadcast (ff:ff:ff:ff:ff:ff) .... ..1. .... .... .... .... = LG bit: Locally administered address (this is NOT the factory default) .... ...1 .... .... .... .... = IG bit: Group address (multicast/broadcast) Source: 02:50:c2:3b:70:00 (02:50:c2:3b:70:00) Address: 02:50:c2:3b:70:00 (02:50:c2:3b:70:00) .... ..1. .... .... .... .... = LG bit: Locally administered address (this is NOT the factory default) .... ...0 .... .... .... .... = IG bit: Individual address (unicast) Type: CSM_ENCAPS Protocol (0x889b) CSM_ENCAPS Opcode: Control Packet (0x0001) Sequence Number: 7 Channel Number: 0x0000 Length: 0 Index: 0 Class: 32 Type: 4 Function Code: (0x0000) Control: 0x00 0... .... = Packet Bit: Message Packet .0.. .... = ACK Suppress Bit: ACK Required .... ...0 = Endian Bit: Big Endian