Re: wep on ath not working in 6.0

George Hartzell <[email protected]>
Newsgroups gmane.os.freebsd.devel.mobile
Message-ID <[email protected]>
Eric Anderson writes:
 > Ross Adams Lippert wrote:
 > 
 > >Hi,
 > >
 > >I'm using an atheros card with freeBSD 6.0.  I'm having trouble making wep work.
 > >(I'm not subscribed to freebsd-mobile, btw)
 > >
 > >The /etc/start_if.ath0 file says
 > >  ifconfig ath0 ssid "name" wepmode on wepkey 0x12345....
 > >and my /etc/rc.conf says
 > >  ifconfig_ath0="inet 192.168.1.4 netmask 255.255.255.0"
 > >  defaultrouter="192.168.1.1"
 > >I'm getting "no route to host" messages when I try to ping the router.
 > >If I disable wep then everything works, but I'd rather know how to fix
 > >this problem.  This worked just as it is on freebsd 5.3.
 > >
 > >I have wlan_wep loaded as shown here
 > >  squiggy# kldstat -v | egrep -e 'wlan|ath'
 > >                27 ath_hal
 > >                42 ath_rate
 > >                43 pci/if_ath
 > >                44 cardbus/if_ath
 > >                218 wlan_wep
 > >                219 wlan
 > >
 > >I did not see anything on the support pages on freebsd.org to indicate
 > >that there was no known problem.
 > >  
 > >
 > 
 > Did you set the 'weptxkey 1' option also?  I can't tell, since there is 
 > a '....' there..

You could also use wpa_supplicant to handle the wep'ing.  Here's a
sample /etc/wpa_supplicant file:

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=wheel
network={
	ssid="NETWORKNAMEHERE"
	key_mgmt=NONE
	wep_key0="abcde"
	wep_key1=0102030405
	wep_key2="1234567890123"
	wep_tx_keyidx=0
	priority=5
}

that ought to work.

I *think* that you can just add WPA to the ifconfig_ath0 line and do
away with /etc/start_if.ath0.

g.
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-mobile
To unsubscribe, send any mail to "[email protected]"
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.