I just convinced a buddy to setup AP6’s at his home which I helped out with.
Setup went smooth, sadly we noticed that his old house apparently has some wires that only supports 100Mbit (Showing orange on the S8 switch) but everything else is smooth.
After I got home, I looked into tweaking his wifi channels and for some reason, on the Outdoor AP, 5Ghz is locked when seeing it in the control panel, but it saves to whatever channel I’m choosing.
It also shows 100% load.
The FW is the same on the indoor and outdoor, 2.0x, however I see some channels are not available on the outdoor (Right now being used indoor, until he has time to fix it outside)
What could the reason be for this 100% load issue? Is it just a visual hickup?
I’m not able to scan the wifi on the AP either.
A screenshot of what you’re seeing could be helpful.
Is there an SSID set up? If there is no SSID configured, the network tab will only show the 5GHz radio (excludes the 2.4GHz radio) and the load is 100% for the 5GHz.
Sorry, I was kind of tired when I wrote the comment!
So it was not going out of channel 36, no matter what I chose (100 - 140 (DFS)) and showing 100% load all of the time.
I “fixed” it by choosing Auto for now, it’s now sitting at channel 108 with 0% load, however I’m not too happy about the fact that I can’t fine tune it to my liking :\
Yes, SSID is setup, everything works perfectly on the AP6 Pro (indoor).
I just changing it to 128 (DFS) which it all of the sudden did without any issues and no 100% load, however once the channel has been manually selected, I’m not able to scan (both Quick and Full), it just times out
I am able to do a full scan on both APs without issue. That tells me it could very well be cache.
If you’re unfamiliar on how to clear cache:
Right click anywhere on the page and click the bottom option, which should be Inspect
Right click on the Refresh icon which is immediately to the right of the Back & Forward buttons and you should get a different context menu
Click Empty Cache & Hard Reload
Try to scan again
If successful, close the pane that popped up when you click Inspect by clicking the X in the upper right-hand corner of that pane
If, however, you’re still unable to scan, click the Console tab of the pane that came up when you clicked Inspect, click the “No Entry” icon (?? - attaching screenshot)
Then reload the page again, take a screenshot of what is there in the console and paste it in a reply here.
It also wouldn’t hurt to check your version of Chrome. I tested successfully on 128.0.6613.86
Since you’re operating exclusively in DFS channels, the 100% load may be a result of DFS scanning, which, depending on the country and channel, can take a maximum of 10 minutes.
Did you try while choosing a manual 5Ghz channel? Thats when the issue starts and I just tried again, after clearing cache (I have the latest version fo Chrome as well) and I get a timeout, it also doesn’t reflect the channel I choose (132 chosen, showing 108)
This happens on both PC and phone, so shouldn’t be a cache issue either
Ok, I’m an idiot and had the AP6-Pro pulled up when I checked the channel list, my apologies.
Those lower channels are for indoor use only, so it makes sense that they’re missing for the AP6-Outdoor.
The higher channels (UNII-3) should be allowed per Denmark’s regdom so yeah, that’s a bit of a headscratcher. For regulatory compliance, we tap Qualcomm’s database, which through cursory checks, isn’t public. I’ll tag @Alta-Jeff for hopefully some more insight on that.
I did a check if the channel width plays a role as that can sometimes be the case, and saw no indication that it does, for what that’s worth.
Correct me if I’m wrong, but wasn’t the channel manually set when I tried my scan? Maybe I’m misunderstanding what you’re saying, but the channels were not set to Auto when I jumped in there. Does it error regardless of the channel that is set?
No, it was set to Auto when you tried, I corrected it to manual right after clearing cache, to confirm if it worked for me as well, as I thought you had set it to manual.
You should still have access, if you want to recreate the timeout
I’ll see what I can do to reproduce the inability to scan. Typically there are extenuating circumstances like mid-DFS scan, but the timing seems awfully long.
It’s not so much “for the AP6-Outdoor” but more-so what’s available for your region/regulatory domain, which is playing a factor in Knocker’s environment.
Definitely not a “fix”. I basically observed the channel that Auto chose and then statically set it, then tested the scan. It’s a bit of a “cheat” because no scan was necessary since the channel didn’t technically change. This way, we didn’t have to wait for a potentially lengthy DFS scan.
