-
Notifications
You must be signed in to change notification settings - Fork 47
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
Using wifi-scan with ev3dev I see "No associated station" #30
Comments
Hi @prasun-raha, Could you share the output of: iw dev wlx08beac12fd67 link iw dev wlx08beac12fd67 station dump # no sudo needed
./wifi-scan-station wlx08beac12fd67 sudo ./wifi-scan-all wlx08beac12fd67 |
thanks @bmegli here's the response
It looks like the wlx08beac12fd67 interface is enabled - I am on a ssh terminal connected to it but the interface is not associated with a station. I came to the wifi-scan test after trying to debug why the ev3wifi module was not working as |
I think that your driver/kernel doesn't support nl80211/cfg80211 for some reason. Try the iwconfig, e.g. iwconfig It is older tool that uses WEXT (Wireless Extensions), now deprecated in favor of iw, wifi-scan library uses the newer nl80211/cfg80211 interface, the same as iw. If that is the case (iwconfig works, iw doesn't) this likely means:
|
It does look like iwconfig is able to find it - any suggestions on next steps?
|
This is not really issue of this library but layer below it. I would investigate it in the following way:
Since this is custom build (rrsport) of custom build (ev3dev), you could ask the rrsport author first. This issue suggests that the driver was specifically added to rubirobot.
This means making it work so that This may include any number of actions like:
Also Trying to do it by yourself may be a major investment of time so weigh if it is worth it. |
I have a slightly modified version of the ev3dev from http://rubirobot.ru/.
When I execute the compiled code above I get "No associated station" comment on my robot.
Here's some excerpts from my trials
The text was updated successfully, but these errors were encountered: