Date: Sun, 1 Sep 2002 19:50:09 -0700 (PDT) From: Gregory Bond <gnb@itga.com.au> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/41834: wi(4) hostap mode won't work with WEP Message-ID: <200209020250.g822o9YB018210@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/41834; it has been noted by GNATS. From: Gregory Bond <gnb@itga.com.au> To: freebsd-gnats-submit@FreeBSD.org Cc: Subject: Re: kern/41834: wi(4) hostap mode won't work with WEP Date: Mon, 02 Sep 2002 12:44:27 +1000 I've done a whole heap more testing on this, and I'm still very confused. I've loaded a recent FreeBSD onto the laptop, and tested that as well, and all up I have the following matrix: Host is a P-100 with a DLink DWL520 PCI card, running a recent -Stable (4.6+) Client is a Toshiba laptop with a DLink DWL650 PCMCIA card Client OS WindowsME FreeBSD Configuration Ad-Hoc, no WEP Works Works Ad-Hoc, 64bit WEP Works Works Ad-Hoc, 128bit WEP Works Works Hostap, no WEP Works Works Hostap, 64bit WEP Doesn't Work Works Hostap, 128bit WEP Doesn't Work Works Switching between Ad-Hoc and Hostap mode on the server often doesn't work without a reboot. It usually can't be done at all with ifconfig, you have to use wicontrol. And sometimes it needs a powercycle as well. I've not managed to work out any pattern to the mode-change failure yet. No such problems were encountered changing the mode under FreeBSD on the laptop. This looks on the surface like the problem is in the Windows driver, but I can't imagine that a driver shipped over 12 months ago and not updated since could still have this sort of major bug in it.... I'm now scratching around for another access point or whatever to test it on. Any clues about how I might debug this further? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200209020250.g822o9YB018210>