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 |
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 |
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 ( |
not offered |
Board ssh is IPv4 only: the board pages give |
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 |
|---|---|---|
|
built |
At Welland: the site name, the Tiny Tapeout site (a |
A resolver the gateway can use |
built |
|
Optional: an internal zone for the fleet delegated to the gateway |
built, optional |
The upstream’s resolver delegates a zone ( |
A public zone for per-board names, |
designed (merged) |
Which zone, who serves it and whether it is signed are open decisions. |