Authentication/Regulatory Domain issues - ath5k - 12.2

antttikutoja · February 17, 2013, 7:16pm

I have an Atheros wireless card in an old siemens amilo laptop.

I installed 12.2 and it chose the ath5k driver for it.

When attempting to connect to the AP, the authentication times out repeatedly and no connection can be made.

During boot, I see the messages: “ath: Country alpha2 being used: AM” followed by “cfg80211: Calling CRDA for country: AM”.

I inserted “options cfg80211 ieee80211_regdom=FI” into /etc/modprobe.d/00-systerm.conf and re-booted.

Saw during boot that cgf80211 set the country code to FI via CRDA but this was followed just after by the ath: message as above. Still Authentication times out.

Now, AM is Armenia no? WTF!

Whilst this was going on, I do iw reg get and it reported the country as 98 followed by the various frequencies. I then did iw reg set FI and saw in the log that cfg80211 changed the country to 98. At this point iw reg get and it reported country 00.

Messages in the log indicate that cfg80211 is repeatedly calling CRDA to change the country to 97! However, iw reg get is still reporting country as 00.

Authentication is still timing out so I am getting nowhere.

Is this a “OLD_REG” vs “NEW_REG” issue? Is it the driver? I can’t find a driver module option that affects the regulatory domain.

On another box with a ralink usb wireless nic, all I see during boot is a message from cfg80211 that it is calling CRDA to change the country code and iw reg get gives country 00. Needless to say, the wlan is up and running sweetly.

I checked and double-check the passphrase and it’s correct. I even copied the working box’s ifcfg-wlan0 file over so they are identical.

During authentication. I see in the log: wlan0: direct probe to MAC ADDRESS (try n/3) 3 times then the time out message. The MAC address it is doing its direct probe on is indeed the MAC of the router. The repeated call by cfg80211 only started happening after I had issued the iw reg set FI and now preceed every attempt by the card to authenticate. iw reg get still shows country as 00.

Any clues?

Cheers - AK

knurpht · February 17, 2013, 10:11pm

Hard to follow what you’ve done. Why not use Yast, and have it’s networkmodule do the job. A thing to consider: turning off ipv6.

lwfinger · February 17, 2013, 10:15pm

On 02/17/2013 12:26 PM, antttikutoja wrote:
>
> I have an Atheros wireless card in an old siemens amilo laptop.
>
> I installed 12.2 and it chose the ath5k driver for it.
>
> When attempting to connect to the AP, the authentication times out
> repeatedly and no connection can be made.
>
> During boot, I see the messages: “ath: Country alpha2 being used: AM”
> followed by “cfg80211: Calling CRDA for country: AM”.
>
> I inserted “options cfg80211 ieee80211_regdom=FI” into
> /etc/modprobe.d/00-systerm.conf and re-booted.
>
> Saw during boot that cgf80211 set the country code to FI via CRDA but
> this was followed just after by the ath: message as above. Still
> Authentication times out.
>
> Now, AM is Armenia no? WTF!

I recently found that the ath9k_htc driver will not override the CN setting in
its EEPROM even though I am loading cfg80211 with “ieee80211_regdom=US”. In my
case, the main difference is that channels 12 and 13 are allowed even though
local regulations prevent using them. I have not yet discussed this issue with
the Atheros engineers.

Please post the lines from the dmesg output that look like this:


cfg80211: Calling CRDA for country: US
cfg80211: Regulatory domain changed to country: US
cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
cfg80211:   (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
cfg80211:   (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
cfg80211:   (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)

Please post the lines inside code tags. You should have 2 sets - 1 for FI and
another for AM. In addition, describe what channel you are trying to use.

I would not expect the differences between FI and AM to be that significant,
particularly for the 2.4 GHz band. I suspect some other problem in your setup.

antttikutoja · February 18, 2013, 10:13am

knurpht.

I did use yast to configure the card in the first place. I subsequently checked ifcfg-wlan0 to see what I had given as the passphrase. It was fine. I used the copy from the other box just to see if I had messed up something.

The card comes up exactly as I want and in line with the yast settings. That is, if the wired connection is available, use it and don’t bring up the wireless. If the wired connection is not available, bring up the wireless.

I always disable both Network Manager and IPV6.

finger. Will do that later today when I can get my hands on the box again.

Cheers - AK

antttikutoja · February 18, 2013, 5:12pm

Hi finger.

Here is the dmesg stuff.

Here is the dialogue for the whole ath start-up. It looks like ath gets there first. Does the 30 mean 0x30 regdom for ETSI? Don’t know where it gets the country from AM is Armenia. It might be in the same timezone as EET. Then comes my module option for cfg80211 quickly overidden by something else. I assume it’s ath but it already seemed to do that.

The frequencies shown by the first set of cfg802 messages is similar but not the same as the FI settings and then the AM settings are different from the first lot.


   22.502730] ath: EEPROM indicates we should expect a direct regpair map
   22.502735] ath: Country alpha2 being used: AM
   22.502737] ath: Regpair used: 0x30
   23.124978] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
   23.125489] ath5k phy0: Atheros AR2413 chip found (MAC: 0x78, PHY: 0x45)
   23.176195] firewire_ohci 0000:02:0b.2: added OHCI v1.10 device as card 0, 4 IR + 8 IT contexts, quirks 0x2
   23.677243] firewire_core 0000:02:0b.2: created device fw0: GUID 0000000000000000, S400
   23.987090] cfg80211: World regulatory domain updated:
   23.987172] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
   23.987256] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
   23.987337] cfg80211:   (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
   23.987420] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
   23.987501] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
   23.987581] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
   23.987680] cfg80211: Calling CRDA for country: FI
   23.993338] cfg80211: Regulatory domain changed to country: FI
   23.993426] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
   23.993510] cfg80211:   (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
   23.993587] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (N/A, 2000 mBm)
   23.993667] cfg80211:   (5250000 KHz - 5330000 KHz @ 40000 KHz), (N/A, 2000 mBm)
   23.993745] cfg80211:   (5490000 KHz - 5710000 KHz @ 40000 KHz), (N/A, 2700 mBm)
   23.993848] cfg80211: Calling CRDA for country: AM
   23.999248] cfg80211: Current regulatory domain intersected:
   23.999333] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
   23.999416] cfg80211:   (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
   23.999495] cfg80211:   (5170000 KHz - 5250000 KHz @ 20000 KHz), (N/A, 1800 mBm)
   23.999572] cfg80211:   (5250000 KHz - 5330000 KHz @ 20000 KHz), (N/A, 1800 mBm)

