On Fri, Feb 15, 2002 at 05:16:33PM +0100, bert hubert wrote: > > I have a server that has two ethernet cards, eth0 (64.94.46.199) and > > eth1 (66.28.98.52). > > Can you show what happens? So something like this: I found out that even before I make the IP routing table changes that I mentioned in my previous message, there is already this problem. Check this out: [root@lina rc.d]# ping -r -b 64.94.47.255 WARNING: pinging broadcast address PING 64.94.47.255 (64.94.47.255) from 64.94.46.199 : 56(84) bytes of data. Warning: time of day goes back, taking countermeasures. 64 bytes from 64.94.46.199: icmp_seq=0 ttl=255 time=1.081 msec 64 bytes from 64.94.46.199: icmp_seq=1 ttl=255 time=109 usec 64 bytes from 64.94.46.35: icmp_seq=0 ttl=255 time=1.012 sec (DUP!) 64 bytes from 64.94.46.206: icmp_seq=0 ttl=255 time=1.013 sec (DUP!) 64 bytes from 64.94.46.197: icmp_seq=0 ttl=255 time=1.013 sec (DUP!) 64 bytes from 64.94.46.202: icmp_seq=0 ttl=255 time=1.013 sec (DUP!) 64 bytes from 64.94.46.200: icmp_seq=0 ttl=255 time=1.014 sec (DUP!) The above is a ping broadcast. I used the -r flag to make ping send directly to hosts on the local network, bypassing the routing tables (so that I know my routing tables are not an issue). But yet, the ping times are 1 second which is outrageous for hosts on a local network. Any ideas what I should try next? Would this be a problem with the ethernet card, network cable, switch, or any of the above?
