Skip to content

parker6: anycast DNS64 address and AP controller DHCP options - #1012

Merged
awlx merged 5 commits into
parkerfrom
awlx-parker6-firmware-dns64-address
Nov 21, 2026
Merged

awlx merged 5 commits into
parkerfrom
awlx-parker6-firmware-dns64-address

Conversation

@awlx

@awlx awlx commented Nov 21, 2026 •

Copy link
Copy Markdown
Member

Summary

This PR prepares the site configuration for parker6.

Part of #1011

Closes #1007

DNS64: one anycast address per site

The DNS64 server moves from one gateway to one anycast address per site. Every gateway of the site serves this address.

  • The config service gives the DNS64 address of each site to the node. The node uses the static servers only when the config service gives no site data.
  • The static fallback in ffmuc, ffdon, ffwert, ffbachtal_bachtal and ffdlg_dlg changes from 2001:678:ed0:ff00::d to the addresses of both sites:
    • 2001:678:ed0:f064::64 (MUC01)
    • 2001:678:e68:f064::64 (VIE01)
  • The addresses are site-local and are not in BGP. One address alone fails when the node is on the other site. Thus the fallback lists both.

UniFi and Omada controller DHCP options

Before this change, Parker routing nodes did not send the access point controller options. The classic gateways send 5.1.66.255 for both. The parker section of site.conf now sets the same address:

  • unifi_controller4: DHCPv4 option 43, suboption 1, for vendor class ubnt
  • omada_controllers4: DHCPv4 option 138

No domain overrides the parker section. Thus all parker domains get these options.

community-packages changes

The pin moves from 70dba2e to 5ad880c (head of parker-release-2026.11). These merged PRs are new:

The old pin already contains freifunkMUC/community-packages#51, freifunkMUC/community-packages#52, freifunkMUC/community-packages#54 and freifunkMUC/community-packages#55.

Gluon packages feed

FFBS rewrote the branch main-ffbs-next of https://gitli.stratum0.org/ffbs/packages. Commit b3a30be, which gluon-parker 029ea60 pins, is no longer on that branch. Thus make update failed.

Gateways: done

All pgws already serve the DNS64 address of their site: 2001:678:ed0:f064::64 on MUC01 and 2001:678:e68:f064::64 on VIE01.

Nodes can get this firmware at any time.

Tests

Lab image: v2026.11.1-parker5+cp5ad880c-parker6-lab (site a146859, community-packages 5ad880c)

Local checks:

  • All domain files and site.conf parse as Lua. Each domain shows both DNS64 addresses.
  • The new controller values agree with the check_site.lua rules of ffbs-mesh-vpn-parker (one IPv4 address, and a list of IPv4 addresses).
  • The new pin 5ad880c is a descendant of the old pin 70dba2e on parker-release-2026.11.
  • With the site modules file, the Gluon module script fetches the gluon feed from freifunkMUC/gluon-packages and finds b3a30be.

Lab results (all PASS):

  • Upgrade from parker5 to the lab image.
  • DNS64 through f064::64 for each site.
  • DHCPv4 options 43 (UniFi) and 138 (Omada) go to the clients.
  • respondd shows the correct client count.
  • Regression: site failover, gateway failover and carry-over of connections.
  • IPv6 recovers 10 to 18 s after a client cut. This is in the same range as parker5.
  • community-packages d5c1bea: lab PASS.
  • CLAT image (community-packages 361431a): lab PASS.
    • The counters increase in both directions.
    • Without CLAT, respondd has no clat key.
    • The CLAT stops cleanly.
    • The counters reset when the CLAT starts.
    • IPv4 through the CLAT works.

DNS64 static fallback (lab PASS):

  • Without site data from the config service, DNS64 works with the tunnel on MUC01 and on VIE01 (MUC01 cut).
  • With site data from the config service, DNS64 works on both sites.
  • The CLAT counters are still present.

Not tested:

  • Production nodes.

awlx added 2 commits November 21, 2026 09:21
The DNS64 server moves from pgw01 (2001:678:ed0:ff00::d) to one anycast
address per site. Every pgw of MUC01 serves 2001:678:ed0:f064::64.

This static server is the fallback when the config service gives no
per-site DNS64 address. Change it in ffmuc, ffdon, ffwert,
ffbachtal_bachtal and ffdlg_dlg.
Parker routing nodes did not send the AP controller options. The classic
gateways send 5.1.66.255 for both. Set the same address:

- unifi_controller4: DHCPv4 option 43 suboption 1 for vendor class ubnt
- omada_controllers4: DHCPv4 option 138
Includes:
- freifunkMUC/community-packages#60: tests: fix ShellCheck SC2317
- freifunkMUC/community-packages#61: count the clients of routing nodes
- freifunkMUC/community-packages#66: rx traffic as a second liveness check
- freifunkMUC/community-packages#67: report the CLAT traffic through respondd
@awlx
awlx force-pushed the awlx-parker6-firmware-dns64-address branch from 16be470 to e7c3fca Compare November 21, 2026 11:52
awlx added 2 commits November 21, 2026 12:54
The f064::64 addresses are site-local. A node on VIE01 without site
data from the config service cannot reach the MUC01 address. Thus list
the DNS64 address of both sites:

- 2001:678:ed0:f064::64: MUC01 (pgw01, pgw02)
- 2001:678:e68:f064::64: VIE01 (pgw03, pgw04)
…-packages

FFBS rewrote main-ffbs-next on gitli.stratum0.org/ffbs/packages. Commit
b3a30be, which gluon-parker 029ea60 pins, is no longer on that branch.
Thus make update fails.

The branch ffbs-parker-b3a30be in freifunkMUC/gluon-packages keeps this
commit. The site modules file overrides the Gluon pin. The commit is the
same, so the firmware content does not change.
@awlx
awlx merged commit eeb7bc9 into parker Nov 21, 2026
2 of 35 checks passed
@awlx
awlx deleted the awlx-parker6-firmware-dns64-address branch November 21, 2026 12:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants