On Sat, 20 Sep 2008 17:11:09 +0100
Lisi <hantslug@???> wrote:
> I have followed Jonathan's advice and acquired a ZD-1211b wireless USB dongle.
> And I have been crawling thorugh setting it up at the rate of an hour or 2 on
> the internet and one small step, followed by an hour or 2....
>
> But although I have managed to progress a bit, crucially iwconfig still tells
> me (odd choice of name the box's, not mine):
>
> eth1 IEEE 802.11b/g ESSID:off/any Nickname:"zd1211"
> Mode:Managed Frequency:2.412 GHz Access Point: Invalid
>
> The nickname was supplied automatically, so it has obviously found the right
> card.
>
> And ifconfig gives me its hardware address, so it must be seeing it.
>
> But I cannot get past that "Access Point: Invalid", which Google suggests
> refers to the card being "off" and not to anything being wrong with the AP on
> the router.
>
> Has anyone any ideas??
>
> TIA
> Lisi
>
Lisi,
Some questions really.
Do you have HW Address filtering on the AP, and if so, have you added
the HW Address of the new card?
Once you've checked that, what mode are you using --- WPA2 ?
Do you have wpasupplicant installed and configured for the AP /
passphrase (if you're not using Network Manager).
Do you have "Restricted Modules' and the firmware installed ?
Currently my zd1211b card is sitting on the headless / wireless
Intrepid box (dangerous concept all round); to mitigate the risk of no
connectivity I have (no network manager):
/etc/network/interfaces:
auto wlan1
iface wlan1 inet dhcp
pre-up iwconfig wlan1 essid MY-WLAN
wpa-driver wext
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf
pre-up iwconfig wlan1 rate 24M
post-up iwconfig wlan1 rate auto
/etc/wpa_supplicant/wpa_supplicant.conf
network={
ssid="MY-WLAN"
key_mgmt=WPA-PSK
scan_ssid=1
psk="youllnevereverguessthis"
}
$ ls -lR /lib/firmware/zd*
-rw-r--r-- 1 root root 62484 2008-09-11 13:51 /lib/firmware/zd1201-ap.fw
-rw-r--r-- 1 root root 70612 2008-09-11 13:51 /lib/firmware/zd1201.fw
/lib/firmware/zd1211:
total 64
-rw-r--r-- 1 root root 4018 2008-09-11 13:40 zd1211b_ub
-rw-r--r-- 1 root root 5120 2008-09-11 13:40 zd1211b_uph
-rw-r--r-- 1 root root 5120 2008-09-11 13:40 zd1211b_uphm
-rw-r--r-- 1 root root 5120 2008-09-11 13:40 zd1211b_uphr
-rw-r--r-- 1 root root 3584 2008-09-11 13:40 zd1211b_ur
-rw-r--r-- 1 root root 4018 2008-09-11 13:40 zd1211_ub
-rw-r--r-- 1 root root 5120 2008-09-11 13:40 zd1211_uph
-rw-r--r-- 1 root root 5120 2008-09-11 13:40 zd1211_uphm
-rw-r--r-- 1 root root 5120 2008-09-11 13:40 zd1211_uphr
-rw-r--r-- 1 root root 3584 2008-09-11 13:40 zd1211_ur
And from dmesg:
[ 105.075496] firmware: requesting zd1211/zd1211b_ub
[ 105.175220] firmware: requesting zd1211/zd1211b_uphr
[ 105.287238] zd1211rw 4-1:1.0: firmware version 4725
[ 105.326899] zd1211rw 4-1:1.0: zd1211b chip 0ace:1215 v4810 high 00-16-e0 AL2230_RF pa0 ---NS
[ 106.774141] NET: Registered protocol family 17 [ 107.004054] wlan1: authenticate with AP xx:xx:xx:xx:xx:xx
[ 107.035062] wlan1: authenticated [ 107.035099] wlan1: associate with AP xx:xx:xx:xx:xx:xx
[ 107.038852] wlan1: RX AssocResp from xx:xx:xx:xx:xx:xx (capab=0x431 status=0 aid=6)
[ 107.038877] wlan1: associated
-jonathan
