psw/web
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

added TL; DR: to netcup ipv6

Browse source
This commit is contained in:
Paul Wilde 2025-01-20 22:48:21 +00:00
parent 4a8a1c2cb1
commit a360f22f3e
2 changed files with 19 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

19
ponderings/my-battles-with-netcup-ipv6-on-freebsd/index.html
View file

@ -119,7 +119,24 @@ as I have found their offerings more performant, and less expensive, than other
VPS providers.<br />
However, it seems due to the way Netup's IPv6 network is set up causes some issues
with FreeBSD, and allegedly other BSDs leading to loss of connectivity via IPv6.</p>
<span id="continue-reading"></span>
<span id="continue-reading"></span><h3 id="tl-dr">TL;DR:</h3>
<p>Using Netcup's IPv6 gateway <code>fe80::1</code> with FreeBSD results in eventual lost connectivity with IPv6.<br />
Instead of using the link-local address for a gateway, using IPv6 addresses in the same /48 range as your provided IPv6 range, and setting your IPv6 address prefix to /48 instead of /64 seems to work fairly reliably.<br />
For example if Netcup provide you with IPv6 range: <code>2a03:4000:AAAA:BBBB::/64</code>, you would set this statically in your <code>rc.conf</code> but as a /48, and set <code>2a03:4000:AAAA::2</code> and/or <code>2a03:4000:AAAA::3</code> as your gateway.</p>
<pre data-lang="conf" style="background-color:#212121;color:#eeffff;" class="language-conf "><code class="language-conf" data-lang="conf"><span style="font-style:italic;color:#4a4a4a;"># /etc/rc.conf
</span><span style="font-style:italic;color:#4a4a4a;">#ifconfig_vtnet0_ipv6=&quot;inet6 2a03:4000:AAAA:BBBB:cccc:dddd:eeee:ffff/64&quot;
</span><span style="color:#f78c6c;">ifconfig_vtnet0_ipv6</span><span style="color:#89ddff;">=</span><span style="color:#c3e88d;">&quot;inet6 2a03:4000:AAAA:BBBB:cccc:dddd:eeee:ffff/48&quot;
</span><span style="font-style:italic;color:#4a4a4a;">#ipv6_defaultrouter=&quot;fe80::1%vtnet0&quot;
</span><span style="color:#f78c6c;">ipv6_defaultrouter</span><span style="color:#89ddff;">=</span><span style="color:#c3e88d;">&quot;2a03:4000:AAAA::2&quot;
</span></code></pre>
<p>add other routes with</p>
<pre data-lang="sh" style="background-color:#212121;color:#eeffff;" class="language-sh "><code class="language-sh" data-lang="sh"><span style="color:#82aaff;">route</span><span style="color:#89ddff;"> -</span><span style="color:#f78c6c;">6</span><span style="color:#82aaff;"> add default 2a03:4000:AAAA:3
</span></code></pre>
<p>I've had most reliability setting <em>both</em> <code>::2</code> and <code>::3</code> gateways, YMMV.<br />
It appears in each Netcup /48 subnet <code>::2</code> and <code>::3</code> are gateways.</p>
<hr />
<p>On with the full story...</p>
<h3 id="netcup">Netcup</h3>
<p>I have moved to Netcup for a few reasons: 1. expense, 2. experienced better performance than my previous provider, and 3. ability to provide my own ISOs for OS install.<br />
Netcup in my experience are great, I have a few Debian systems with them that have been super reliable.<br />
But, I want to use FreeBSD for my projects, so my new VPSs run FreeBSD.</p>

2
search_index.en.js
View file

File diff suppressed because one or more lines are too long