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

NB 2339 on hAP removes AP band selection if Mesh RF is on - 2 GHz only #720

Closed
k6ccc opened this issue Feb 18, 2023 · 13 comments
Closed

NB 2339 on hAP removes AP band selection if Mesh RF is on - 2 GHz only #720

k6ccc opened this issue Feb 18, 2023 · 13 comments

Comments

@k6ccc
Copy link

k6ccc commented Feb 18, 2023

On Nightly build 2339 on a hAP lite, if Mesh RF is enabled on a node that has the WiFi AP enabled on 5 GHz, the band selection for the AP is removed and the channels are forced to 2 GHz. Then the node complains that you can't have Mesh RF and LAN AP on the same wireless card.
This screen capture is before I made any changes:
hAP_2339_issue-1

After enabling Mesh RF, AP Band selection is not longer there and only 2 GHz channels available for selection.
hAP_2339_issue-2

After hitting Save, it bitches about Mesh and LAN AP trying to use the same wireless.
hAP_2339_issue-3

After disabling Mesh RF and saving, the Band selection for the LAN AP returns.

@k6ccc
Copy link
Author

k6ccc commented Feb 18, 2023

Similar problem on GL iNet AR750. This node prior to upgrade to 2339 had the LAN AP enabled on 5 GHz and Mesh RF enabled on 2.4 GHz. After updating to 2339, this is what I see on the basic setup page. According to a WiFi analyzer on my phone, the AR750 really is operating the AP on channel 44 on 5 GHz - not channel 1 as indicated.
AR750_2339_issue-1

@k1ky
Copy link

k1ky commented Feb 19, 2023

It appears to work ok if MESH RF is NOT enabled, but otherwise pretty messed up when MESH RF is enabled. N2339 on GL.INET AR750.

@aanon4
Copy link
Contributor

aanon4 commented Feb 20, 2023

#724

@k6ccc
Copy link
Author

k6ccc commented Feb 20, 2023

Looks like it is fixed on NB 2347 - tested on both hAP lite and iNet AR750.

@aanon4
Copy link
Contributor

aanon4 commented Feb 20, 2023

Thanks!

@aanon4 aanon4 closed this as completed Feb 20, 2023
@k6ccc
Copy link
Author

k6ccc commented Feb 20, 2023

Well, not so fast. I was able to update my newer hAP ac3 to NB 2347 and when enabling Mesh RF, the AP is locked to 2GHz.

@aanon4
Copy link
Contributor

aanon4 commented Feb 20, 2023

Let's keep the AP discussion over here (the other issue is just for the update process).
Pinging you on mattermost to ask some questions.

@aanon4
Copy link
Contributor

aanon4 commented Feb 20, 2023

This is what my hAP ac3 looks like with 2347 on it:
Screenshot 2023-02-20 at 10 41 05 AM

@aanon4
Copy link
Contributor

aanon4 commented Feb 20, 2023

If you're up for changing one line by hand to test something, that'd be fantastic?

File: /www/cgi-bin/setup
Line: 1237
Currently:
local alt_phy = phy == "phy0" and "phy1" or "phy0"
Change to:
local alt_phy = (not phy or phy == "phy0") and "phy1" or "phy0"
And see how that changes things

@aanon4
Copy link
Contributor

aanon4 commented Feb 20, 2023

#728

@k6ccc
Copy link
Author

k6ccc commented Feb 20, 2023

To be honest Tim, editing a 1487 line file in vi is getting beyond my comfort level. I can barely manage to use vi with an online help on another screen.
Unless the nodes have a more friendly editor.

@aanon4
Copy link
Contributor

aanon4 commented Feb 20, 2023

Not to worry - This should take care of the problem and I know you'll test the change once it hits nightly - much appreciated as ever.

@k6ccc
Copy link
Author

k6ccc commented Mar 5, 2023

Fixed a rev or two ago.

@k6ccc k6ccc closed this as completed Mar 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants