nixos/home: Keep untrusted to the Internet

The routers reject new connections from the `untrusted` VLAN to
internal destinations before the firewall's ICMP rules, then allow
Internet transit via `wan` and `as211024`. The shared
`lib.my.c.internalNets` also covers the modem's management subnet.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-11-18 22:01:54 +00:00
co-authored by Claude Opus 5.5
parent 89cc4b679c
commit 5fb8e8d280
5 changed files with 56 additions and 27 deletions
+20 -2
View File
@@ -363,6 +363,24 @@ instead anchor DNS on the VIPs via the shared `lib.my.c.home.vlanDns "<vlan>"` f
`DNS` to `vips.<vlan>.{v4,v6}` and `Domains` to the advertised search list; the always-present
static v4 VIP keeps resolution working even with v6 down.
#### Untrusted clients
The routers restrict clients on the `untrusted` VLAN to Internet destinations. The filter also
blocks access to colony, where the home prefixes are trusted across the mesh.
- `forward-early` sends new connections from `lan-untrusted` to `untrusted-internal`, which rejects
everything in `lib.my.c.internalNets`: private, CGNAT (Tailscale), link-local, multicast and
reserved IPv4, IPv6 ULA / link-local / multicast, and our own global IPv6 prefixes. It runs
before `forward`, whose ICMP rules would otherwise let pings through.
- `filter-untrusted` then accepts `wan` and `as211024` (IPv6 Internet transit) and rejects the
rest.
- Rejecting rather than dropping makes clients fall back from colony's IPv6 addresses (such as
`git.nul.ie`'s) to IPv4 immediately.
- Replies to connections from `hi` and `lo` are allowed, so trusted boxes can still reach
`untrusted` hosts.
- Traffic to the routers themselves goes through the same `input` rules as `wan`.
- Clients on `untrusted` share layer 2 with each other; the routers can't filter that.
#### DNS binding
`pdns-recursor` binds the VIPs directly; see
@@ -406,8 +424,8 @@ The bare-metal backup uses DHCP from the Virgin Media modem on `wan` (VLAN 130),
The full fabric story — which switch port carries what, why VLAN 10 is trunked untranslated,
and the multi-ONT plan — is in [sites/home/switches.md](sites/home/switches.md); the
`my.homeRouter.*` options (`dns.wanSkipBroadcasts`, `firewall.untrustedRejectV4`) let each box
tell `routing-common` about subnets sharing its WAN interface.
`my.homeRouter.dns.wanSkipBroadcasts` option lets each box tell `routing-common` about subnets
sharing its WAN interface.
## The AS211024 L2 mesh
+5 -9
View File
@@ -68,15 +68,11 @@ uses the DOCSIS overhead preset.
### Per-box `routing-common` options
The modem's management subnet shares the `wan` interface, which `routing-common` itself knows
nothing about — it declares two per-box options
([`routing-common/default.nix`](../../../nixos/boxes/home/routing-common/default.nix)) that this
box sets:
- `my.homeRouter.dns.wanSkipBroadcasts` — skip the modem subnet's broadcast address when
auto-selecting the router's own `wan` A record for the zone's LUA record.
- `my.homeRouter.firewall.untrustedRejectV4` — reject untrusted clients from
reaching the modem subnet (needed only because it shares `wan`; WAN egress is otherwise
accepted).
nothing about. This box sets `my.homeRouter.dns.wanSkipBroadcasts`
([`routing-common/default.nix`](../../../nixos/boxes/home/routing-common/default.nix)) to skip the
modem subnet's broadcast address when auto-selecting the router's own `wan` A record for the zone's
LUA record. `untrusted` clients can't reach the modem subnet: it's private, so the
[`untrusted` filter](../../networking.md#untrusted-clients) rejects it.
## Switching (RSTP)