From 5a0b90c60b5e051c284839db8ee4d7a58bb0a382 Mon Sep 17 00:00:00 2001 From: Paul Wilde Date: Mon, 20 Jan 2025 15:27:39 +0000 Subject: [PATCH] add netcup ipv6 fbsd post --- .../my-battles-with-netcup-ipv6-on-freebsd/index.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/ponderings/my-battles-with-netcup-ipv6-on-freebsd/index.html b/ponderings/my-battles-with-netcup-ipv6-on-freebsd/index.html index 73d2e57..cf9fa0a 100644 --- a/ponderings/my-battles-with-netcup-ipv6-on-freebsd/index.html +++ b/ponderings/my-battles-with-netcup-ipv6-on-freebsd/index.html @@ -136,9 +136,9 @@ they have provided, but they also sent one via email, so I'll just use that for

2a03:4000 is Netcup's network I believe with AAAA defining a certain part of that network.
BBBB is the subnet provided to me with cccc:dddd:eeee:ffff being the range of address I can use in that subnet.

Netcup's IPv6 network is switched, not routed, I'm sure there's a reason for this, and I'm sure it's sensible, but for now the important bit is that the IPv6 gateway should always be fe80::1%vtnet0 (where vtnet0 is the external interface name) rather than another 2a03:4000::AAAA:BBBB IPv6 address. I pop that into my rc.conf as well.

-
...
-ipv6_defaultrouter="fe80::1%vtnet0"
-...
+
...
+ipv6_defaultrouter="fe80::1%vtnet0"
+...
 

 
Reboot the VPS, and all works well. ping6s work, curls to IPv6 addresses work, incoming IPv6 connections work. Great! Done...

 
Not Done.