Skip to content

docs(networking): instances attach to IncusOS-owned fast40 #25

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.

Sign up for GitHub

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

Merged
jmgilman merged 1 commit into from
Aug 25, 2026
Merged

docs(networking): instances attach to IncusOS-owned fast40 #25

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 9 additions & 3 deletions docs/docs/reference/networking/address-plan.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -131,9 +131,15 @@ LAGs, one per MS-02 SFP+ pair: `bond-lab01` (ports 1–2), `bond-lab02` (ports
interface. VLANs 30 and 40 are tagged on the three LAGs and port 7: VLAN 30
is the node storage network, and VLAN 40 carries Incus instance traffic so
workloads stay off the management plane. These links are not required for
IncusOS management boot. The host-side counterpart is the `vlan_tags`
allow-list converged by the `GilmanLab/fleet` `cluster/` project. Additional
instance VLANs join these links when their first consumer arrives.
IncusOS management boot. The host-side counterpart, converged by the
`GilmanLab/fleet` `cluster/` project, is the `vlan_tags` allow-list plus an
IncusOS-declared VLAN interface per carried VLAN (`fast30`, `fast40`).
Instances must attach to the IncusOS-owned interface (for example macvlan
with `parent=fast40`), never with an Incus-created `vlan=` sub-interface on
`fast`: the visible `fast` device is an IncusOS-internal VLAN-filtering
bridge, and only IncusOS-declared VLANs receive bridge self-port membership,
so other tagged sub-interfaces pass no traffic. Additional instance VLANs
join these links when their first consumer arrives.

## DHCP and DNS ownership

Expand Down