Later on in dmesg I see:


   53.503709] wlan0: authenticate with cc:5d:4e:29:d9:44
   53.515164] wlan0: direct probe to cc:5d:4e:29:d9:44 (try 1/3)
   53.716067] wlan0: direct probe to cc:5d:4e:29:d9:44 (try 2/3)
   53.917091] wlan0: direct probe to cc:5d:4e:29:d9:44 (try 3/3)
   54.118090] wlan0: authentication with cc:5d:4e:29:d9:44 timed out
   55.067627] wlan0: authenticate with cc:5d:4e:29:d9:44
   55.086743] wlan0: direct probe to cc:5d:4e:29:d9:44 (try 1/3)
   55.287058] wlan0: direct probe to cc:5d:4e:29:d9:44 (try 2/3)
   55.488070] wlan0: direct probe to cc:5d:4e:29:d9:44 (try 3/3)

Here’s what happens when I use iw from the CLI:


AKUPAKKU:/home/aku # iw reg get
country 98:
        (2402 - 2482 @ 40), (N/A, 20)
        (5170 - 5250 @ 20), (N/A, 18)
        (5250 - 5330 @ 20), (N/A, 18), DFS

This matches the final cfg802 messages. Does the "intersected" message mean that these are common values?

AKUPAKKU:/home/aku # iw reg set FI
AKUPAKKU:/home/aku # iw reg get
country 00:
        (2402 - 2472 @ 40), (3, 20)
        (2457 - 2482 @ 20), (3, 20), PASSIVE-SCAN, NO-IBSS
        (2474 - 2494 @ 20), (3, 20), NO-OFDM, PASSIVE-SCAN, NO-IBSS
        (5170 - 5250 @ 40), (3, 20), PASSIVE-SCAN, NO-IBSS
        (5735 - 5835 @ 40), (3, 20), PASSIVE-SCAN, NO-IBSS

These are somewhat different again. Country shown as zero (ISO 3166, Finland = 246) but could it be a regdom of 0x00 which is wildcard? 

The values do correspond to the values I get from the box that is working fine.

There follows a section of the log after I’ve done the cli stuff. I noted that if I do not do any CLI stuff, I do not see all the calls to CRDA/cfg80211 so doing iw reg set FI has put some cats among those pigeons. Also, I see it is setting country = 97 when my original iw reg get showed 98. This sequence of messages is repeated continuosly.


