Conference Network Report#

Yoshinobu Matsuzaki, IIJ (APRICOT Technical Committee)

• Why: A compact live postmortem from running a real network under load — including an IPv6-mostly deployment with measured client behavior and a genuinely unusual BGP debugging story.
• What: The APRICOT 2026 NOC ran dual transit (Lintasarta, Envision) plus Starlink backup, Akvorado NetFlow analysis, and an IPv6-mostly design: 609 unique MACs, 70% of clients (431) operated IPv6-only via NAT64 (DHCPv4 option 108 signaling), 30% dual-stack, 300 Mbps peak. Incidents and fixes: WiFi channel overload at the opening plenary; a BGP "ghost route" — their prefixes showed globally reachable via route-views/RIS but lacked actual reachability, traced to a longer-than-expected AS_PATH left over from an earlier temporary announcement, cleared by contacting ASes on the path (one had a config bug); a rogue AP broadcasting the same SSID/password outside controller management, fixed by a reset; and intermittent public-DNS resolution failures on IPv4 queries with RD=1, fixed by offering local resolvers via RDNSS/DHCP.
• How: Straightforward ops: PREF64/NAT64 for the v6-only tier, per-incident triage with community help on the ghost route.
• Where applicable: Conference scale, but the lessons — IPv6-mostly is now viable for 70% of unmanaged clients, stale AS_PATHs can linger as ghost routes after withdrawals, rogue APs happen even with a controller — transfer directly to enterprise and campus networks.