luci-mod-status: add support for the 6g band #6498
Conversation
|
@dhewg I tested, scan works, 6 ghz band is less crowded.
|
|
Nice, thanks! |
|
Well, maybe those widths are okay. At least my local 80mhz wide network shows up correctly. |
|
@dhewg we should think of a solution for those channel number... Any idea? maybe reduce the text size? Or write them on 2 different lines with an y offset? |
|
The shot above may be an extreme example. It depends on the country code and the available channels. It looks like this for me: |
|
@dhewg mhhh ok but we also need to handle that case... I think a 2 line implementation is the simplest one and would solve the thing... and maybe guard it and enable this only when then chan number is > of a specific value? I can do some test if you don't have time with handling this |
|
That would be nice, js isn't my strong suit... |
|
@mj22226 can you create an issue about this adding your image and tagging me so we can track this and I won't forget to improve this? |
|
@dhewg nit last commit can you improve the commit description? Something like "Enable support for 6GHz band now that code supports it" |
iwinfo already provides the band information with every channel, so just use that instead. Signed-off-by: Andre Heider <a.heider@gmail.com>
This prevents adding entries to mismatching bands when a channel number exists on more than one band. Signed-off-by: Andre Heider <a.heider@gmail.com>
Enable support for the 6GHz band now that the code supports it. For that it just needs to be added to the "bands" object. Signed-off-by: Andre Heider <a.heider@gmail.com>
Currently, results from the 2.4 and 6 ghz bands get mixed together, because internally the channel number is used for some checks.
This adds some checks to prevent that, and then adds a new 6g band tab.
This works on my end, but my AP is the only 6g one nearby, so I don't have others in my scan results. Can someone test that please?