Incorrect arp for 3Com SuperStack

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Tonight I discovered that I am unable to access my 3Com SuperStack 3300 switch
from either of my Linux hosts. Note that I can use the switch, I just cannot
manage the switch with either Telnet or http. However, my Windows based hosts
have no problem accessing the switch (via telnet or http). After a bit of
research, I've found a problem with the arp entry for the switch on both Linux
hosts. The actual mac address reported on the switch is 00:90:04:b8:b7:d8.

My Linux hosts report:

# arp -an  (host 1)
? (192.168.2.254) at 00:01:03:7B:DD:72 [ether] on eth0

# arp -an  (host 2)
? (192.168.2.254) at 00:01:03:7B:DD:72 [ether] on eth0

However, my Windows hosts report the correct mac address in their arp tables.

I couldn't find this documented anywhere, so I thought I would go to the
source. The Linux hosts are both running 2.2.17-21mdk (Mandrake 7.2) and both
machines are using the stock eepro100 driver that shipped with 'Drake 7.2.

Also, arp -d 192.168.2.254 doesn't seem to kill the entry.

Any ideas?

Thanks!

John LeMay Jr.
Senior Enterprise Consultant
NJMC, LLC.


[tag] It is pitch black. You are likely to be eaten by a grue.
-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.kernel.org


[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux 802.1Q VLAN]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Git]     [Bugtraq]     [Yosemite News and Information]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux PCI]     [Linux Admin]     [Samba]

  Powered by Linux