Solved bwi WEP no carrier

Hello.

I just want to understand what the problem is with connecting to WEP with my BWI wireless card.

/boot/loader.conf:
Code:
if_bwi_load="YES"
wlan_wep_load="YES"
/etc/rc.conf/
Code:
wlans_bwi=wlan0
ifconfig_wlan0="WPA DHCP ssid Frontier7874"
/etc/wpa_supplicant.conf
Code:
network={
ssid="Frontier7874"
key_mgmt=NONE
wep_key1=0123456789
wep_tx_keyidx=1
}
After I use # ifconfig wlan0 up the wireless light goes green. And after I use # ifconfig wlan0, I see that wireless tried to taste different channels: 1,2,3,...., and again 1,2,3,4.... and there is no association taking place. What am I do wrong ?

Thank you.
 
In /etc/rc.conf, you only need
Code:
ifconfig_wlan0="WPA DHCP"
. You don't need ssid Frontier7874 in ifconfig_wlan0.
 
It's not helpful.
Still I can scan all the networks, but can't connect to anyone, don't know why =(
Tried Ndis, which isn't helpful also, because after kldload *driver.sys.ko there is no new interface in ifconfig
 
kAldown said:
I tried with open WEP, and there goes another problem:
Code:
bwi0: bwi_restart begins, help!
Have you tried with no security at all? Also, are you aware of the use of quotes in wep_keyN?
Code:
wep_keyN key
	     An ASCII string enclosed in quotation marks to encode the WEP
	     key.  Without quotes this is a hex string of the actual key. [...]
You could use wpa_cli(8) to interactively debug authentication issues.
 
Just a friendly reminder, don't use WEP. It's so broken it will take a hacker only a couple of minutes to break the "encryption". For your own safety use WPA instead.
 
Thanks to all.

Yes, I tried as an ASCII and as a HEX (it's a 60\64 HEX for sure), Tried as 0xPASSWORD, and as a PASSWORD simple. there is no solution. Some off-topic: I just came in to IN state, as a Russian student for a summer, and there was Windows XP, on a very old computer, so I want to install FreeBSD, but WiFi isn't working. There are 12 people who else using WiFi very strongly, so nobody cares about security :D. And I can not move the DSL modem, because of the short cable.

I think that it is something with firmware. I downloaded it on a next computer, and mv it to /usr/ports/distfiles/.
 
Back
Top