Re: P2P Networking Question
First of all i'd like to apologise for the late reply (real life stuff and all that), so here's what i got:
>tcpdump -i eth0
>
>then from the win32 box ping the linux box see if anything comes up on the
>terminal
>running tcpdump.
Yea, actually i'm surprised that something did in fact come up...
20:53:21.704143 arp who-has mercury tell 192.168.1.2
20:53:21.704143 arp reply mercury is-at 0:0:e8:1b:83:4b
20:53:23.204143 arp who-has mercury tell 192.168.1.2
20:53:23.204143 arp reply mercury is-at 0:0:e8:1b:83:4b
etc..
>verify the cable is working as well by using it between 2 other systems.
It's a brand new cable, and the link lights on both NIC's are on
>lastly
>if it still does not work ...
>run:
>ifconfig eth0 >/tmp/diagnostics.log
>route -n >>/tmp/diagnostics.log
>uname -a >>/tmp/diagnostics.log
>lsmod >>/tmp/diagnostics.log
>lspci -v >>/tmp/diagnostics.log
>
>and copy the contents of that file to an email to the list. you may need to
**Start**
eth0 Link encap:Ethernet HWaddr 00:00:E8:1B:83:4B
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:6336 errors:0 dropped:0 overruns:0 frame:0
TX packets:6342 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
Interrupt:10 Base address:0x300
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
Linux mercury 2.2.18pre21 #1 Sat Nov 18 18:47:15 EST 2000 i486 unknown
Module Size Used by
af_packet 6136 0 (autoclean)
lockd 41720 0 (autoclean) (unused)
sunrpc 55452 0 (autoclean) [lockd]
serial 19640 1 (autoclean)
nls_cp437 3880 0 (autoclean)
pcmcia_core 44896 0
ne 6132 1
8390 5924 0 [ne]
unix 11336 9 (autoclean)
**End**
Now what i found strange about the ifconfig results is the Tx/Rx packets... I guess this means that the NIC's on both machines are set up correctly and the cable works (correct me if i'm wrong).
>in order to use them .. now if your ethernet card is ISA(shudder) don't
>bother with the lspci stuff :)
Yea unfortunately it is, it's on an old dx2/66...
>nate
-Jason
Reply to: