Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 21 Aug 2002 12:24:50 +1000 (EST)
From:      Gregory Bond <gnb@itga.com.au>
To:        FreeBSD-gnats-submit@FreeBSD.org
Subject:   kern/41834: wi(4) hostap mode won't work with WEP
Message-ID:  <200208210224.g7L2Oocv068297@gnbfw.bond.wattle.id.au>

next in thread | raw e-mail | index | archive | help

>Number:         41834
>Category:       kern
>Synopsis:       wi(4) hostap mode won't work with WEP
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Aug 20 19:30:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Gregory Bond <gnb@itga.com.au>
>Release:        FreeBSD 4.6-STABLE i386
>Organization:
ITG Australia Ltd
>Environment:
System: FreeBSD gnbfw.bond.wattle.id.au 4.6-STABLE FreeBSD 4.6-STABLE #3: Sat Jul 20 16:45:58 EST 2002 root@gregbsd.bond.wattle.id.au:/usr/obj/usr/src/sys/FW i386

Ancient Pentium-100 box acting as a firewall.

wi(4) running on a DLink 520
Client is a WinMe laptop with a DLink 650

wi0: <Intersil Prism2.5> mem 0xfbfe0000-0xfbfe0fff irq 11 at device 12.0 on pci0
wi0: 802.11 address: 00:05:5d:5b:c4:c8
wi0: using RF:PRISM2.5 MAC:ISL3874A(Mini-PCI)
wi0: Intersil Firmware: Primary 1.00.05, Station 1.03.04


>Description:

Using the wi(4) driver in ad-hoc mode, I can enable WEP on both
ends and it works fine.

In hostap mode, and without WEP, it works fine.

In hostap mode with WEP enabled, the laptop cannot get an association.
As soon as I turn WEP off on both ends, the laptop can get an
association.

I'm using Hex keys, and even simple unambiguous keys (like 0x11111...).
I've tried 64 and 128 bit WEP.



I've asked about this in the -stable list, and gotten a couple of
"me too"s from people with other wireless cards, but no answers.
So I don't think it's necessarily a case of user error.

(Yes, I know WEP is not much chop but it's good enough to stop
casual leeching of my cable link.)

[Severity is Serious/medium because it is very unwise to run wireless
without some sort of security.]

As an aside, I can't go from hostap mode back to ad-hoc mode without
a reboot, it gets ENXIO.  Looking at if_wi.c, something like this
appears to be deliberate (in wi_media_change(), line 2846ff), but
I think the ENXIO is coming from sys/net/if_media.c:ifmedia_ioctl(),
due to ifmedia_match() failing, which is very very odd.....

>How-To-Repeat:

# ifconfig wi0 inet <whatever> netmask <whatever> ssid <whatever> wepkey <whatever>
(Put laptop in Ad-Hoc mode with same key)

Note that the link works.

# ifconfig wi0 wepkey <whatever> mediaopt hostap
(Put laptop in BSS mode)

Note failure to get an association.

# ifconfig wi0 -wep
(And turn WEP off on the laptopo)

Note the laptop is able to associate.

# ifconfig wi0 mediaopt adhoc
ifconfig: SIOCSIFMEDIA: Device not configured
#

>Fix:

None known.  Possible work-around is to use IPSEC or PPPoE for
network security.

I'm willing to play around with this box if anyone can give me some 
pointers or wants me to try some debugging.
>Release-Note:
>Audit-Trail:
>Unformatted:

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?200208210224.g7L2Oocv068297>