Date: Wed, 8 May 2002 23:10:03 -0700 (PDT) From: Mark Abene <phiber@radicalmedia.com> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/32124: Cannot set 128 bit wep key on prism2 cards Message-ID: <200205090610.g496A3367422@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/32124; it has been noted by GNATS. From: Mark Abene <phiber@radicalmedia.com> To: Brooks Davis <brooks@one-eyed-alien.net> Cc: freebsd-gnats-submit@FreeBSD.org, nsayer@quack.kfu.com, brooks@FreeBSD.org Subject: Re: kern/32124: Cannot set 128 bit wep key on prism2 cards Date: Thu, 9 May 2002 02:05:28 -0400 I recently had some time to experiment with this problem again, and I've tracked it down: the problem host will totally ignore its response packets UNLESS the "wi" card (in my case an SMC 2632W) is put into promiscuous-mode. I found this out by accident, when I ran tcpdump on the problem machine and noticed that the card magically started working. So, something is still odd with the driver, though this is a temporary work around. The only options I'm setting with wicontrol are -n, -k (with a 128-bit value), and -e. In promiscuous-mode, the card now appears to function properly. Also, I uncovered two more bugs in the driver, which are semi-related: attempting to use WEP key 2, 3, or 4 results in TOTALLY corrupted packets being transmitted by the card. Only key 1 works properly. The second bug appears to be improper bounds checking on the value of the "transmit WEP key" setting. For example, "wicontrol -T 0" will panic the machine, which for some reason I found humorous at this late hour. :) In any event, I hope we can track down the cause of the promiscuous-mode oddity. Cheers, -Mark 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?200205090610.g496A3367422>