Wolfgang Bornath wrote: > > Am Dienstag, 27. November 2001 17:12 schrieben Sie: > > OK... give us the results of: > > > > ping -br 255.255.255.255 > > ping -br 192.168.0.255 > > Desktop (disconnected from internet) > > [root@molch wobo]# ping -br 255.255.255.255 > connect: Network is unreachable > > ifconfig (disconnected from internet) says: > > eth0 Protokoll:Ethernet Hardware Adresse 00:50:BA:31:0F:B2 > inet Adresse:10.0.0.10 Bcast:10.0.0.255 Maske:255.255.255.0 > > eth1 Protokoll:Ethernet Hardware Adresse 00:20:AF:6E:F5:16 > inet Adresse:192.168.0.1 Bcast:192.168.0.255 Maske:255.255.255.0 > > lo Protokoll:Lokale Schleife > inet Adresse:127.0.0.1 Maske:255.0.0.0 > > # ping -br 192.168.0.255 > WARNING: pinging broadcast address > PING 192.168.0.255 (192.168.0.255) from 192.168.0.1 : 56(84) bytes of > data. > 64 bytes from 192.168.0.1: icmp_seq=0 ttl=255 time=1.844 msec > 64 bytes from 192.168.0.1: icmp_seq=1 ttl=255 time=205 usec > 64 bytes from 192.168.0.1: icmp_seq=2 ttl=255 time=202 usec > 64 bytes from 192.168.0.1: icmp_seq=3 ttl=255 time=204 usec > > # ping -br 10.0.0.255 > WARNING: pinging broadcast address > PING 10.0.0.255 (10.0.0.255) from 10.0.0.10 : 56(84) bytes of data. > 64 bytes from 10.0.0.10: icmp_seq=0 ttl=255 time=1.838 msec > 64 bytes from 10.0.0.10: icmp_seq=1 ttl=255 time=188 usec > 64 bytes from 10.0.0.10: icmp_seq=2 ttl=255 time=181 usec > > -------------------------------------------------------------------------- > > On the notebook : > > # ping -br 192.168.0.255 > WARNING: pinging broadcast address > PING 192.168.0.255 (192.168.0.255) from 192.168.0.2 : 56(84) bytes of > data. > 64 bytes from 192.168.0.2: icmp_seq=0 ttl=255 time=92 msec > 64 bytes from 192.168.0.2: icmp_seq=1 ttl=255 time=73 usec > 64 bytes from 192.168.0.2: icmp_seq=2 ttl=255 time=73 usec > 64 bytes from 192.168.0.2: icmp_seq=3 ttl=255 time=73 usec > > # ping -br 255.255.255.255 > WARNING: pinging broadcast address > PING 255.255.255.255 (255.255.255.255) from 192.168.0.2 : 56(84) > bytes of data. > 64 bytes from 192.168.0.2: icmp_seq=0 ttl=255 time=71 msec > 64 bytes from 192.168.0.2: icmp_seq=1 ttl=255 time=73 usec > 64 bytes from 192.168.0.2: icmp_seq=2 ttl=255 time=73 usec > 64 bytes from 192.168.0.2: icmp_seq=3 ttl=255 time=70 usec > > ---------------------------------------------------------------------- > > # /sbin/arp -a > # > > arp -a gives nothing on both machines.
The lack of "(DUP!)" responses confirms that neither machine is seeing the other's packets... like it or not, you appear to have a physical problem... "ping -r" bypasses the routing table and sends directly to the NIC... Next steps (assumes your NICs have link & traffic LEDs): 1. see if your "link" LEDs are on on both NICs 2. make sure you have the right drivers installed 3. start pinging (broadcasts as above) from one machine at a time and see if the traffic LED flashes on the card itself... 4. make sure the packet gets to the other end of the cable by checking traffic LED at other machine Until you get past this point, I'm not sure anything else will help... actually, now that I think about it... you could try to force the use of unicast packets only (avoiding the ARP broadcast in the case of directed pings) by setting the "arp" entries manually (see "man arp") in both machines so their arp tables have the IP-to-h/w addresses pre-resolved. BTW, "ping -I eth1 -br 255.255.255.255" should overcome the "Network is unreachable" response... if so, ping may have a bug 'cuz "-r" is supposed to bypass the routing table. Of course, it could be that by doing so, it assumes 255.* is a "network" and tries to find the corresponding interface... oh well... not the first anomoly I've found with ping... Pierre
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
