Date: Sun, 21 Sep 2003 12:46:27 +1000 From: Rudolph Pereira <memetical@yahoo.com.au> To: freebsd-net@freebsd.org Subject: wi problems Message-ID: <20030921024626.GC916@starfleet.org.au>
next in thread | raw e-mail | index | archive | help
Hello, I am having some problems with my lucent-chipset based wi pccard under recent builds of current. The problem seems to have been with commits done ~20 aug; in particular it looks like the commit described at http://lists.freebsd.org/pipermail/cvs-src/2003-August/009232.html breaks things; I'm pretty sure about this because if I apply those changes to a tree checked out from the just before that time that works, it stops working. I am also aware of ongoing problems with the wi driver, but these don't seem related, and I've also tried the owi driver with no success. The card is: wi0: <Avaya Communication Avaya Wireless PC Card> at port 0x180-0x1bf irq 11 function 0 config 1 on pccard0 wi0: 802.11 address: 00:02:2d:31:28:42 wi0: using Lucent Technologies, WaveLAN/IEEE wi0: Lucent Firmware: Station (8.72.1) wi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps I'm trying to get it talking to a prism2.5-based card in a linux machine (i.e adhoc mode). What I see is this: outgoing (from my wi pccard) packets never get to the other machine. For example: (prism2.5) (lucent) 192.168.0.1 192.168.0.2 [ping 192.168.0.2] -> arp request -> -> arp request <- arp reply ...(nothing)... [ add arp entry ] [ping 192.168.0.2] echo request echo request echo reply ...(nothing)... [ping 192.168.0.1] echo request ...(nothing)... I'm trying to narrow down the problematic bits from the above commits, but not having much success so far. Does anyone have any idea what could be going on? Any information, pointers, etc would be appreciated. Thanks
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030921024626.GC916>