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.

Sign up for GitHub

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

Jump to bottom

consider reverting mesh_other, mesh_uplink #22

Open
mkg20001 opened this issue Jan 23, 2022 · 1 comment
Open

consider reverting mesh_other, mesh_uplink #22

mkg20001 opened this issue Jan 23, 2022 · 1 comment

Comments

@mkg20001
Copy link
Member

currently it just assumes that other is lan and uplink is wan

better would be to just drop the mesh_other / mesh_uplink interfaces completely and then go with each interface individually

this is a tad more complicated:

  • theoretically lan can also be used as uplink
  • for the interfaces that are part of lan we don't know which ones. currently there's just lan but how does web-static-ip deal with that then?
mkg20001 added a commit that referenced this issue Jan 23, 2022
@mkg20001
web-static-ip: migrate to roles
56b7545 
we're just treating other as lan and uplink as wan

see #22
mkg20001 added a commit that referenced this issue Jan 23, 2022
@mkg20001
web-static-ip: migrate to roles
c8e4b87 
we're just treating other as lan and uplink as wan

see #22
mkg20001 added a commit that referenced this issue Mar 3, 2022
@mkg20001
web-static-ip: migrate to roles
69498bf 
we're just treating other as lan and uplink as wan

see #22
mkg20001 added a commit that referenced this issue Mar 5, 2022
@mkg20001
web-static-ip: migrate to roles
c5be043 
we're just treating other as lan and uplink as wan

see #22
mkg20001 added a commit that referenced this issue Mar 20, 2022
@mkg20001
web-static-ip: migrate to roles
2006092 
we're just treating other as lan and uplink as wan

see #22
mkg20001 added a commit that referenced this issue Mar 22, 2022
@mkg20001
web-static-ip: migrate to roles
e93061e 
we're just treating other as lan and uplink as wan

see #22
@mkg20001
Copy link
Member Author

current solution is that meshing on role uplink is mesh_uplink, and everything else with just mesh goes to mesh_other, as part of that bridge

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mkg20001