From dc43ccf3bf41c0af11f93bd35bbaf53d7a3b7002 Mon Sep 17 00:00:00 2001 From: ScottW514 Date: Mon, 24 Aug 2026 16:42:19 -0400 Subject: [PATCH] docs: IPv6 proven end to end (CAMPAIGN-LOG, BRINGUP item 21) With the access point's RA and DHCPv6 off, the board took the firewall's lease; every service answered on the global address from another VLAN and the board reached the IPv6 WAN gateway. Docs only; no catalog consequence. --- docs/BRINGUP.md | 11 ++++++----- docs/CAMPAIGN-LOG.md | 7 +++++++ 2 files changed, 13 insertions(+), 5 deletions(-) diff --git a/docs/BRINGUP.md b/docs/BRINGUP.md index d20cc4d..85fe1fe 100644 --- a/docs/BRINGUP.md +++ b/docs/BRINGUP.md @@ -1560,11 +1560,12 @@ Open items only. Anything closed is in `CAMPAIGN-LOG.md`. quiet way) and the last stray dmesg line is gone. The missing GUA is a network matter, diagnosed (CAMPAIGN-LOG 2026-08-24, "the second DHCPv6 responder"): the firewall advertises an address, but an access point on - the bench VLAN still runs its own RA and DHCPv6 server, its Advertise - arrives first with nothing to give, and busybox's `udhcpc6` stays with - the first Advertise it sees. Disabling RA and DHCPv6 on that access - point (as on the other two) is the fix; nothing on the board changes. - Then the item-16 drill and the campaign. + the bench VLAN still ran its own RA and DHCPv6 server, its Advertise + arrived first with nothing to give, and busybox's `udhcpc6` stays with + the first Advertise it sees. With that access point's RA and DHCPv6 + disabled (as on the other two) the board took the firewall's lease, and + every service answered on the global address from another VLAN: IPv6 is + on end to end. Left: the item-16 drill and the campaign. **Deliberately not gated:** an armed GRBL job after an underrun cuts at the stale origin unless homing is required (GRBL mode permits unhomed cutting; the diff --git a/docs/CAMPAIGN-LOG.md b/docs/CAMPAIGN-LOG.md index ad1ceb7..9e75384 100644 --- a/docs/CAMPAIGN-LOG.md +++ b/docs/CAMPAIGN-LOG.md @@ -3872,6 +3872,13 @@ NDP-Proxy disabled, which is the setting that belongs on all three. The ULA the board carried all along was that access point's. Nothing on the board needs to change; the network side owns the fix. +With RA and DHCPv6 disabled on that access point, the next Solicit took +the firewall's lease: a global address on wlan0 (a /128 with the lease +as its lifetime, renewed on schedule), sshd, grblHAL TCP:23, forgectrl +and forgetest all answered on it from a host on a different VLAN, and +the board reached the IPv6 WAN gateway. IPv6 is on end to end; the +stale ULA ages out with its own lifetime. + ## Superseded status notes ### Shared machine services — remaining polish, as listed 2026-08-13