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

Enable networking with vnet #35

Merged
merged 6 commits into from
Dec 4, 2022
Merged

Enable networking with vnet #35

merged 6 commits into from
Dec 4, 2022

Conversation

samuelkarp
Copy link
Owner

Issue number:
Fixes #20

Description of changes:
The freebsd extension to the OCI spec in runj (and runj.ext.json) now supports specifying a new vnet and passing interfaces into the vnet. A new integration test demonstrates how this can be used in combination with an epair, a bridge, and PF can be used to enable local and Internet access via NAT.

Testing done:
New integration test.
Manual test using containerd

Terms of contribution:

By submitting this pull request, I agree that this contribution is licensed under the terms found in the LICENSE file.

A base.txz matching the current version and architecture is downloaded
and extracted to a well-known directory to facilitate integration tests
which need a full base system.
This test tests jails with new vnets, passing interfaces, setting up
routing over a bridge, and NAT with pf.

The test requires:
* pf
* no existing NAT rules
* no bridges or interfaces that conflict with 172.31.255.0/24
* Internet access

Future improvements can be made to remove some of these requirements.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Networking
1 participant