-
Notifications
You must be signed in to change notification settings - Fork 11
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
ioc_start.py: allow setting IP address on lo0 #48
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
Iocage currently expects interfaces to be specified in the nic:bridge format, where bridge cannot be none. This results in iocage always creating a bridge to which VNET jail epair interfaces are added as members. In a scenario where the user wants jails to be isolated on the data-link layer (OSI layer 2 / Ethernet) and use the host as a router, this bridge is unnecessery. It can also result in illegitimate cross-jail traffic being allowed, since pf filtering on bridge interfaces is disabled by default on FreeBSD systems (net.link.bridge.pfil_bridge=0). Closes freebsd#44
Currently, iocage ignores IP addresses given for the loopback interface lo0 that exists by default in a VNET jail. Adding addresses to that interface can be useful, for instance to implement rfc7404 addressing where link-local addresses are used for interconnections, and routable addresses are set on loopback interfaces. This commit enables setting additional addresses on the lo0 interface using the usual ip4_addr or ip6_addr settings. For instance: ip4_addr='lo0|192.168.2.10' Closes freebsd#46
Pull Request Test Coverage Report for Build 11916048528Details
💛 - Coveralls |
1 similar comment
Pull Request Test Coverage Report for Build 11916048528Details
💛 - Coveralls |
Would you like me to rebase this? |
It should merge flawlessly |
Thank you once again ! |
dgeo
added a commit
to criecm/iocage
that referenced
this pull request
Nov 29, 2024
* ioc_start.py: allow 'none' bridge in interfaces Iocage currently expects interfaces to be specified in the nic:bridge format, where bridge cannot be none. This results in iocage always creating a bridge to which VNET jail epair interfaces are added as members. In a scenario where the user wants jails to be isolated on the data-link layer (OSI layer 2 / Ethernet) and use the host as a router, this bridge is unnecessery. It can also result in illegitimate cross-jail traffic being allowed, since pf filtering on bridge interfaces is disabled by default on FreeBSD systems (net.link.bridge.pfil_bridge=0). Closes freebsd#44 * ioc_start.py: allow setting IP address on lo0 Currently, iocage ignores IP addresses given for the loopback interface lo0 that exists by default in a VNET jail. Adding addresses to that interface can be useful, for instance to implement rfc7404 addressing where link-local addresses are used for interconnections, and routable addresses are set on loopback interfaces. This commit enables setting additional addresses on the lo0 interface using the usual ip4_addr or ip6_addr settings. For instance: ip4_addr='lo0|192.168.2.10' Closes freebsd#46 --------- Co-authored-by: dgeo <[email protected]>
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.
Please merge #47 first.
Currently, iocage ignores IP addresses given for the loopback interface
lo0 that exists by default in a VNET jail. Adding addresses to that
interface can be useful, for instance to implement rfc7404 addressing
where link-local addresses are used for interconnections, and routable
addresses are set on loopback interfaces.
This commit enables setting additional addresses on the lo0 interface
using the usual ip4_addr or ip6_addr settings.
For instance: ip4_addr='lo0|192.168.2.10'
Closes #46