Looks like a PCMCIA bridge configuration issue. I had similar problem with the new Teletronics motherboards.
What kind of PCMCIA chipset do you use? In any case, in "/etc/init.d/pcmcia" there is a special kludge (line 116) which detects TI bridges used in Teletronics. Modify it so that it recognizes your PCMCIA chipset ID and check if it will help you. Ray wrote: > On Sun, Jul 28, 2002 at 02:14:06PM +0300, Vladimir I. wrote: > >>Ray wrote about "[leaf-user] WISP drivers loaded but can't ping": >> >> >>>I managed to get WISP-Dist loaded and recognizing my Prism 2 based wireless >>>card with no problem but I can't get it to ping any of my other wireless >>>boxes. All are using the same type of card, 2 are using a standard Debian >>>distro with wlan-ng and 1 is using Station Server. The are all using Ad-Hoc >>>mode with wep disabled and they can talk to each other just fine. From the >>>Statistics page it looks like the WISP-Dist box is seeing packets from the >>>others but just isn't doing anything about them. I'm reasonably sure I >> >>Can you run "tcpdump -i [interface] -n" and see what it shows >>when you try to ping etc? > > > Ok, I removed all machines from the wireless network except the WISP-Dist > box and a laptop and ran tcpdump on the WISP-Dist box and started pinging > from the laptop.: > > # tcpdump -i netcs1 -n > Kernel filter, protocol ALL, datagram packet socket > tcpdump: listening on netcs1 > 11:12:11.852643 B arp who-has 192.168.4.2 tell 192.168.4.6 > 11:12:11.852957 > arp reply 192.168.4.2 (0:2:6f:1:5f:27) is-at > 0:2:6f:1:5f:27 (0:2:6f:1:89:48) > 11:12:12.848877 B arp who-has 192.168.4.2 tell 192.168.4.6 > 11:12:12.849035 > arp reply 192.168.4.2 (0:2:6f:1:5f:27) is-at > 0:2:6f:1:5f:27 (0:2:6f:1:89:48) > 11:12:13.848948 B arp who-has 192.168.4.2 tell 192.168.4.6 > 11:12:13.849102 > arp reply 192.168.4.2 (0:2:6f:1:5f:27) is-at > 0:2:6f:1:5f:27 (0:2:6f:1:89:48) > 11:12:14.850622 B arp who-has 192.168.4.2 tell 192.168.4.6 > 11:12:14.850777 > arp reply 192.168.4.2 (0:2:6f:1:5f:27) is-at > 0:2:6f:1:5f:27 (0:2:6f:1:89:48) > 11:12:15.849210 B arp who-has 192.168.4.2 tell 192.168.4.6 > 11:12:15.849360 > arp reply 192.168.4.2 (0:2:6f:1:5f:27) is-at > 0:2:6f:1:5f:27 (0:2:6f:1:89:48) > > 10 packets received by filter > > The 192.168.4.6 and 0:2:6f:1:89:48 really do belong to the laptop so at > least the WISP box is receiving correctly... I also noticed that the laptop > side shows a RX packets of 0 (using ifconfig) so it's not getting the > replies. Reversing the process outputs nothing at all on the laptop. > > >>>havn't done anything dumb with the routing and iptables -L doesn't show any >>>firewall rules. What could I be missing? >>> >>>BTW I can't seem to cut & paste from the Statistics page (I'm logged in via >>>ssh on the wired link) so is there any good way to get that same >>>information? >> >>Hmm, I'm able to do it. However I didn't try it using xterm, try >>to login via virtual console or change terminal from "xterm" to >>something else. >> >>Of course, you can run statistics commands manually from the >>command line. "iwconfig", "ip addr", "ip route" etc. > > > Thanks I'd forgotten about the ip *** commands. > > Could the output from the WISP box be getting stuck before getting out? > Also, as an experiment I tried running WISP as an AP. The other machines > were able to associate but could not communicate with any others. > > Any ideas? > -- Best Regards, Vladimir Systems Engineer (RHCE) ------------------------------------------------------- This sf.net email is sponsored by: Dice - The leading online job board for high-tech professionals. Search and apply for tech jobs today! http://seeker.dice.com/seeker.epl?rel_code=31 ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
