docs: use the real WireGuard tunnel addresses in the prod peering configs

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
Rayhaan JaufeerallyandClaude Fable 5.1 committed 2026-09-19 16:05:44 +02:00
1 parent e41776f253
commit 22384d0b07
2 files changed
+4 -4

No files matched your search

+2 -2
View File
@@ -51,8 +51,8 @@ filter ferrix_import
protocol bgp ferrix
{
description "ferrix_bgp teaching lab (announce only)";
local fd00:179::1 as 210036;
neighbor fd00:179::2 as FERRIX_ASN;
local 2a0d:d747:1::1 as 210036;
neighbor 2a0d:d747:1:: as FERRIX_ASN;
direct;
# ferrix dials us. Staying passive avoids log noise from failed attempts
+2 -2
View File
@@ -5,11 +5,11 @@ local_asn: 4200000001 # private; stripped by the production router
# IPv6 prefixes are only announced over an IPv6 session, and the next hop is
# our end of it, so listen and dial on the tunnel's IPv6 address.
listen_endpoints { address: "fd00:179::2" port: 179 }
listen_endpoints { address: "2a0d:d747:1::" port: 179 }
peers {
name: "prod"
endpoint { address: "fd00:179::1" port: 179 }
endpoint { address: "2a0d:d747:1::1" port: 179 }
remote_asn: 210036
hold_time_seconds: 90
}