Feb 18 16:22:54 AKUPAKKU kernel:   928.616075] cfg80211: Calling CRDA to update world regulatory domain
Feb 18 16:22:54 AKUPAKKU kernel:   928.621248] cfg80211: World regulatory domain updated:
Feb 18 16:22:54 AKUPAKKU kernel:   928.621256] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Feb 18 16:22:54 AKUPAKKU kernel:   928.621260] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Feb 18 16:22:54 AKUPAKKU kernel:   928.621265] cfg80211:   (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Feb 18 16:22:54 AKUPAKKU kernel:   928.621269] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Feb 18 16:22:54 AKUPAKKU kernel:   928.621273] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Feb 18 16:22:54 AKUPAKKU kernel:   928.621277] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Feb 18 16:22:54 AKUPAKKU kernel:   928.621419] cfg80211: Calling CRDA for country: 97
Feb 18 16:22:54 AKUPAKKU kernel:   928.624069] wlan0: authentication with cc:5d:4e:29:d9:44 timed out
Feb 18 16:22:54 AKUPAKKU kernel:   929.562640] wlan0: authenticate with cc:5d:4e:29:d9:44
Feb 18 16:22:54 AKUPAKKU kernel:   929.567608] wlan0: direct probe to cc:5d:4e:29:d9:44 (try 1/3)
Feb 18 16:22:55 AKUPAKKU kernel:   929.768023] wlan0: direct probe to cc:5d:4e:29:d9:44 (try 2/3)
Feb 18 16:22:55 AKUPAKKU kernel:   929.969028] wlan0: direct probe to cc:5d:4e:29:d9:44 (try 3/3)
Feb 18 16:22:52 AKUPAKKU kernel:   927.078029] wlan0: authentication with cc:5d:4e:29:d9:44 timed out
Feb 18 16:22:53 AKUPAKKU dhcpcd[2160]: wlan0: timed out
Feb 18 16:22:53 AKUPAKKU kernel:   928.016693] wlan0: authenticate with cc:5d:4e:29:d9:44
Feb 18 16:22:53 AKUPAKKU kernel:   928.021585] wlan0: direct probe to cc:5d:4e:29:d9:44 (try 1/3)
Feb 18 16:22:53 AKUPAKKU dhcpcd[2160]: wlan0: trying to use old lease in `/var/lib/dhcpcd/dhcpcd-wlan0.info'
Feb 18 16:22:53 AKUPAKKU dhcpcd[2160]: wlan0: lease expired 207043 seconds ago
Feb 18 16:22:53 AKUPAKKU dhcpcd[2160]: wlan0: broadcasting for a lease
Feb 18 16:22:53 AKUPAKKU kernel:   928.222027] wlan0: direct probe to cc:5d:4e:29:d9:44 (try 2/3)
Feb 18 16:22:53 AKUPAKKU kernel:   928.423024] wlan0: direct probe to cc:5d:4e:29:d9:44 (try 3/3)
Feb 18 16:22:54 AKUPAKKU kernel:   928.616075] cfg80211: Calling CRDA to update world regulatory domain
Feb 18 16:22:54 AKUPAKKU kernel:   928.621248] cfg80211: World regulatory domain updated:
Feb 18 16:22:54 AKUPAKKU kernel:   928.621256] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Feb 18 16:22:54 AKUPAKKU kernel:   928.621260] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Feb 18 16:22:54 AKUPAKKU kernel:   928.621265] cfg80211:   (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Feb 18 16:22:54 AKUPAKKU kernel:   928.621269] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Feb 18 16:22:54 AKUPAKKU kernel:   928.621419] cfg80211: Calling CRDA for country: 97
Feb 18 16:22:54 AKUPAKKU kernel:   928.624069] wlan0: authentication with cc:5d:4e:29:d9:44 timed out
Feb 18 16:22:54 AKUPAKKU kernel:   929.562640] wlan0: authenticate with cc:5d:4e:29:d9:44
Feb 18 16:22:54 AKUPAKKU kernel:   929.567608] wlan0: direct probe to cc:5d:4e:29:d9:44 (try 1/3)
Feb 18 16:22:55 AKUPAKKU kernel:   929.768023] wlan0: direct probe to cc:5d:4e:29:d9:44 (try 2/3)
Feb 18 16:22:55 AKUPAKKU kernel:   929.969028] wlan0: direct probe to cc:5d:4e:29:d9:44 (try 3/3)
Feb 18 16:22:55 AKUPAKKU kernel:   930.170168] wlan0: authentication with cc:5d:4e:29:d9:44 timed out

Cheers - AK.

antttikutoja · February 18, 2013, 5:26pm

Sorry finger. You also asked what channel I am using. The router is set to “auto” and says it is currently using channel 13.

Cheers - AK

antttikutoja · February 18, 2013, 7:07pm

finger.

Here is the results of iwlist scan. I have often to try several times to get a result, I guess it just depends on what state the card is in at the time.


          Cell 03 - Address: CC:5D:4E:29:D9:44
                    Channel:13
                    Frequency:2.472 GHz (Channel 13)
                    Quality=57/70  Signal level=-53 dBm
                    Encryption key:on
                    ESSID:"BATCAVE"
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 9 Mb/s
                              18 Mb/s; 36 Mb/s; 54 Mb/s
                    Bit Rates:6 Mb/s; 12 Mb/s; 24 Mb/s; 48 Mb/s
                    Mode:Master
                    Extra:tsf=0000000274f2f13a
                    Extra: Last beacon: 103ms ago
                    IE: Unknown: 000742415443415645
                    IE: Unknown: 010882848B961224486C
                    IE: Unknown: 03010D
                    IE: Unknown: 32040C183060
                    IE: Unknown: 33082001020304050607
                    IE: Unknown: 33082105060708090A0B
                    IE: Unknown: 050400010000
                    IE: Unknown: 2A0100
                    IE: Unknown: 2D1AEE1117FF000000010000000000000000000000000C0000000000
                    IE: Unknown: 3D160D070400000000000000000000000000000000000000
                    IE: Unknown: 7F0101
                    IE: IEEE 802.11i/WPA2 Version 1
                        Group Cipher : CCMP
                        Pairwise Ciphers (1) : CCMP
                        Authentication Suites (1) : PSK
                    IE: Unknown: DD180050F2020101800003A4000027A4000042435E0062322F00
                    IE: Unknown: 0B05010001127A
                    IE: Unknown: DD1E00904C33EE1117FF000000010000000000000000000000000C00000
00000
                    IE: Unknown: DD1A00904C340D070400000000000000000000000000000000000000
                    IE: Unknown: DD07000C4307000000

2472 is within the range being used right? The card seems to pick up the channel 13 bit as well. There are two other cells that it picks up as well. Two are on the same frequency different from 2472 and they are both using channel 1.

Hope this is useful.

lwfinger · February 18, 2013, 7:41pm

On 02/18/2013 10:16 AM, antttikutoja wrote:
> 22.502730] ath: EEPROM indicates we should expect a direct regpair map
> 22.502735] ath: Country alpha2 being used: AM

That is the value encoded into your device. Channel 13 is at 2472000 KHz, thus I
have deleted the 5 GHz lines below.

> 23.987090] cfg80211: World regulatory domain updated:
> 23.987172] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
> 23.987256] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
> 23.987337] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
> 23.987420] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
> 23.987680] cfg80211: Calling CRDA for country: FI
> 23.993338] cfg80211: Regulatory domain changed to country: FI
> 23.993426] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
> 23.993510] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
> 23.993848] cfg80211: Calling CRDA for country: AM
> 23.999248] cfg80211: Current regulatory domain intersected:
> 23.999333] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
> 23.999416] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)

The intersected domain is the values common to AM and FI (think of a Venn
diagram), and it says that channel 13 should be OK, even with 40 MHz channels;
although I’m not sure of HT40+ on channel 13. As you can see, there is no
difference between the AM and FI data for your channel. Is it possible to change
that AP to use a fixed channel of 11? That would be the test.

The rest of the dmesg output says that authentication is failing. That usually
means that the secret is wrong. If you are sure that you have it right, perhaps
trying a different channel will work.

antttikutoja · February 18, 2013, 8:48pm

finger.

Changed the router to channel 11. No different. The box that’s running comes up still with no problems.

I’ve re-checked /etc/sysconfig/network/ifcfg-wlan0 and the secret is spot on. In fact, it’s a copy of the same file on the box that is running.

What I’m going to do now is change the router chanel from 1 through all it’s got and try that.

If that bombs, I will delete the interface via yast and try to set it up again. On another thread, I have been “*****ing” about how yast shows me what it last saw I gave it rather than what is actually in the underlying config file and maybe thjis is one of those situations and, further, the interface is being configured from somewhere else than ifcfg-wlan0 and there is a mistake in wherever that file is.

Will report back.

Thanks so much for your help. This wireless stuff tech is trickier than I thought but it’s like “whatever breaks, gives you the opportunity to learn”.

Cheers - AK.

antttikutoja · February 18, 2013, 9:45pm

finger.

I assume that I didn’t have to reboot after every channel change right? The box that runs seemed to cope with the channel changes OK. I did notice some slight variations with ping times using different channels but I can look into that later on.

No change on channel change what ever channel I used.

I went back to yast. I moved the existing ifcfg-wlan0 out of the way and re-defined the interface.

Afterwards, the interface could not be brought up because of RFKILL (in the log). rfkill list showed a hard block on the wlan. That usually indicates that the switch is on so I toggled it and rfkill list still showed a hard block. Tried to unlock all and unlock specific but it stubbornly refused to changed.

I checked ifcfg-wlan0 at this point and it was good. That is, the secret was correct.

rfkill list after reboot shows no block but still not able to authenticate. If it is blocked it doesn’t even want tio come up so…

I can try to reboot after each channel change. I guess it’s the only other thing left. It’s annoying because I know this box used to run XP and its wlan was fine.

I’ve checked the log on the router but it doesn’t give any kind of detail. Oh! I have just seen a new message there.

After every channel change, it says " WLAN[2.4G], CountryRegion = 1". Is this significant?

The box that’s running always reports regdom as country 00 (iw reg get) so do you think the fact that this box is insisting on 98 is an issue. 98 reports a range of 2402 - 2482 and then in 5 range. The channels on the router are all in the 24 range from 2412 through to 2472.

Cheers - AK

lwfinger · February 18, 2013, 9:36pm

On 02/18/2013 01:56 PM, antttikutoja wrote:
>
> finger.
>
> Changed the router to channel 11. No different. The box that’s running
> comes up still with no problems.
>
> I’ve re-checked /etc/sysconfig/network/ifcfg-wlan0 and the secret is
> spot on. In fact, it’s a copy of the same file on the box that is
> running.
>
> What I’m going to do now is change the router chanel from 1 through all
> it’s got and try that.

That will be a waste of time.

> If that bombs, I will delete the interface via yast and try to set it
> up again. On another thread, I have been “*****ing” about how yast shows
> me what it last saw I gave it rather than what is actually in the
> underlying config file and maybe thjis is one of those situations and,
> further, the interface is being configured from somewhere else than
> ifcfg-wlan0 and there is a mistake in wherever that file is.

The only file is ifcfg-wlan0. Post it here with secret obscured.

> Will report back.
>
> Thanks so much for your help. This wireless stuff tech is trickier than
> I thought but it’s like “whatever breaks, gives you the opportunity to
> learn”.

The trickiness of wireless stuff is the reason we recommend NetworkManager.

antttikutoja · February 18, 2013, 9:49pm

Sorry to prattle but. Is the timeout the standard behaviour for failing the secret? The router just ignores the request?

lwfinger · February 18, 2013, 10:05pm

On 02/18/2013 02:46 PM, antttikutoja wrote:
>
> finger.
>
> I assume that I didn’t have to reboot after every channel change right?
> The box that runs seemed to cope with the channel changes OK. I did
> notice some slight variations with ping times using different channels
> but I can look into that later on.
>
> No change on channel change what ever channel I used.
>
> I went back to yast. I moved the existing ifcfg-wlan0 out of the way
> and re-defined the interface.
>
> Afterwards, the interface could not be brought up because of RFKILL (in
> the log). rfkill list showed a hard block on the wlan. That usually
> indicates that the switch is on so I toggled it and rfkill list still
> showed a hard block. Tried to unlock all and unlock specific but it
> stubbornly refused to changed.
>
> I checked ifcfg-wlan0 at this point and it was good. That is, the
> secret was correct.
>
> rfkill list after reboot shows no block but still not able to
> authenticate. If it is blocked it doesn’t even want tio come up so…
>
> I can try to reboot after each channel change. I guess it’s the only
> other thing left. It’s annoying because I know this box used to run XP
> and its wlan was fine.

That only indicates that the hardware is OK - nothing more.

> I’ve checked the log on the router but it doesn’t give any kind of
> detail. Oh! I have just seen a new message there.
>
> After every channel change, it says " WLAN[2.4G], CountryRegion = 1".
> Is this significant?

How should I know? I have no idea what router you are using, or any of the
details of its programming.

> The box that’s running always reports regdom as country 00 (iw reg get)
> so do you think the fact that this box is insisting on 98 is an issue.
> 98 reports a range of 2402 - 2482 and then in 5 range. The channels on
> the router are all in the 24 range from 2412 through to 2472.

No, I don’t think that is the problem, but if you are worried, stop trying to
force FI. As the rules are the same for AM and FI, it should not make a difference.

antttikutoja · February 18, 2013, 10:28pm

Hi finger.

Yes, it was!

here is the ifcfg-wlan0 before I deleted the interface and re-defined it via yast.


BOOTPROTO='dhcp'
DEVICE='wlan0'
BROADCAST=''
ETHTOOL_OPTIONS=''
IPADDR=''
MTU='4096'
NAME=''
NETMASK=''
NETWORK=''
REMOTE_IPADDR=''
STARTMODE='ifplugd'
IFPLUGD_PRIORITY='1'
USERCONTROL='no'
WIRELESS_AP=''
WIRELESS_AP_SCANMODE='1'
WIRELESS_AUTH_MODE='psk'
WIRELESS_BITRATE='auto'
WIRELESS_CA_CERT=''
WIRELESS_CHANNEL=''
WIRELESS_CLIENT_CERT=''
WIRELESS_CLIENT_KEY=''
WIRELESS_CLIENT_KEY_PASSWORD=''
WIRELESS_DEFAULT_KEY='0'
WIRELESS_EAP_AUTH=''
WIRELESS_EAP_MODE=''
WIRELESS_ESSID='BATCAVE'
WIRELESS_FREQUENCY=''
WIRELESS_KEY=''
WIRELESS_KEY_0=''
WIRELESS_KEY_1=''
WIRELESS_KEY_2=''
WIRELESS_KEY_3=''
WIRELESS_KEY_LENGTH='128'
WIRELESS_MODE='Managed'
WIRELESS_NICK=''
WIRELESS_NWID=''
WIRELESS_PEAP_VERSION=''
WIRELESS_POWER='yes'
WIRELESS_WPA_ANONID=''
WIRELESS_WPA_IDENTITY=''
WIRELESS_WPA_PASSWORD=''
WIRELESS_WPA_PSK='****************'

Here is the one after I had deleted and re-defined the interface.


BOOTPROTO='dhcp'
BROADCAST=''
ETHTOOL_OPTIONS=''
IFPLUGD_PRIORITY='0'
IPADDR=''
MTU=''
NAME='AR2413 802.11bg NIC'
NETMASK=''
NETWORK=''
REMOTE_IPADDR=''
STARTMODE='ifplugd'
USERCONTROL='no'
WIRELESS_AP=''
WIRELESS_AP_SCANMODE='1'
WIRELESS_AUTH_MODE='psk'
WIRELESS_BITRATE='auto'
WIRELESS_CA_CERT=''
WIRELESS_CHANNEL=''
WIRELESS_CLIENT_CERT=''
WIRELESS_CLIENT_KEY=''
WIRELESS_CLIENT_KEY_PASSWORD=''
WIRELESS_DEFAULT_KEY='0'
WIRELESS_EAP_AUTH=''
WIRELESS_EAP_MODE=''
WIRELESS_ESSID='BATCAVE'
WIRELESS_FREQUENCY=''
WIRELESS_KEY=''
WIRELESS_KEY_0=''
WIRELESS_KEY_1=''
WIRELESS_KEY_2=''
WIRELESS_KEY_3=''
WIRELESS_KEY_LENGTH='128'
WIRELESS_MODE='Managed'
WIRELESS_NICK=''
WIRELESS_NWID=''
WIRELESS_PEAP_VERSION=''
WIRELESS_POWER='no'
WIRELESS_WPA_ANONID=''
WIRELESS_WPA_IDENTITY=''
WIRELESS_WPA_PASSWORD=''
WIRELESS_WPA_PSK='****************'

Point taken re Network Manager. I’d be interested in how it solves this problem.

Cheers - AK

lwfinger · February 19, 2013, 1:12am

On 02/18/2013 03:36 PM, antttikutoja wrote:
>
> Point taken re Network Manager. I’d be interested in how it solves this
> problem.

It avoids needing to create ifcfg-xxxx and uses dbus to write the necessary
parameters into the programs that need them. It knows what is critical and
avoids all the pitfalls. You will read a lot of criticism of NM in the lists;
however, it works for me, even though I know how to write the ifcfg-xxxx files.

antttikutoja · February 19, 2013, 4:33pm

Changed the setup to use Network Manager. Still, the wireless fails to connect.

Here is the log (NetworkManager)


Feb 19 17:09:02 AKUPAKKU NetworkManager[1285]: <info> Auto-activating connection 'BATCAVE'.
Feb 19 17:09:05 AKUPAKKU NetworkManager[1285]: <info> Activation (wlan0) starting connection 'BATCAVE'
Feb 19 17:09:05 AKUPAKKU NetworkManager[1285]: <info> (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Feb 19 17:09:05 AKUPAKKU NetworkManager[1285]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Feb 19 17:09:05 AKUPAKKU NetworkManager[1285]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Feb 19 17:09:06 AKUPAKKU NetworkManager[1285]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Feb 19 17:09:06 AKUPAKKU NetworkManager[1285]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Feb 19 17:09:06 AKUPAKKU NetworkManager[1285]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Feb 19 17:09:06 AKUPAKKU NetworkManager[1285]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Feb 19 17:09:06 AKUPAKKU NetworkManager[1285]: <info> Activation (wlan0/wireless): access point 'BATCAVE' has security, but secrets are required.
Feb 19 17:09:06 AKUPAKKU NetworkManager[1285]: <info> (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0]
Feb 19 17:09:06 AKUPAKKU NetworkManager[1285]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Feb 19 17:09:06 AKUPAKKU NetworkManager[1285]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Feb 19 17:09:06 AKUPAKKU NetworkManager[1285]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Feb 19 17:09:06 AKUPAKKU NetworkManager[1285]: <info> (wlan0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
Feb 19 17:09:06 AKUPAKKU NetworkManager[1285]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Feb 19 17:09:06 AKUPAKKU NetworkManager[1285]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Feb 19 17:09:06 AKUPAKKU NetworkManager[1285]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Feb 19 17:09:06 AKUPAKKU NetworkManager[1285]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Feb 19 17:09:06 AKUPAKKU NetworkManager[1285]: <info> Activation (wlan0/wireless): connection 'BATCAVE' has security, and secrets exist.  No new secrets needed.
Feb 19 17:09:06 AKUPAKKU NetworkManager[1285]: <info> Config: added 'ssid' value 'BATCAVE'
Feb 19 17:09:06 AKUPAKKU NetworkManager[1285]: <info> Config: added 'scan_ssid' value '1'
Feb 19 17:09:06 AKUPAKKU NetworkManager[1285]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
Feb 19 17:09:06 AKUPAKKU NetworkManager[1285]: <info> Config: added 'psk' value '<omitted>'
Feb 19 17:09:06 AKUPAKKU NetworkManager[1285]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Feb 19 17:09:06 AKUPAKKU NetworkManager[1285]: <info> Config: set interface ap_scan to 1
Feb 19 17:09:06 AKUPAKKU NetworkManager[1285]: <info> (wlan0): supplicant interface state: inactive -> scanning
Feb 19 17:09:07 AKUPAKKU NetworkManager[1285]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Feb 19 17:09:08 AKUPAKKU NetworkManager[1285]: <info> (wlan0): supplicant interface state: authenticating -> disconnected
Feb 19 17:09:08 AKUPAKKU NetworkManager[1285]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Feb 19 17:09:09 AKUPAKKU NetworkManager[1285]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Feb 19 17:09:09 AKUPAKKU NetworkManager[1285]: <info> (wlan0): supplicant interface state: authenticating -> disconnected
Feb 19 17:09:09 AKUPAKKU NetworkManager[1285]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Feb 19 17:09:10 AKUPAKKU NetworkManager[1285]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Feb 19 17:09:11 AKUPAKKU NetworkManager[1285]: <info> (wlan0): supplicant interface state: authenticating -> disconnected
Feb 19 17:09:11 AKUPAKKU NetworkManager[1285]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Feb 19 17:09:12 AKUPAKKU NetworkManager[1285]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Feb 19 17:09:12 AKUPAKKU NetworkManager[1285]: <info> (wlan0): supplicant interface state: authenticating -> disconnected
Feb 19 17:09:13 AKUPAKKU NetworkManager[1285]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Feb 19 17:09:13 AKUPAKKU NetworkManager[1285]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Feb 19 17:09:14 AKUPAKKU NetworkManager[1285]: <info> (wlan0): supplicant interface state: authenticating -> disconnected
Feb 19 17:09:14 AKUPAKKU NetworkManager[1285]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Feb 19 17:09:15 AKUPAKKU NetworkManager[1285]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Feb 19 17:09:15 AKUPAKKU NetworkManager[1285]: <info> (wlan0): supplicant interface state: authenticating -> disconnected
Feb 19 17:09:16 AKUPAKKU NetworkManager[1285]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Feb 19 17:09:16 AKUPAKKU NetworkManager[1285]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Feb 19 17:09:17 AKUPAKKU NetworkManager[1285]: <info> (wlan0): supplicant interface state: authenticating -> disconnected
Feb 19 17:09:17 AKUPAKKU NetworkManager[1285]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Feb 19 17:09:18 AKUPAKKU NetworkManager[1285]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Feb 19 17:09:19 AKUPAKKU NetworkManager[1285]: <info> (wlan0): supplicant interface state: authenticating -> disconnected
Feb 19 17:09:19 AKUPAKKU NetworkManager[1285]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Feb 19 17:09:31 AKUPAKKU NetworkManager[1285]: <warn> Activation (wlan0/wireless): association took too long.
Feb 19 17:09:31 AKUPAKKU NetworkManager[1285]: <info> (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0]
Feb 19 17:09:31 AKUPAKKU NetworkManager[1285]: <warn> Activation (wlan0/wireless): asking for new secrets
Feb 19 17:09:31 AKUPAKKU NetworkManager[1285]: <info> (wlan0): supplicant interface state: scanning -> disconnected
Feb 19 17:09:31 AKUPAKKU NetworkManager[1285]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
Feb 19 17:11:31 AKUPAKKU NetworkManager[1285]: <warn> No agents were available for this request.
Feb 19 17:11:31 AKUPAKKU NetworkManager[1285]: <info> (wlan0): device state change: need-auth -> failed (reason 'no-secrets') [60 120 7]
Feb 19 17:11:31 AKUPAKKU NetworkManager[1285]: <warn> Activation (wlan0) failed for access point (BATCAVE)
Feb 19 17:11:31 AKUPAKKU NetworkManager[1285]: <info> Marking connection 'BATCAVE' invalid.
Feb 19 17:11:31 AKUPAKKU NetworkManager[1285]: <warn> Activation (wlan0) failed.
Feb 19 17:11:31 AKUPAKKU NetworkManager[1285]: <info> (wlan0): device state change: failed -> disconnected (reason 'none') [120 30 0]
Feb 19 17:11:31 AKUPAKKU NetworkManager[1285]: <info> (wlan0): deactivating device (reason 'none') [0]

I’m stumped. The card is supported, the psk key is right. Can you suggest anything else I can look at?

lwfinger · February 19, 2013, 5:50pm

On 02/19/2013 09:36 AM, antttikutoja wrote:
>
> Changed the setup to use Network Manager. Still, the wireless fails to
> connect.
>
> Here is the log (NetworkManager)
>
>
> Code:
> --------------------
>
> Feb 19 17:09:02 AKUPAKKU NetworkManager[1285]: <info> Auto-activating connection ‘BATCAVE’.
> Feb 19 17:09:05 AKUPAKKU NetworkManager[1285]: <info> Activation (wlan0) starting connection ‘BATCAVE’
> Feb 19 17:09:05 AKUPAKKU NetworkManager[1285]: <info> (wlan0): device state change: disconnected → prepare (reason ‘none’) [30 40 0]
> Feb 19 17:09:05 AKUPAKKU NetworkManager[1285]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled…
> Feb 19 17:09:05 AKUPAKKU NetworkManager[1285]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started…
> Feb 19 17:09:06 AKUPAKKU NetworkManager[1285]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled…
> Feb 19 17:09:06 AKUPAKKU NetworkManager[1285]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
> Feb 19 17:09:06 AKUPAKKU NetworkManager[1285]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting…
> Feb 19 17:09:06 AKUPAKKU NetworkManager[1285]: <info> (wlan0): device state change: prepare → config (reason ‘none’) [40 50 0]
> Feb 19 17:09:06 AKUPAKKU NetworkManager[1285]: <info> Activation (wlan0/wireless): access point ‘BATCAVE’ has security, but secrets are required.
> Feb 19 17:09:06 AKUPAKKU NetworkManager[1285]: <info> (wlan0): device state change: config → need-auth (reason ‘none’) [50 60 0]
> Feb 19 17:09:06 AKUPAKKU NetworkManager[1285]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
> Feb 19 17:09:06 AKUPAKKU NetworkManager[1285]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled…
> Feb 19 17:09:06 AKUPAKKU NetworkManager[1285]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started…
> Feb 19 17:09:06 AKUPAKKU NetworkManager[1285]: <info> (wlan0): device state change: need-auth → prepare (reason ‘none’) [60 40 0]
> Feb 19 17:09:06 AKUPAKKU NetworkManager[1285]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled…
> Feb 19 17:09:06 AKUPAKKU NetworkManager[1285]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
> Feb 19 17:09:06 AKUPAKKU NetworkManager[1285]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting…
> Feb 19 17:09:06 AKUPAKKU NetworkManager[1285]: <info> (wlan0): device state change: prepare → config (reason ‘none’) [40 50 0]
> Feb 19 17:09:06 AKUPAKKU NetworkManager[1285]: <info> Activation (wlan0/wireless): connection ‘BATCAVE’ has security, and secrets exist. No new secrets needed.
> Feb 19 17:09:06 AKUPAKKU NetworkManager[1285]: <info> Config: added ‘ssid’ value ‘BATCAVE’
> Feb 19 17:09:06 AKUPAKKU NetworkManager[1285]: <info> Config: added ‘scan_ssid’ value ‘1’
> Feb 19 17:09:06 AKUPAKKU NetworkManager[1285]: <info> Config: added ‘key_mgmt’ value ‘WPA-PSK’
> Feb 19 17:09:06 AKUPAKKU NetworkManager[1285]: <info> Config: added ‘psk’ value ‘<omitted>’
> Feb 19 17:09:06 AKUPAKKU NetworkManager[1285]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
> Feb 19 17:09:06 AKUPAKKU NetworkManager[1285]: <info> Config: set interface ap_scan to 1
> Feb 19 17:09:06 AKUPAKKU NetworkManager[1285]: <info> (wlan0): supplicant interface state: inactive → scanning
> Feb 19 17:09:07 AKUPAKKU NetworkManager[1285]: <info> (wlan0): supplicant interface state: scanning → authenticating
> Feb 19 17:09:08 AKUPAKKU NetworkManager[1285]: <info> (wlan0): supplicant interface state: authenticating → disconnected

The authentication step failed. If the secret is correct, then it is possible
that the device is not able to handle the encryption. Try the following sequence


sudo /sbin/modprobe -rv ath5k
sudo /sbin/modprobe -v ath5k nohwcrypt=1

If this does not help, then try the compat-wireless package for your kernel.
That will get you a later driver.

antttikutoja · February 19, 2013, 7:09pm

Hi lwfinger.

I did the modprobe on the CLI but somethiing hard blocked the wlan so I added it as an option to ath5k and rebooted. Here’s the CLI modprobe.


AKUPAKKU:/home/aku # modprobe -rv ath5k
rmmod /lib/modules/3.4.28-2.20-desktop/kernel/drivers/net/wireless/ath/ath5k/ath5k.ko
rmmod /lib/modules/3.4.28-2.20-desktop/kernel/drivers/net/wireless/ath/ath.ko
rmmod /lib/modules/3.4.28-2.20-desktop/kernel/net/mac80211/mac80211.ko
rmmod /lib/modules/3.4.28-2.20-desktop/kernel/net/wireless/cfg80211.ko
AKUPAKKU:/home/aku #

AKUPAKKU:/home/aku # modprobe -v ath5k nohwcrypt=1
insmod /lib/modules/3.4.28-2.20-desktop/kernel/net/wireless/cfg80211.ko ieee80211_regdom=FI
insmod /lib/modules/3.4.28-2.20-desktop/kernel/net/mac80211/mac80211.ko
insmod /lib/modules/3.4.28-2.20-desktop/kernel/drivers/net/wireless/ath/ath.ko
insmod /lib/modules/3.4.28-2.20-desktop/kernel/drivers/net/wireless/ath/ath5k/ath5k.ko nohwcrypt=1
AKUPAKKU:/home/aku #

Here’s the NetworkManager log


Feb 19 19:56:13 AKUPAKKU NetworkManager[1260]: <info> Activation (wlan0) starting connection 'BATCAVE'
Feb 19 19:56:13 AKUPAKKU NetworkManager[1260]: <info> (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Feb 19 19:56:13 AKUPAKKU NetworkManager[1260]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Feb 19 19:56:13 AKUPAKKU NetworkManager[1260]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Feb 19 19:56:13 AKUPAKKU NetworkManager[1260]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Feb 19 19:56:13 AKUPAKKU NetworkManager[1260]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Feb 19 19:56:13 AKUPAKKU NetworkManager[1260]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Feb 19 19:56:13 AKUPAKKU NetworkManager[1260]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Feb 19 19:56:13 AKUPAKKU NetworkManager[1260]: <info> Activation (wlan0/wireless): access point 'BATCAVE' has security, but secrets are required.
Feb 19 19:56:13 AKUPAKKU NetworkManager[1260]: <info> (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0]
Feb 19 19:56:13 AKUPAKKU NetworkManager[1260]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete. 
Feb 19 19:56:13 AKUPAKKU NetworkManager[1260]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Feb 19 19:56:13 AKUPAKKU NetworkManager[1260]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Feb 19 19:56:13 AKUPAKKU NetworkManager[1260]: <info> (wlan0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
Feb 19 19:56:13 AKUPAKKU NetworkManager[1260]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Feb 19 19:56:13 AKUPAKKU NetworkManager[1260]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Feb 19 19:56:13 AKUPAKKU NetworkManager[1260]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Feb 19 19:56:14 AKUPAKKU NetworkManager[1260]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Feb 19 19:56:14 AKUPAKKU NetworkManager[1260]: <info> Activation (wlan0/wireless): connection 'BATCAVE' has security, and secrets exist.  No new secrets needed.
Feb 19 19:56:14 AKUPAKKU NetworkManager[1260]: <info> Config: added 'ssid' value 'BATCAVE'
Feb 19 19:56:14 AKUPAKKU NetworkManager[1260]: <info> Config: added 'scan_ssid' value '1'
Feb 19 19:56:14 AKUPAKKU NetworkManager[1260]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
Feb 19 19:56:14 AKUPAKKU NetworkManager[1260]: <info> Config: added 'psk' value '<omitted>'
Feb 19 19:56:14 AKUPAKKU NetworkManager[1260]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Feb 19 19:56:14 AKUPAKKU NetworkManager[1260]: <info> Config: set interface ap_scan to 1
Feb 19 19:56:14 AKUPAKKU NetworkManager[1260]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Feb 19 19:56:15 AKUPAKKU NetworkManager[1260]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Feb 19 19:56:15 AKUPAKKU NetworkManager[1260]: <info> (wlan0): supplicant interface state: authenticating -> disconnected
Feb 19 19:56:15 AKUPAKKU NetworkManager[1260]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Feb 19 19:56:16 AKUPAKKU NetworkManager[1260]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Feb 19 19:56:17 AKUPAKKU NetworkManager[1260]: <info> (wlan0): supplicant interface state: authenticating -> disconnected
Feb 19 19:56:17 AKUPAKKU NetworkManager[1260]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Feb 19 19:56:24 AKUPAKKU NetworkManager[1260]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Feb 19 19:56:24 AKUPAKKU NetworkManager[1260]: <info> (wlan0): supplicant interface state: authenticating -> disconnected
Feb 19 19:56:24 AKUPAKKU NetworkManager[1260]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Feb 19 19:56:25 AKUPAKKU NetworkManager[1260]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Feb 19 19:56:26 AKUPAKKU NetworkManager[1260]: <info> (wlan0): supplicant interface state: authenticating -> disconnected
Feb 19 19:56:26 AKUPAKKU NetworkManager[1260]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Feb 19 19:56:27 AKUPAKKU NetworkManager[1260]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Feb 19 19:56:27 AKUPAKKU NetworkManager[1260]: <info> (wlan0): supplicant interface state: authenticating -> disconnected
Feb 19 19:56:27 AKUPAKKU NetworkManager[1260]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Feb 19 19:56:28 AKUPAKKU NetworkManager[1260]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Feb 19 19:56:29 AKUPAKKU NetworkManager[1260]: <info> (wlan0): supplicant interface state: authenticating -> disconnected
Feb 19 19:56:29 AKUPAKKU NetworkManager[1260]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Feb 19 19:56:30 AKUPAKKU NetworkManager[1260]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Feb 19 19:56:30 AKUPAKKU NetworkManager[1260]: <info> (wlan0): supplicant interface state: authenticating -> disconnected
Feb 19 19:56:31 AKUPAKKU NetworkManager[1260]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Feb 19 19:56:31 AKUPAKKU NetworkManager[1260]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Feb 19 19:56:32 AKUPAKKU NetworkManager[1260]: <info> (wlan0): supplicant interface state: authenticating -> disconnected
Feb 19 19:56:32 AKUPAKKU NetworkManager[1260]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Feb 19 19:56:33 AKUPAKKU NetworkManager[1260]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Feb 19 19:56:34 AKUPAKKU NetworkManager[1260]: <info> (wlan0): supplicant interface state: authenticating -> disconnected
Feb 19 19:56:34 AKUPAKKU NetworkManager[1260]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Feb 19 19:56:34 AKUPAKKU NetworkManager[1260]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Feb 19 19:56:35 AKUPAKKU NetworkManager[1260]: <info> (wlan0): supplicant interface state: authenticating -> disconnected
Feb 19 19:56:35 AKUPAKKU NetworkManager[1260]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Feb 19 19:56:36 AKUPAKKU NetworkManager[1260]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Feb 19 19:56:37 AKUPAKKU NetworkManager[1260]: <info> (wlan0): supplicant interface state: authenticating -> disconnected
Feb 19 19:56:37 AKUPAKKU NetworkManager[1260]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Feb 19 19:56:38 AKUPAKKU NetworkManager[1260]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Feb 19 19:56:38 AKUPAKKU NetworkManager[1260]: <info> (wlan0): supplicant interface state: authenticating -> disconnected
Feb 19 19:56:38 AKUPAKKU NetworkManager[1260]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Feb 19 19:56:39 AKUPAKKU NetworkManager[1260]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Feb 19 19:56:39 AKUPAKKU NetworkManager[1260]: <warn> Activation (wlan0/wireless): association took too long.
Feb 19 19:56:39 AKUPAKKU NetworkManager[1260]: <info> (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0]
Feb 19 19:56:39 AKUPAKKU NetworkManager[1260]: <warn> Activation (wlan0/wireless): asking for new secrets
Feb 19 19:56:39 AKUPAKKU NetworkManager[1260]: <info> (wlan0): supplicant interface state: authenticating -> disconnected
Feb 19 19:56:39 AKUPAKKU NetworkManager[1260]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
Feb 19 19:58:39 AKUPAKKU NetworkManager[1260]: <warn> No agents were available for this request.
Feb 19 19:58:39 AKUPAKKU NetworkManager[1260]: <info> (wlan0): device state change: need-auth -> failed (reason 'no-secrets') [60 120 7]
Feb 19 19:58:39 AKUPAKKU NetworkManager[1260]: <warn> Activation (wlan0) failed for access point (BATCAVE)
Feb 19 19:58:39 AKUPAKKU NetworkManager[1260]: <info> Marking connection 'BATCAVE' invalid.
Feb 19 19:58:39 AKUPAKKU NetworkManager[1260]: <warn> Activation (wlan0) failed.
Feb 19 19:58:39 AKUPAKKU NetworkManager[1260]: <info> (wlan0): device state change: failed -> disconnected (reason 'none') [120 30 0]
Feb 19 19:58:39 AKUPAKKU NetworkManager[1260]: <info> (wlan0): deactivating device (reason 'none') [0]

I have to be away for the next hour or so but will check in when I’m back. If you still can’t see anything, I’ll look at the compat-wireless stuff.

Thanks very much for your efforts so far. Much appreciated.

Cheers - AK

lwfinger · February 19, 2013, 7:47pm

On 02/19/2013 12:16 PM, antttikutoja wrote:

> Feb 19 19:56:16 AKUPAKKU NetworkManager[1260]: <info> (wlan0): supplicant interface state: scanning -> authenticating
> Feb 19 19:56:17 AKUPAKKU NetworkManager[1260]: <info> (wlan0): supplicant interface state: authenticating -> disconnected

Same problem.

antttikutoja · February 19, 2013, 8:32pm

****! It’s frustrating because it points to the passphrase being wrong. I did a wee test where I used a bogus passphrase and got the same but I couldn’t be more sure that the one I’m using here is the right one.

I’ll get on to the compat-wireless stuff asap and report back.

Thanks again. Much appreciated.

Cheers - AK.