Unable to connect to WiFi: CRDA error

[JonB]

Hi

Can anyone help me? I cannot connect to WiFi on the Joggler any more. I am seeing errors in dmesg:

cfg80211: Calling CRDA to update world regulatory domain
wlan0: deauthenticated from f8:1e:df:fc:fe:f5 (Reason: 2=PREV_AUTH_NOT_VALID)

I've had a good look round t'Internet but I cannot find a fix that works. It's a brick without wifi.

Any ideas?

Cheers
JonB

PS, Am running SqueezePlayOS v1.59.

[Man in a van]

Hi

Can anyone help me? I cannot connect to WiFi on the Joggler any more. I am seeing errors in dmesg:

cfg80211: Calling CRDA to update world regulatory domain
wlan0: deauthenticated from f8:1e:df:fc:fe:f5 (Reason: 2=PREV_AUTH_NOT_VALID)

I've had a good look round t'Internet but I cannot find a fix that works. It's a brick without wifi.

Any ideas?

Cheers
JonB

PS, Am running SqueezePlayOS v1.59.

Can you connect via ethernet and then re-enable the wlan?

or make a new (seperate) OS, latest version, you don't say internal or external.

Ronnie

[hawsey]

A plug in WiFi adapter is supported in SqPlayOs I forget which one but it will be in the thread .
Have you another Joggler you could swap the WiFi adapter with to make sure it's that what is faulty ?
Did it happen after lightening ?


Sent from my Moto G (4) using Tapatalk

[pete]

Not seen that error before. I have seen the inside USB O2 Joggler get a bit loosey goosey (well after shipping one) causing issues.

Googling a bit the message you posted is seen with or without a WLAN card.

Do you still see the WLAN device with lsusb?

[JonB]

Yes, the WLAN card is still visible to the OS, so I think there is no loose connection. It used to work with this SqueezePlay OS version (the latest), then suddenly stopped.

I think CRDA is a standard that ensures WiFi cards conform to the region they are being used in. So, the driver should be asking a CRDA server what region it is in, or something like that. Or maybe it is attempting to authenticate itself with the router? I read up a bit on it, but gave up as it was all needlessly complex. My other Joggler won't connect wirelessly, either. I am surprised no one else is seeing this to be honest!

So far I have tried:

• fresh install of SqueezePlay OS
• login via Ethernet and check the wlan card is detected by the OS - it is
• try to re-enable the wlan card while logged in over ethernet
• check the spare Joggler (normally connected via lan) to see if it can connect via wifi - it can't)

..all to no avail!

[Man in a van]

Jon

How about "turn it off, then turn it on"

Switch off the joggler/s with the shutdown command.

Disconnect the router from the internet and then restart it.

When it's up and running, restart the Joggler without the ethernet cable and go to Network and fill in the log-in details for wireless.

Ronnie

[JonB]

Yes of course I have power cycled it...

[pete]

Have you tried to boot Buzz's Ubuntu build wireless stuff? Did it work?

[hawsey]

I always have to connect via ethernet first , then wireless then remove ethernet cable .

Sent from my Moto G (4) using Tapatalk

[pete]

Here totally redid my Squeezeplayer Openframe 2 wireless connectivity. I did it all via the command line here.

I did update the Squeezeplayer Ubuntu 14.04 initially changing the apt source.list to:

Code: Select all

# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
# newer versions of the distribution.
deb http://archive.ubuntu.com/ubuntu/ trusty main restricted
deb-src http://archive.ubuntu.com/ubuntu/ trusty main restricted

## Major bug fix updates produced after the final release of the
## distribution.
deb http://archive.ubuntu.com/ubuntu/ trusty-updates main restricted
deb-src http://archive.ubuntu.com/ubuntu/ trusty-updates main restricted

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team. Also, please note that software in universe WILL NOT receive any
## review or updates from the Ubuntu security team.
deb http://archive.ubuntu.com/ubuntu/ trusty universe
deb-src http://archive.ubuntu.com/ubuntu/ trusty universe
deb http://archive.ubuntu.com/ubuntu/ trusty-updates universe
deb-src http://archive.ubuntu.com/ubuntu/ trusty-updates universe

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu 
## team, and may not be under a free licence. Please satisfy yourself as to 
## your rights to use the software. Also, please note that software in 
## multiverse WILL NOT receive any review or updates from the Ubuntu
## security team.
deb http://archive.ubuntu.com/ubuntu/ trusty multiverse
deb-src http://archive.ubuntu.com/ubuntu/ trusty multiverse
deb http://archive.ubuntu.com/ubuntu/ trusty-updates multiverse
deb-src http://archive.ubuntu.com/ubuntu/ trusty-updates multiverse

Using WPA2 - TKIP or AES and still keep my SSID hidden.

Assumption is that wpa_supplicant and iw is installed.

1 - first
nano /etc/network/interfaces

to look like this.

auto wlan0
iface wlan0 inet dhcp
wpa-ssid {ssid}
wpa-psk {password}

2 - next

nano /etc/wpa_supplicant.conf

to look like this:

network={
ssid="wifi_name"
psk="wifi_key"
}

or shortcut it:

wpa_passphrase Your_SSID Your_passwd > /etc/wpa_supplicant.conf

