Network#
Fifteen jobs, in three groups: making an interface exist, deciding where packets go, and using more than one way out.
Interfaces#
| Guide | The job |
|---|---|
| Add a VLAN | A tagged sub-interface on a physical port |
| Bridge two ports | One layer-2 segment across two NICs |
| Bond two ports | Two NICs, one logical link, 802.3ad |
| A PPPoE uplink | The addressing most DSL and some fibre providers use |
| GRE, IPIP, SIT and VXLAN interfaces | Tunnel interfaces, and what each is for |
Where packets go#
| Guide | The job |
|---|---|
| Add a static route | A prefix, a next hop, and a distance |
| Shape a link with CAKE | Egress shaping, and what the editor can and cannot express |
| A BGP session | One neighbour, one AS |
| An OSPF area | An area and the interfaces in it |
| IPv6: what is configurable and what is not observable | The honest state of IPv6 here |
More than one way out#
An uplink is any interface that carries a default route — VyOS has no gateway object. The Uplinks tab finds them through all five mechanisms and joins them with the live forwarding table.
| Guide | The job |
|---|---|
| A second uplink with health-checked failover | The one most people want |
| Share load across two uplinks | New connections spread by weight |
| Send one subnet out a chosen uplink | "The cameras go out through LTE" |
| Masquerade behind each uplink | One source NAT rule per uplink |
| Two routers, one virtual address | VRRP, and what it does and does not give you |
Checked against docs/multi-wan.md ·
agent/wan.go ·
ui/src/pages/Interfaces.tsx ·
ui/src/pages/Wan.tsx