Hi once again,
On Wednesday 18 July 2001 18:35, you wrote:
> Try tcpdump during a ping to another node on the local subnet
> tcpdump -i eth0 icmp
Yes! Ok, I tried this, and now I'm getting somewhere. Starting from a fresh
RedHat 7.1 installation, just rebooted, we have --
[ insert card ... beep beep ... wvlan_cs loaded ]
[root@localhost ihab]# iwconfig eth0
eth0 IEEE 802.11-DS ESSID:"Wavelan Network"
Nickname:"localhost.localdomain"
Frequency:2.422GHz Sensitivity:1/3 Mode:Ad-Hoc
Access Point: 02:60:1D:F0:D6:0A
Bit Rate:2Mb/s RTS thr:off Fragment thr:off
Encryption key:7365-6375-31
Power Management:off
Link quality:0/92 Signal level:-102 dBm Noise level:-102 dBm
Rx invalid nwid:0 invalid crypt:0 invalid misc:0
[root@localhost ihab]# iwconfig eth0 essid linksys
[root@localhost ihab]# iwconfig eth0 mode managed
[root@localhost ihab]# iwconfig eth0 enc off
But 'iwconfig' still shows 'Mode:Ad-Hoc'. Oh well. Now do --
[root@localhost ihab]# ifconfig eth0 192.168.1.130 netmask 255.255.255.0
And now, aha!, iwconfig shows 'Mode:Managed'. Okay. Now, do --
[root@localhost ihab]# ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) from 192.168.1.130 : 56(84) bytes of data.
>From 192.168.1.130: Destination Host Unreachable
>From 192.168.1.130: Destination Host Unreachable
>From 192.168.1.130: Destination Host Unreachable
< ... repeated ... >
while, in another window, tcpdump is saying --
[root@localhost ihab]# /usr/sbin/tcpdump -i eth0
Kernel filter, protocol ALL, TURBO mode (575 frames), datagram packet socket
tcpdump: listening on eth0
11:49:25.638503 > arp who-has 192.168.1.1 tell 192.168.1.130 (0:60:1d:f0:d6:a)
11:49:25.648503 < arp reply 192.168.1.1 is-at 0:4:5a:cf:ad:85
(0:60:1d:f0:d6:a)
11:49:26.638503 > arp who-has 192.168.1.1 tell 192.168.1.130 (0:60:1d:f0:d6:a)
11:49:26.638503 < arp reply 192.168.1.1 is-at 0:4:5a:cf:ad:85
(0:60:1d:f0:d6:a)
11:49:27.638503 > arp who-has 192.168.1.1 tell 192.168.1.130 (0:60:1d:f0:d6:a)
11:49:27.638503 < arp reply 192.168.1.1 is-at 0:4:5a:cf:ad:85
(0:60:1d:f0:d6:a)
11:49:28.638503 > arp who-has 192.168.1.1 tell 192.168.1.130 (0:60:1d:f0:d6:a)
11:49:28.638503 < arp reply 192.168.1.1 is-at 0:4:5a:cf:ad:85
(0:60:1d:f0:d6:a)
11:49:29.638503 > arp who-has 192.168.1.1 tell 192.168.1.130 (0:60:1d:f0:d6:a)
11:49:29.638503 < arp reply 192.168.1.1 is-at 0:4:5a:cf:ad:85
(0:60:1d:f0:d6:a)
11:49:30.638503 > arp who-has 192.168.1.1 tell 192.168.1.130 (0:60:1d:f0:d6:a)
11:49:30.638503 < arp reply 192.168.1.1 is-at 0:4:5a:cf:ad:85
(0:60:1d:f0:d6:a)
< ... repeated ... >
and, after doing this for a while, I have --
[root@localhost ihab]# ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:60:1D:F0:D6:0A
inet addr:192.168.1.130 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:12 errors:0 dropped:0 overruns:0 frame:0
TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
collisions:0
So, correct me if I'm wrong, but it seems _some_ physical layer stuff is
actually happening (my router is replying with its MAC address) ... but there
are no ICMP packets going through. How strange.
* * * * *
Now, as I mentioned, this is with a fresh Seawolf install just for
consistency. I have also attempted to remove the 'kernel-pcmcia-cs' RPM and
install the 'pcmcia-cs-3.1.27' module from sourceforge, which allows me to
turn on debugging and play with the source code. It seemed -- at a
superficial level -- that there were packets being transmitted by the driver.
* * * * *
As a test, I tried bringing up eth0 via my 3Com 10/100BaseT PCMCIA card,
going to the same Linksys router. I brought up eth0 manually exactly as I did
with the wireless, and here's what I got for the ping --
[root@localhost ihab]# ping -I eth0 192.168.1.1
PING 192.168.1.1 (192.168.1.1) from 192.168.1.130 eth0: 56(84) bytes of data.
Warning: time of day goes back, taking countermeasures.
64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=1.955 msec
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=763 usec
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=758 usec
< ... repeated ... >
and, in tcpdump --
[root@localhost ihab]# /usr/sbin/tcpdump -i eth0
Kernel filter, protocol ALL, TURBO mode (575 frames), datagram packet socket
tcpdump: listening on eth0
11:57:18.438503 M 160.94.110.92.50499 > 239.255.255.253.svrloc: udp 49
11:57:22.458503 M 160.94.110.92.50499 > 239.255.255.253.svrloc: udp 49
11:57:22.798503 > arp who-has 192.168.1.1 tell 192.168.1.130
(0:50:da:e9:f0:ee)
11:57:22.798503 < arp reply 192.168.1.1 is-at 0:4:5a:cf:ad:85
(0:50:da:e9:f0:ee)
11:57:22.798503 > 192.168.1.130 > 192.168.1.1: icmp: echo request (DF)
11:57:22.798503 < 192.168.1.1 > 192.168.1.130: icmp: echo reply
11:57:23.798503 > 192.168.1.130 > 192.168.1.1: icmp: echo request (DF)
11:57:23.798503 < 192.168.1.1 > 192.168.1.130: icmp: echo reply
11:57:24.798503 > 192.168.1.130 > 192.168.1.1: icmp: echo request (DF)
11:57:24.798503 < 192.168.1.1 > 192.168.1.130: icmp: echo reply
11:57:25.798503 > 192.168.1.130 > 192.168.1.1: icmp: echo request (DF)
11:57:25.798503 < 192.168.1.1 > 192.168.1.130: icmp: echo reply
11:57:26.478503 M 160.94.110.92.50499 > 239.255.255.253.svrloc: udp 49
11:57:26.798503 > 192.168.1.130 > 192.168.1.1: icmp: echo request (DF)
11:57:26.798503 < 192.168.1.1 > 192.168.1.130: icmp: echo reply
11:57:27.328503 M 160.94.109.50.afs3-rmtsys > 224.101.101.101.afs3-rmtsys:
udp 309 [ttl 1]
11:57:27.798503 > 192.168.1.130 > 192.168.1.1: icmp: echo request (DF)
11:57:27.798503 < 192.168.1.1 > 192.168.1.130: icmp: echo reply
< ... etc etc ... >
which looks very much like what Stephen Carville listed as an example. Hm.
* * * * *
Thanks as always & peace,
Ihab Awad
--
Ihab A Awad <[EMAIL PROTECTED]>
Center for Computational Genomics and Bioinformatics,
University of Minnesota. http://www.cbc.umn.edu/~ihab/
_______________________________________________
Seawolf-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/seawolf-list
