IPv6 and DNS

You are setting up a site’s upstream and need what it must provide for IPv6 and for the site’s names. Each requirement says whether it is built (the deployed gateway relies on it now) or designed (a design, merged or in draft, needs it and no code uses it yet), as on the landing page.

IPv6

Requirement

State

Notes

A global IPv6 address for the gateway’s uplink

built at Welland

IPv6 clients reach the web site and the WebRTC media port on it directly, with no forwarding. ps1’s gateway had no global IPv6 address on 6 October 2026 (its read), so none of the IPv6 rows holds there.

The upstream lets tcp 80, 443 and 22, and tcp and udp webrtc_media_port (8189 at Welland, Inbound IPv4), reach the gateway’s own global IPv6 address

built

Relied on today: the web site, the camera media, and ssh for operators and deploys. On 2026-10-07, from outside, tcp 22, 80 and 443 reached Welland’s gateway at its global IPv6 address (2404:e80:a137:2100::1); the media port was not checked then.

A prefix routed to the gateway’s uplink address, large enough for one /64 per fleet switch (a /56 at Welland)

built, and in effect on the boards (read 2026-10-14 on one host)

Each board gets one address inside its switch’s /64. The gateway is the router for the prefix; the upstream only needs a route to it. The prefix is routed by a static route to the gateway’s static IPv6 uplink address, and must not change. The inventory runs no prefix-delegation client. The gateway side is roles/pxe (templates/ports.conf.j2: one DHCPv6 address per port, and enable-ra); on 2026-10-07 the gateway’s interface for switch 2 port 43 had its address in the switch’s /64 (the per-switch /64 is {pib_network6_base}{switch:02d}:: and a board’s address …::{port}, ansible/filter_plugins/port_vlans.py). The boards do not take the address by DHCPv6 or router advertisement. Each sets it, and a default route via its switch’s …::ffff, statically from its switch and port: first with fpgas-ipv6.service (fpgas.online-infra PR #251, 7 October 2026), and now with systemd-networkd’s .network file (The network after boot). On 2026-10-14 pi-sw2-p43 held 2404:e80:a137:2102::43/128 and a default route via 2404:e80:a137:2102::ffff (read on the board, read-only). On 2026-10-07, before PR #251, it had only a link-local address.

The upstream does not filter the board prefix, or filters it to the same ports the gateway allows

designed (an unmerged draft)

The gateway’s forward chain decides what reaches a board. An upstream filter in front of it must allow at least ICMPv6, and tcp 22, 80 and 443 to the prefix, or direct IPv6 access to boards cannot work. Both filters have to agree, and both have to be checked.

Per-board ssh and aux ports (<s><pp>22, <s><pp>44) on the gateway’s global IPv6 address

not offered

Board ssh is IPv4 only: the board pages give ssh -4. On 2026-10-07 Welland’s upstream refused the per-board ssh ports over IPv6 before they reached the gateway (a capture on the gateway saw none of those SYNs, while SYNs to other ports arrived), and the gateway forwards these ports for IPv4 only (table ip nat). OpenSSH, which tries the IPv6 address first, falls back to IPv4 (recorded 2026-10-07). IPv6 access to the boards is for the direct-addressing design (a draft); whether to forward the per-board ports over IPv6 instead is open.

Reverse DNS for the prefix routed to the gateway

designed (an unmerged draft)

Needed for per-board names to have matching reverse records.

DNS

Requirement

State

Notes

A records for every public name of the site pointing at the public IPv4 address, and AAAA records pointing at the gateway’s global IPv6 address

built

At Welland: the site name, the Tiny Tapeout site (a CNAME to it) and the package cache name. The names live in the public fpgas.online zone, which is not served by the site. The package cache name and its certificate exist only where apt_cache_enabled is true; PS1 sets it false.

A resolver the gateway can use

built

eth_uplink_dns_server. The gateway runs its own resolver for the fleet and forwards to this one.

Optional: an internal zone for the fleet delegated to the gateway

built, optional

The upstream’s resolver delegates a zone (dnsmasq_auth_zone) to the gateway with an NS record and glue. The glue address must be reachable from the upstream resolver. Its queries arrive on the gateway’s uplink, so their source address must be listed in firewall_dns_query_sources. A site that does not want this leaves the dnsmasq_auth_* variables (zone, glue, subnet, interface) unset.

A public zone for per-board names, <site>.fpgas.online, with SSHFP records

designed (merged)

Which zone, who serves it and whether it is signed are open decisions.