Date: Tue, 3 Sep 2002 00:40:03 -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: <200209030740.g837e39P048749@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: Tue, 03 Sep 2002 17:30:52 +1000 > I've done a whole heap more testing on this, and I'm still very confused. More testing, using an Apple Ti Powerbook and my laptop running FreeBSD and Windows ME. This works for every combination of Ad-hoc/Hostap, WEP/no-WEP, using either the Apple or FreeBSD as the access point and the Apple, FreeBSD and WindowsME as the client, _except_: it will not work using the WindowsME client in Infrastructure mode with WEP enabled, with any access point we tried. This is almost certainly a bug in the D-Link windows driver. I have been using the latest version available on the dlink.com.au site (1.34) which is the same version as is on the CD that came with the card. The dlink.com site has a later version; it's "1.07.37F" on the config utility About page. This version does work with WEP in Infrastructure mode using the Powerbook as the access point. I can't check with the FreeBSD as an access point for a few days. Chalk it up to bad Windows drivers caused by stale vendor web page. This PR can be closed. 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?200209030740.g837e39P048749>