Skip to content
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

Open
ilario opened this issue Dec 1, 2019 · 6 comments

Comments

@ilario
Copy link
Member

ilario commented Dec 1, 2019

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:

local radios_5ghz = ft.filter(wireless.is5Ghz, radios)
-- Convert radios to phys (get a list of phys from radio devices)
local phys = ft.map(utils.extract_phys_from_radios, radios_5ghz)
-- Scan networks in phys and format result
local networks = ft.map(
function(phy)
local nets = iwinfo.nl80211.scanlist(phy)
return ft.map(utils.add_prop("phy_idx", utils.phy_to_idx(phy)), nets)
end, phys)

A possible improvement would be to use 2.4 GHz radios only once the 5 GHz radios didn't find anything.

@ilario ilario changed the title FBW scans for new networks only on 5 GHz radios FBW scans for new networks only on 5 GHz radios, warn the user or add also 2.4 GHz radios Jan 4, 2020
@ilario ilario added this to Needs triage in LibreMesh 20.xx release Jan 9, 2020
@ilario ilario added this to Mid priority - Worth to fix in LibreMesh 2020.2 release Jan 10, 2020
@spiccinini
Copy link
Contributor

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?

@ilario
Copy link
Member Author

ilario commented Jun 4, 2020

That would do!

@luandro
Copy link
Contributor

luandro commented Mar 21, 2022

I tested this yesterday with LROS 1.5, only using 2.4. One network found the other. Might be solved.

@ilario
Copy link
Member Author

ilario commented Mar 22, 2022

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...
What do you mean with "only using 2.4"?

@ilario
Copy link
Member Author

ilario commented Dec 16, 2022

@selankon let's continue here the discussion started on libremesh/lime-app#324 (comment) :
there are places in firstbootwizard.lua where the 5 GHz interfaces get listed, like here:

local radios_5ghz = ft.filter(wireless.is5Ghz, radios)

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:

@ilario ilario added this to the 2020.2 milestone Feb 23, 2023
@ilario
Copy link
Member Author

ilario commented Feb 28, 2023

This is important if we want to suggest FBW to non-LibreRouter users.
@selankon @spiccinini do you think that we can fix this before the 2020.2 release?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
LibreMesh 2020.2 release
  
Mid priority - Worth to fix
LibreMesh 20.xx release
  
Needs triage
Development

No branches or pull requests

3 participants