-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WARNING] Not associated to an AP #27
Comments
@slate-1 Sorry about that. Coupld you please insert a This definitely is strange to me... I've never seen that error before when I was actually connected to a network. |
No need to be sorry, probably an issue with my hardware - old kit re-purposed -only 2.4g capability. Please find debug output (wifi-survey:1): Gtk-CRITICAL **: 05:53:55.045: gtk_distribute_natural_allocation: assertion 'extra_space >= 0' failed |
Sorry closed by mistake |
Well... that's weird. The pertinent output here is:
Those logs - specifically the first and last of those lines, are coming from this tiny function on lines 88-95 of collector.py:
There's not much room for something to go wrong there. So either the BSSID-getting logic in Scanner is broken, or something else is going on here. @slate-1 Could you please post the full output of |
Output from command |
Although I know very little about coding my thoughts are turning to - how about instead of getting "Not Connnected to AP" but display this first time. Possibly set a flag for override = true to continue without BSSID check. Or would this cause further issues down the line? I am of course assuming that the iperf3 server test will function happily without a check. This of course may not affect anyone else but if it does then there is an option to continue regardless (If it works, it works). I'm assuming iw dev should return the BSSID - in my case it's not. Thanks for looking at this issue. |
Examples looked great & wished to try this out.
Possible Bug Report
Not sure if this is a bug or my own error. If this can be resolved great, if not also ok.
Running wifi-survey with docker run command as specified runs successfully - But when starting tests (Left click on Plan) receive "Aborted : Not connected to an access point" in bottom of window.
Plan stays loaded & can click all over map but always returns Aborted error
Host is connected on wifi network.
Docker container appears to correctly receive wifi information from host - running "sudo docker exec ../sbin/iwconfig lists the connection details which includes the BSSID etc. - Although I believe this is not used by wifi-survey any more, thought this at least proved the container received the details from the host.
Version
Using docker image ID 27941809078c
Installation Method
Installed Docker on Debian Buster Debian 4.19.235-1 (First time ever used Docker)
Installed wifi survey with
sudo docker run --net="host" --privileged --name survey -it --rm -v $(pwd):/pwd -w /pwd -e DISPLAY=$DISPLAY -v "$HOME/.Xauthority:/root/.Xauthority:ro" jantman/python-wifi-survey-heatmap wifi-survey -i wlp3s0 -s 192.168.x.x -p plan.png -t "Plan Heatmap"
Running iperf3 on separate system (Not in Docker) - Assuming the "Abort" issue is raised before any testing starts and I may have issues later if current issue can be resolved but one step at time.
Gtk-CRITICAL error - Don't think this error has anything to do with issue but does happen when launching.
Actual Output
Output from Terminal
(wifi-survey:1): Gtk-CRITICAL **: 21:29:57.664: gtk_distribute_natural_allocation: assertion 'extra_space >= 0' failed
[2022-06-17 21:30:04,489 WARNING] Not associated to an AP
Expected Output
Was hoping for the first test to run & reach 100%
Testing Assistance
Will help if I can, but may need detailed instructions to provide required information.
The text was updated successfully, but these errors were encountered: