Skip to content

Allow direct use of interfaces in ExtLinks#96

Merged
FelixMcFelix merged 4 commits intomainfrom
felixmcfelix/non-vnic-extlink
May 6, 2026
Merged

Allow direct use of interfaces in ExtLinks#96
FelixMcFelix merged 4 commits intomainfrom
felixmcfelix/non-vnic-extlink

Conversation

@FelixMcFelix
Copy link
Copy Markdown
Contributor

This PR allows for a network interface to be directly used in an ExtLink rather than creating a new VNIC atop that device. This is necessary to make use of pseudo-devices like OPTE ports, which are directly used by Viona.

The preflight routine has a small change to verify that each interface is only used to host (several) VNICs, or a single exclusive ExtLink. This current implementation leaves some cosmetic gaps in VNIC numbering (e.g., [duo_piano_vn_vnic0, opte1, duo_piano_vn_vnic2]) -- these don't affect the correctness of setup/teardown.

This PR allows for a network interface to be directly used in an
`ExtLink` rather than creating a new VNIC atop that device. This is
necessary to make use of pseudo-devices like OPTE ports, which are
directly used by Viona.

The preflight routine has a small change to verify that each interface
is only used to host (several) VNICs, or a single exclusive `ExtLink`.
This current implementation leaves some cosmetic gaps in VNIC numbering
(e.g., `[duo_piano_vn_vnic0, opte1, duo_piano_vn_vnic2]`) -- these don't
affect the correctness of setup/teardown.
@rcgoodfellow
Copy link
Copy Markdown
Collaborator

Hey @FelixMcFelix sorry for the delay in looking at this. Happy to work toward getting this in after #135 lands.

@FelixMcFelix FelixMcFelix merged commit c8567cd into main May 6, 2026
2 checks passed
@FelixMcFelix FelixMcFelix deleted the felixmcfelix/non-vnic-extlink branch May 6, 2026 09:53
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.

2 participants