I set up my router last night and configured radio0 as 5GHz and radio1 as 2.4GHz with 40 and 20 MHz channel widths respectively. I tried adding another guest network on 2.4 GHz but ran into the bug where the interface edit screen gives error 500, so I ended up doing a factory reset and starting over.
Now after setting it up again, the 5Ghz network was working last night but seems to have disappeared this morning. I don’t think I did anything unusual in setting it up. When I went in to look, the radio shows disabled and the setting boxes are all blank. I’d rather not start over again - what file do I need to edit and what are the default settings in there to bring it back? Thanks. Screenshot below:
Here’s my current situation - both networks are working but I cannot view the radio0 details in LUCI, I get an error 500. I did end up downloading the ath10k firmware yesterday and I’m using the firmware-5.bin_10.2.4.70-2 from hw2.0/10.2.4 as /lib/firmware/ath10k/QCA988X/hw2.0/firmware-5.bin and then reboot.
Here’s my current contents of /etc/config/wireless (with ssid and passwords removed):
I’m trying to remember if I changed anything else - I did a lot of reloading of firmware and rebooting but I think this is the final config that worked (except for the error 500 on the web UI). I haven’t rebooted much since, so I don’t know if the config works across reboots.
Rebooting using LUCI or issueing ‘reboot’ in CLI results in ath10k not loading. If I remove power and reapply, then the driver will load correctly.
I was back to radio0 offline, but it seems whatever I just did fixed it again - I had tried adding a txpower and channel to /etc/config/wireless but removing them again looks like it helped. I also had SQM on when I was doing the reboots but now it’s off and things seem fine. Not entirely sure that’s related, since I did a few things at the same time.
Same problem here for the 5GHz radio. Changing the country code from CZ to DE in LuCI or directly in /etc/config/wireless causes the card to crash: “Wireless is disabled or not associated”. wifi or reboot commands have no effect, even if the country code is set back to CZ. Only removing the power for a couple of seconds will do the trick.
Seems like a serious bug.
Not sure if this is the same problem but both of my radios go down after several days. Right now radio0 is down with the same “0% Wireless is disabled or not associated”. message after three days. I also get error 500. radio 1 is still up but I don’t know for how much longer. In either case disabling and the enabling has no effect. wifi down wlan0 gives
Command failed: Not found
wlan0(): Interface type not supported
A reboot fixes it. Any ideas or should I start a new thread?
This is actually crazy. This router is not even remotely ready for the public.
I’ve had the router plugged in for a matter of hours and I have this issue.
Essentially after the router is restarted the first time after the initial configuration and update the 5GHz wifi is gone for good.
I can restart it via any method, power plug, reboot in ssh, reboot in luci. Nothing works.
Thankfully i made a backup of my config after i did some mac address reservations and other stuff before i started to tinker with the wireless. I can confirm i’m also having the same issue. At first i thought it was because i was setting the wireless security to force CCMP (AES) encryption, but it seems like anytime i change the country code from CZ to CA (in my case) on either the 2.4 Ghz radio or the 5 GHz radio, it breaks the 5GHz radio. As long as i don’t disable or reboot, 5GHz radio continues to work, even though clicking on edit produces the dreaded internal server error 500.
I agree with anyone who’s said this is a pretty serious bug, i actually got in deep shit with the mrs because i broke the wireless. However, for anyone who’s backed up their config, a restore of my config from the turris GUI did restore connectivity.
@TURRISOMNIATEAM, PLEASE FIX, WHERE’S THE AUTO UPDATE FOR THIS?
EDIT: NOT SURE IF ITS RELATED, but i find after this issue crops up, i have to reboot my switches to restore connectivity (this also happens regardless of whether i make changes or not). PLEASE HELP TURRIS TEAM!
Concur. Where’s the updated firmware that fixes this issue? https://github.com/CZ-NIC/turris-os/issues/10 implies that there is a fix, but no existing build of the firmware has it.
I encountered on this bug after putting a mSATA in the Omnia and off course by following the procedure used in the video-tutorial.
I came to know that the channel on the 5 GHz has A LOT to do with it. The moment i changed it for example to channel 140, it lost tx-power and in a few seconds it just went down. On the net i stumbled upon this.
So apparently each country has a set of channels that permit certain tx-power output. I have experimented with it, but i have the feeling that that information is OR outdated OR incorrect. Me being from the Netherlands tried to use channel 140, however it crashed. I had to change channel and reboot to get it back. Currently i am on channel 128, although looking at the card, it does not stay fixed on channel 128, but it still randomly switches. This causes the tx-power to adapt to certain channel that it is hopping on. Which means getting a weaker signal sometimes.
EDIT2: On LuCi looking at the wireless section, i can clearly see the following.
As you can see that the TX-Rate stays the same all the time, while the RX-Rate changes sometimes. Sometimes both at the same time and sometimes only one as you can see in the pictures. Which is logical because one is my laptop and one is my smartphone. However the output from the 5 GHz has never changed.