Add all mesh interfaces to firewall rule wired_mesh #2041
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
neocturne
requested changes
May 30, 2020
neocturne
approved these changes
May 30, 2020
|
this obviously needs to be merged into one commit and it needs a decent commit message ;-) |
This allows for multiple mesh legs out of one box. Useful for offloaders and networks using vlan for separate mesh transport. Custom mesh interfaces in a VXLAN domain are otherwise firewalled. This fixes #1479
|
Thanks - I slightly modified the commit message when merging. |
dzzinstant
pushed a commit
to dzzinstant/gluon
that referenced
this pull request
Jun 9, 2020
…luon#2041) This allows for multiple mesh legs out of one box. Useful for offloaders and networks using vlan for separate mesh transport. Custom mesh interfaces in a VXLAN domain are otherwise firewalled. This fixes freifunk-gluon#1479
dzzinstant
pushed a commit
to dzzinstant/gluon
that referenced
this pull request
Jun 10, 2020
…luon#2041) This allows for multiple mesh legs out of one box. Useful for offloaders and networks using vlan for separate mesh transport. Custom mesh interfaces in a VXLAN domain are otherwise firewalled. This fixes freifunk-gluon#1479
dzzinstant
pushed a commit
to dzzinstant/gluon
that referenced
this pull request
Jun 10, 2020
…luon#2041) This allows for multiple mesh legs out of one box. Useful for offloaders and networks using vlan for separate mesh transport. Custom mesh interfaces in a VXLAN domain are otherwise firewalled. This fixes freifunk-gluon#1479
dzzinstant
pushed a commit
to dzzinstant/gluon
that referenced
this pull request
Jun 11, 2020
…luon#2041) This allows for multiple mesh legs out of one box. Useful for offloaders and networks using vlan for separate mesh transport. Custom mesh interfaces in a VXLAN domain are otherwise firewalled. This fixes freifunk-gluon#1479
dzzinstant
pushed a commit
to dzzinstant/gluon
that referenced
this pull request
Jun 11, 2020
…luon#2041) This allows for multiple mesh legs out of one box. Useful for offloaders and networks using vlan for separate mesh transport. Custom mesh interfaces in a VXLAN domain are otherwise firewalled. This fixes freifunk-gluon#1479
margau
added a commit
to margau/gluon
that referenced
this pull request
Jun 20, 2020
Documents the changes introduced in freifunk-gluon#2041
This was referenced Jun 20, 2020
margau
added a commit
to margau/gluon
that referenced
this pull request
Jun 20, 2020
Documents the changes introduced in freifunk-gluon#2041
neocturne
added a commit
that referenced
this pull request
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 pull request
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 pull request
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 pull request
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)
lemoer
pushed a commit
to lemoer/gluon
that referenced
this pull request
Dec 20, 2020
…luon#2041) This allows for multiple mesh legs out of one box. Useful for offloaders and networks using vlan for separate mesh transport. Custom mesh interfaces in a VXLAN domain are otherwise firewalled. This fixes freifunk-gluon#1479
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This allows for multiple mesh legs out of one box. Useful for offloaders
and networks using vlan for separate mesh transport.
This fixes #1479