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

mesh_lan not enabled on initial install, when mesh_on_lan is enabled in site_config #2090

Closed
thillux opened this issue Aug 14, 2020 · 0 comments · Fixed by #2091
Closed

mesh_lan not enabled on initial install, when mesh_on_lan is enabled in site_config #2090

thillux opened this issue Aug 14, 2020 · 0 comments · Fixed by #2091

Comments

@thillux
Copy link

thillux commented Aug 14, 2020

Bug report

When initially flashing gluon with a factory image of the current master, which has mesh_on_lan enabled by default in its site config, the mesh_lan interface does not get assigned to the networks of the wired_mesh firewall zone.

The issue seems to have its root in package/gluon-core/luasrc/lib/gluon/upgrade/*:
140-firewall-rules looks, if any gluon_wired interfaces (!= mesh_wan) exist and puts them into the wired_mesh network list.
At this point in time, no mesh_lan interface exists, because it gets created later by 220-interface-lan.

@neocturne neocturne self-assigned this Aug 14, 2020
neocturne added a commit that referenced this issue Aug 14, 2020
scripts so that the mesh_lan interface is accounted for.

Two other firewall upgrade scripts (mesh-babel and l3roamd) are
reordered as well. While there seems to be no hard dependency at the
moment, it makes sense to run the basic setup first, also to avoid
problems with future changes.

Closes: #2090
Fixes: ed094bc ("gluon-core: firewall: Allow custom gluon_wired interfaces (#2041)")
neocturne added a commit that referenced this issue Aug 14, 2020
Reorder scripts so that the mesh_lan interface is accounted for.

Two other firewall upgrade scripts (mesh-babel and l3roamd) are
reordered as well. While there seems to be no hard dependency at the
moment, it makes sense to run the basic setup first, also to avoid
problems with future changes.

Closes: #2090
Fixes: ed094bc ("gluon-core: firewall: Allow custom gluon_wired interfaces (#2041)")
rotanid pushed a commit that referenced this issue Aug 14, 2020
)

Reorder scripts so that the mesh_lan interface is accounted for.

Two other firewall upgrade scripts (mesh-babel and l3roamd) are
reordered as well. While there seems to be no hard dependency at the
moment, it makes sense to run the basic setup first, also to avoid
problems with future changes.

Closes: #2090
Fixes: ed094bc ("gluon-core: firewall: Allow custom gluon_wired interfaces (#2041)")
neocturne added a commit that referenced this issue Aug 22, 2020
)

Reorder scripts so that the mesh_lan interface is accounted for.

Two other firewall upgrade scripts (mesh-babel and l3roamd) are
reordered as well. While there seems to be no hard dependency at the
moment, it makes sense to run the basic setup first, also to avoid
problems with future changes.

Closes: #2090
Fixes: ed094bc ("gluon-core: firewall: Allow custom gluon_wired interfaces (#2041)")
(cherry picked from commit de5ebfa)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants