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

Move WAN VLAN id from Adv Config to Setup page #355

Closed
ab7pa opened this issue May 4, 2022 · 3 comments
Closed

Move WAN VLAN id from Adv Config to Setup page #355

ab7pa opened this issue May 4, 2022 · 3 comments

Comments

@ab7pa
Copy link
Contributor

ab7pa commented May 4, 2022

Currently the Advanced Configuration page has a setting to change the WAN VLAN ID. This setting will not be displayed for any device that uses a switch chip, but it does currently appear on devices that have a dedicated WAN port and therefore do not use VLAN tags for WAN access.
advConfig-wanVlan

Suggest moving this setting to the Setup page under the "Advanced WAN Settings" column where it could be configured with the other advanced WAN settings. If moved to Setup, it should only be displayed when the device must use a VLAN tag for WAN access, which would eliminate confusion on devices that have switches or a dedicated WAN port on which VLAN tags are not supported or required. The selection dropdown should validate that VLAN 2 is not selectable since it is already dedicated for DtD links. There should also be a link to the onboard help (?) and a help section should be added that describes this configuration setting.

Screen Shot 2022-05-05 at 8 36 46 AM

@dman776
Copy link
Contributor

dman776 commented May 4, 2022

I think this setting should remain on the adv cfg page because:
It is hardware dependent
The input is not validated and could cause major errors if entered incorrectly
The setup page does not have the logic framework for device dependent hiding

my opinions…

@ae6xe
Copy link
Contributor

ae6xe commented May 4, 2022

Related but different issue to capture. the user selectable vlan range should not include single digit numbers. Possibly, there are some standard guidelines we could research to constrain user selections to . the openwrt code auto assign vlans, 1, 2, 3 ... . In the current upgrade branch, I've cleaned up aredn usage to better align. Today, we have a hack to use vlan '0' on some switches for the LAN, to get things working. In the upgrade branch to current openwrt releases, the switch is using vlan 3 internally for the LAN, but not visible to end users.

@ab7pa
Copy link
Contributor Author

ab7pa commented May 6, 2022

Sounds like this idea may not be viable or practical. Just trying to think of ways to keep Adv Config from becoming a "junk drawer" by putting features into the UI where similar functionality is located. Will close this issue for now.

@ab7pa ab7pa closed this as completed May 6, 2022
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