3 - autostart your WiFi connection

Here just did an autostart of:

dhclient wlan0

Works by default on boot just fine.

[JonB]

Hi Pete

Sorry for the late reply (one year late). I've reflashed with the latest SqueezePlayerOS 303 and amended the /etc/network/interfaces file in your first step. Reboot and it appears to be working, bypassing the SqueezeBox settings completely.

Hurrah!

Now I can dust the Jogglers off and restore them to their rightful places (Kitchen and Study).

Very Happy Camper now!

Cheers
JonB

[pete]

Good news JonB.

Subsequent to the above decided to update with most current version of Squeezeplayer installation on the Joggler. With that I didn't have to redo the network stuff as it worked fine out of the box with the wireless network Squeezeplayer network configuration menu.

[JonB]

Ah, spoke too soon.

One of them is working. The other refuses to connect wirelessly, not sure why. I can only get into it with an Ethernet cable and ssh. I followed these instructions:

https://unix.stackexchange.com/question ... mmand-line

..and it did connect but on reboot without the Ethernet cable plugged in, nothing. The SqueezePlayer wireless config didn't work for me (and I just retried it).

[pete]

It could be a bad USB WLAN stick. Maybe try switching them?

Here on one test device installed a SSD USB inside of the Joggler. It is larger than the openboard WLAN stick and glued a small 7 port USB hub on the back of the Joggler and use the WLAN stick on the hub. The USB 2.0 hub is directly wired to the Joggler motherboard for a 3rd USB connection.

[keynet]

It may be that the wireless signal is too weak and it's trying to reinitialise and failing. Sometimes you see odd messages during re-inits that may be unrelated to the actual problem it has. I have various issues with wireless strength due to too many people with conflicting AP's in a nearby tower. I updated the firmware per this viewtopic.php?f=2&t=555&p=27179&hilit=firmware#p27179, though I think it was later updated in PNP 3.6, so I'm now on that version. It seemed to make a little improvement, but sensitivity is still not that great, it's easy enough to swap the firmware file and try - YMMV.

In fact I'd quite like to try a more modern USB adapter but it's not yet such a problem that I want to take my Jogglers apart and try to find/build drivers etc...! The real solution for me would be to switch to 5GHz, and connect my 5GHz base station instead.

[roobarb!]

In fact I'd quite like to try a more modern USB adapter but it's not yet such a problem that I want to take my Jogglers apart and try to find/build drivers etc...! The real solution for me would be to switch to 5GHz, and connect my 5GHz base station instead.

I can highly recommend the Netgear WNDA3200 and it's supported in SQPOSv3. Whip out the old card and antennae, plug this in, you're done.

No idea if it could be made to work under the original OS. It does have the quirk that it starts in mass storage mode (drivers built-in) and needs usbmodeswitch to kick it into wifi mode. Supports 5 GHz nicely.

[jkn]

Hi Roobarb

In fact I'd quite like to try a more modern USB adapter but it's not yet such a problem that I want to take my Jogglers apart and try to find/build drivers etc...! The real solution for me would be to switch to 5GHz, and connect my 5GHz base station instead.

I can highly recommend the Netgear WNDA3200 and it's supported in SQPOSv3. Whip out the old card and antennae, plug this in, you're done.

No idea if it could be made to work under the original OS. It does have the quirk that it starts in mass storage mode (drivers built-in) and needs usbmodeswitch to kick it into wifi mode. Supports 5 GHz nicely.

Is the WNDA3100 (also dual band, I think) also supported in SQPOS V3, can you tell me?

Thanks, Jon N

[roobarb!]

Is the WNDA3100 (also dual band, I think) also supported in SQPOS V3, can you tell me?

I have no idea, I'm afraid - a lot of Netgear drivers are in the kernel and I included as many wifi and ethernet USB devices as possible, so if there's any kernel support for it at all, it is likely to be there. What I can't promise is that there won't be some quirks - as in, the WNDA3200 shows up a mass storage device first, then needs a kick from a package called usbmodeswitch to flip it into wifi mode. That may also be the case with the WNDA3100, but having never had one, I don't know.

If you already own one, give it a whirl!

[pete]

Here left the internal WiFi connected and SSH'd to SP, plugged in a generic TP-Link micro USB WiFi Stick and manually installed the drivers for Linux posted on the TP-Link web site.

[jkn]

Is the WNDA3100 (also dual band, I think) also supported in SQPOS V3, can you tell me?

I have no idea, I'm afraid - a lot of Netgear drivers are in the kernel and I included as many wifi and ethernet USB devices as possible, so if there's any kernel support for it at all, it is likely to be there. What I can't promise is that there won't be some quirks - as in, the WNDA3200 shows up a mass storage device first, then needs a kick from a package called usbmodeswitch to flip it into wifi mode. That may also be the case with the WNDA3100, but having never had one, I don't know.

If you already own one, give it a whirl!

Hi roobarb
I finally got around to looking at fitting an WNDA3200 into one of my jogglers. But the antennae micro-connectors are of a slightly different style and won't fit. Reading between the lines here a bit, do you just not bother connecting the antennae to the Netgear module?

Cheers, Jon N