Try forcing both cards to 10Mbs, every cross over cable I've tried with
100Mbs never worked.


J Saunders wrote:

> Hi Folks!
>
> Thanks to all those who have so far offered help.
>
> > Check the tcpdump. If it shows the packets going out on the interface,
> > then you have a cable problem. Otherwise, you have a routing problem.
>
> Okay, I'm a networking newbie, so I'm sending some tcpdump info. I have
> read the NET3-HOWTO, and everything looks set up as it suggests. In
> fact, I've used the Redhat netcfg utility and checked that against NET3.
> I don't have routed running as there's only the two machines. I just
> don't understand why this is happening (as everything I know to check
> looks just fine).
>
> Maybe you guys can give me some verbose pointers? tcpdump on both
> machines gives the same output (phew!), so it would seem that the
> cabling is okay, so it's down to a routing problem. What to do, then?
>
> Background - both are running kernel 2.2.5, office1 is a dual PII SMP
> machine with Intel Pro/100+ TX card (using eepro100 driver), whereas
> office2 is a single proc machine with Realtek PCI-NE2000 card (using
> ne2k-pci). Office1 is running samba, which explains the netbios
> datagrams.
>
> First, to get the IP and HWaddr info:
>
> [root@office1 linux]# ifconfig eth0
> eth0      Link encap:Ethernet  HWaddr 00:10:5C:AB:01:D8
>           inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
>           UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
>           RX packets:218 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:819 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:2 txqueuelen:100
>           Interrupt:11 Base address:0xe800 Memory:40-0
>
> [root@office2 /root]# ifconfig eth0
> eth0      Link encap:Ethernet  HWaddr 00:00:E8:D7:4C:21
>           inet addr:192.168.1.2  Bcast:192.168.1.255  Mask:255.255.255.0
>           UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
>           RX packets:311 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:2581 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:100
>           Interrupt:10 Base address:0x6400
>
> [root@office1 linux]# ping office2
> PING office2 (192.168.1.2): 56 data bytes
>
> There was 100% packet loss
>
> Here's the tcpdump:
>
> 17:01:05.300986 office1 > office2: icmp: echo request
> 17:01:06.301268 office1 > office2: icmp: echo request
> 17:01:07.321620 office1 > office2: icmp: echo request
> 17:01:08.321269 office1 > office2: icmp: echo request
> 17:01:09.321273 office1 > office2: icmp: echo request
> 17:01:10.291220 arp who-has office2 tell office1
> 17:01:10.291528 arp reply office2 is-at 0:0:e8:d7:4c:21
> 17:01:10.321239 office1 > office2: icmp: echo request
> 17:01:11.291215 arp who-has office2 tell office1
> 17:01:11.291517 arp reply office2 is-at 0:0:e8:d7:4c:21
> 17:01:11.321255 office1 > office2: icmp: echo request
> 17:01:12.291216 arp who-has office2 tell office1
> 17:01:12.291526 arp reply office2 is-at 0:0:e8:d7:4c:21
>
> Okay... so, I'll try it from the other end:
>
> [root@office2 /root]# ping office1
> PING office1 (192.168.1.1): 56 data bytes
>
> 100% packet loss as usual....
>
> 17:17:55.120115 office2 > office1: icmp: echo request
> 17:17:56.119833 office2 > office1: icmp: echo request
> 17:17:57.119670 office2 > office1: icmp: echo request
> 17:17:58.119618 office2 > office1: icmp: echo request
> 17:17:59.119332 office2 > office1: icmp: echo request
> 17:18:00.119177 office2 > office1: icmp: echo request
> 17:18:09.291364 office1.netbios-dgm > 192.168.1.0.netbios-dgm: udp 213
> 17:18:09.291456 office1.netbios-dgm > office2.netbios-dgm: udp 181
> 17:18:14.291217 arp who-has office2 tell office1
> 17:18:14.291522 arp reply office2 is-at 0:0:e8:d7:4c:21
> 17:18:15.291226 arp who-has office2 tell office1
> 17:18:15.291531 arp reply office2 is-at 0:0:e8:d7:4c:21
> 17:18:16.291215 arp who-has office2 tell office1
> 17:18:16.291527 arp reply office2 is-at 0:0:e8:d7:4c:21
>
> Neither machine sends replies to the other. They just send requests.
> Both machines get exactly the same output from tcpdump. Please let me
> know what I should do to get them talking.
>
> Thanks,
> Jason
> -
> To unsubscribe from this list: send the line "unsubscribe linux-net" in
> the body of a message to [EMAIL PROTECTED]

--
(...Later..:)
         _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
        _/                        _/ Exxon Research & Engineering   _/
       _/ _/_/_/ _/_/     _/_/_/ _/ Kevin K. Sochacki              _/
      _/ _/     _/  _/   _/     _/ ICSBS CC124 (908) 730-2911     _/
     _/ _/_/_/ _/_/   & _/_/_/ _/ mailto:[EMAIL PROTECTED]       _/
    _/ _/     _/ _/    _/     _/ PERSONAL                       _/
   _/ _/_/_/ _/  _/   _/_/_/ _/ mailto:[EMAIL PROTECTED]       _/
  _/                        _/ http://mars.superlink.net/kks  _/
 _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/



-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]

Reply via email to