-
Notifications
You must be signed in to change notification settings - Fork 96
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
FBW scans for new networks only on 5 GHz radios, warn the user or add also 2.4 GHz radios #661
Comments
Maybe we can filter out radios that do not have a mesh interface (so if 2.4GHz radios do not have a mesh interfaces then they are not used), what do you think? |
That would do! |
I tested this yesterday with LROS 1.5, only using 2.4. One network found the other. Might be solved. |
The causing code didn't change, it should not be fixed... |
@selankon let's continue here the discussion started on libremesh/lime-app#324 (comment) :
we could add a check and in case this list is empty do something else with the available interfaces. We should address the following cases:
|
This is important if we want to suggest FBW to non-LibreRouter users. |
FBW function to join an existing network does not work with 2.4 GHz only devices.
It will make the user wait and then return just a "no network found" message.
This is likely the cause of #589
The related code is:
lime-packages/packages/first-boot-wizard/files/usr/lib/lua/firstbootwizard.lua
Lines 63 to 71 in 3235c25
A possible improvement would be to use 2.4 GHz radios only once the 5 GHz radios didn't find anything.
The text was updated successfully, but these errors were encountered: