Find the answer to your Linux question:
Results 1 to 5 of 5
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Linux Enthusiast
    Join Date
    Apr 2004
    Location
    UK
    Posts
    747

    WLAN direct probe leads to authentication timeout.


    I'm having wireless problems. Technically they are intermittent, but I'm ending up with more problems than not.

    I'm in a hotel right now and the network works just fine, so I don't think there are hardware issues. Same device, WPA2/CCMP, same drivers.

    I've found the logs when it works look like the following

    Code:
    Mar 21 15:33:11 magrat kernel: [    4.707757] wlan0: authenticate with 22:aa:4b:00:9c:1e
    Mar 21 15:33:11 magrat kernel: [    4.707851] wlan0: send auth to 22:aa:4b:00:9c:1e (try 1/3)
    Mar 21 15:33:11 magrat kernel: [    4.713059] wlan0: authenticated
    (this is a connection at the hotel)

    When I'm at the office I find two options:

    Code:
    Mar 21 14:59:07 magrat kernel: [  508.108040] wlan0: authenticate with <snip>
    Mar 21 14:59:07 magrat kernel: [  508.108171] wlan0: direct probe to <snip> (try 1/3)
    Mar 21 14:59:07 magrat kernel: [  508.311230] wlan0: direct probe to <snip> (try 2/3)
    Mar 21 14:59:07 magrat kernel: [  508.515560] wlan0: direct probe to <snip> (try 3/3)
    Mar 21 14:59:07 magrat kernel: [  508.719335] wlan0: authentication with <snip> timed out
    This fails, and keeps failing. But sometimes I get the following and it springs to life:

    Code:
    Mar 21 10:13:18 magrat kernel: [ 6841.886224] wlan0: authenticate with <snip>
    Mar 21 10:13:18 magrat kernel: [ 6841.886437] wlan0: direct probe to <snip> (try 1/3)
    Mar 21 10:13:18 magrat kernel: [ 6842.088715] wlan0: direct probe to <snip> (try 2/3)
    Mar 21 10:13:19 magrat kernel: [ 6842.292801] wlan0: send auth to <snip> (try 3/3)
    Mar 21 10:13:19 magrat kernel: [ 6842.295441] wlan0: authenticated
    (the BSSID I've snipped is the same value in all messages. I'm ok with you knowing where I'm staying, but not where I'm working!)

    Edit: Additional, seemingly pertinent information:

    The office has multiple access points. So does the hotel, but there have been reports of intel drivers fluttering between APs and not authenticating with either.
    Code:
    lspci -vvv -s 2:0.0
    02:00.0 Network controller: Broadcom Corporation BCM43225 802.11b/g/n (rev 01)
    	Subsystem: Hewlett-Packard Company Device 145e
    	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
    	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
    	Latency: 0, Cache Line Size: 64 bytes
    	Interrupt: pin A routed to IRQ 16
    	Region 0: Memory at da100000 (64-bit, non-prefetchable) [size=16K]
    	Capabilities: <access denied>
    	Kernel driver in use: bcma-pci-bridge
    not an intel card here.

    So the direct probe seems to not work and not be necessary. Is there any way I can force it to always "send auth"?

    Thanks,
    Last edited by kakariko81280; 03-21-2015 at 04:45 PM.
    To be good, you must first be bad. "Newbie" is a rank, not a slight.

  2. #2
    Linux Enthusiast
    Join Date
    Apr 2004
    Location
    UK
    Posts
    747
    Today's update:

    I swapped to the wl driver.

    Code:
    lspci -s 2:0.0 -v
    02:00.0 Network controller: Broadcom Corporation BCM43225 802.11b/g/n (rev 01)
    	Subsystem: Hewlett-Packard Company Device 145e
    	Flags: bus master, fast devsel, latency 0, IRQ 16
    	Memory at da100000 (64-bit, non-prefetchable) [size=16K]
    	Capabilities: <access denied>
    	Kernel driver in use: wl
    Which worked great at the hotel but had similar symptoms at the office. Different errors though:

    Code:
    ERROR @wl_cfg80211_get_station : Wrong Mac address
    and
    Code:
    CTRL-EVENT-ASSOC-REJECT status_code=16
    I also noted that the network I'm trying to connect to has an AP with a BSSID id of 00:00:00:00:00:00 in iwlist, which I'm sure isn't good.

    I seem to have managed to work around them by specifying my MAC address in the user defined MAC address field, and the BSSID I want to connect to in NetworkManager.

    If it lasts all week I'll mark it as solved, but I'd still appreciate some input on what I can look for at this network that's giving me trouble.

    Thanks,

    Edit:

    And I just got done posting this when the connection packed up again. It re-established itself very quickly, but apparently not fast enough because the network captive portal popped up again and disconnected my VPN. I'm reading this as errors rather than this network boots guests every hour so I seem to still have problems, but it's something to run past tech support here, just in case.
    To be good, you must first be bad. "Newbie" is a rank, not a slight.

  3. #3
    Linux Enthusiast
    Join Date
    Apr 2004
    Location
    UK
    Posts
    747
    Linux WiFi Reason Codes - Disconnection & De-Authentication Issues

    This seems pretty handy. Posting for future reference.
    To be good, you must first be bad. "Newbie" is a rank, not a slight.

  4. $spacer_open
    $spacer_close
  5. #4
    Linux Enthusiast
    Join Date
    Apr 2004
    Location
    UK
    Posts
    747
    Next update. new versions of the wl drivers don't seem to help much. Investigations with ndiswrapper got nowhere when I couldn't get a non-self-extracting exe version of the driver. Most frustrating.

    I'd like to say the 00:00:00:00:00:00 AP didn't really exist and was a bug in the driver.

    On the other hand, the people who work in the building confirm the supplied wifi isn't that reliable so it's not just my computer.

    Tomorrow is the last day so I won't be able to try any new tests to see if I can work out where the problem is. Consider this one unresolved.
    To be good, you must first be bad. "Newbie" is a rank, not a slight.

  6. #5
    Linux Enthusiast
    Join Date
    Apr 2004
    Location
    UK
    Posts
    747
    -->
    Linux Wifi: A guide to tuning your wifi for adverse conditions.

    More handy information. Increasing packet fragmentation didn't seem to help. I suppose that's only any use *after* the connection has been established.
    To be good, you must first be bad. "Newbie" is a rank, not a slight.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •