You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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)")
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)")
)
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)")
)
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)
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.
The text was updated successfully, but these errors were encountered: