Ok, the first one somewhat does PoE+ (803.at) but only up to class 2 so it’s really more of a 802.3af adapter, although it should be fine. It’s moot because the 2nd one does PoE+. We were seeing sporadic results with 802.3at so I think your Engenius injector is the way to and we need to look deeper in to the bug.
Thanks for the data points!
Hey @Alta-Matt_v2 i just checked and when I’m logging in via ssh into the AP itself, then the check runs successfully, but on the UI it’s still time’s out.
These commands gives back the correct result:
iw dev <devname> scan -jiw dev <devname> scan -j accurateThe AP is on the latest firmware.
In the logs, I can not see anything more then this:
rc [2023/09/17 00:11:31:9158] N: JSON: {"scan":"quick","viewer":"<id>"}
kernel [332888.154929] mcastq full!
kernel [332888.155125] mcastq full!
rc [2023/09/17 00:11:31:9166] N: Scanning: quick for <id>
rc [2023/09/17 00:11:52:9623] N: JSON: {"reqStats":{"start":1694902251,"stop":1694902312,"period":"seconds","clientId":"<id>"}}
We are aware of a bug related to scanning. It’s been extremely difficult to reproduce as we indicators that it is contingent upon the other SSIDs in a particular environment. For example, I can do scans all day and they don’t fail once, but you have difficulties performing even a single scan.
Have you been able to get a single scan to complete? If you are able to get one, it would be helpful to know the SSIDs that get returned.
Not a single one.
Can you use an app (WiFi Analyzer on Android is my go-to) to scan your environment?
Yes, I usually check my environment with WiFi Explorer form my MacOS without any issues.
Perfect! Can you post a screenshot of that?
the part you censored is the part we need.
If you’re uncomfortable sharing that without the censorship publicly, feel free to DM it to me.
Ok, just sent the DM
I’m a newbie to this. But I’m seeing the same thing in late 2024-10 on an install I started about 90 minutes ago. Version 2.2c. Absolutely consistent.
Perhaps the team at AltaLabs already has this figured out?
Are you using Chrome as the browser? I had the same issue earlier this week, worked great in Firefox. Updated and restarted Chrome, scanning was working again. Just wondering if it might be low hanging fruit.
I just noticed I’m no longer seeing the problem. I can scan.
I also notice that I’ve been upgraded to version 2.2d. I was seeing this problem when I was running 2.2c, but I don’t know if the version change is relevant.
Re: another post: I was running Firefox at all times. I don’t use Chrome.
