[Klug-general] bt home hub2 - wireless connection problems

james morris james at jwm-art.net
Sat Dec 5 01:12:24 UTC 2009


Should mention:

iwconfig wlan0

does display the associated device as specified below and:

iwlist wlan0 scan

does list a number of wireless hubs in the area.

I am confused over the various different keys, "wep", "wireless key",
"wireless pin", "wpa"...

James.



On 5/12/2009, "james morris" <james at jwm-art.net> wrote:

>
>Hello,
>
>Got the broadband in linux via ethernet cable, but can't connect a
>laptop via wireless. Running Debian stable on laptop.
>
>sudo iwconfig wlan0 essid "BTHomeHub2-XXXX" key xxxxxxxx
>
>appears to do nothing. dmesg:
>
>[ 2615.308608] wlan0: Initial auth_alg=0
>[ 2615.308608] wlan0: authenticate with AP xx:xx:xx:xx:xx:xx
>[ 2615.318003] wlan0: RX authentication from xx:xx:xx:xx:xx:xx (alg=0
>transaction=2 status=0)
>[ 2615.318015] wlan0: authenticated
>[ 2615.318022] wlan0: associate with AP xx:xx:xx:xx:xx:xx
>[ 2615.319876] wlan0: RX AssocResp from xx:xx:xx:xx:xx:xx (capab=0x411
>status=12 aid=0)
>[ 2615.319888] wlan0: AP denied association (code=12)
>[ 2615.516564] wlan0: associate with AP xx:xx:xx:xx:xx:xx
>[ 2615.518545] wlan0: RX AssocResp from xx:xx:xx:xx:xx:xx (capab=0x411
>status=12 aid=0)
>[ 2615.518556] wlan0: AP denied association (code=12)
>[ 2615.716080] wlan0: associate with AP xx:xx:xx:xx:xx:xx
>[ 2615.719156] wlan0: RX AssocResp from xx:xx:xx:xx:xx:xx (capab=0x411
>status=12 aid=0)
>[ 2615.719156] wlan0: AP denied association (code=12)
>[ 2615.915524] wlan0: association with AP xx:xx:xx:xx:xx:xx timed out
>
>Don't know what that means. Got the cmdline from:
>(loosely followed Debian instructions)
>http://www.ingallegri.com/public/bthomehub/btrouter.html#Debian
>
>Laptop has Broadcom 4311 wireless - it needs some special firmware cutter
>thing and I believe it's working, but a "link not ready" msg appears
>after kernel msgs regarding it:
>
>[    9.791170] b43-phy0: Broadcom 4311 WLAN found
>[    9.866887] phy0: Selected rate control algorithm 'pid'
>[    9.954043] Broadcom 43xx driver loaded [ Features: PMLR, Firmware-ID:
>FW13 ]
>....
>[   25.076837] input: b43-phy0 as /class/input/input9
>[   25.180115] firmware: requesting b43/ucode5.fw
>[   25.244286] firmware: requesting b43/pcm5.fw
>[   25.325018] firmware: requesting b43/b0g0initvals5.fw
>[   25.386784] firmware: requesting b43/b0g0bsinitvals5.fw
>[   25.557337] b43-phy0: Loading firmware version 410.2160 (2007-05-26
>15:32:10)
>[   26.904518] Registered led device: b43-phy0::tx
>[   26.904630] Registered led device: b43-phy0::rx
>[   26.904727] Registered led device: b43-phy0::radio
>[   26.960018] ADDRCONF(NETDEV_UP): wlan0: link is not ready
>[   26.991049] ADDRCONF(NETDEV_UP): eth0: link is not ready
>
>At a bit of a loss as this networking malarky is all new to me. Any help
>appreciated.
>
>Cheers,
>James.
>
>_______________________________________________
>Kent mailing list
>Kent at mailman.lug.org.uk
>https://mailman.lug.org.uk/mailman/listinfo/kent
>



More information about the Kent mailing list