vgk/ungleich-staticcms
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

correct urls

Browse source
This commit is contained in:
Nico Schottelius 2020-03-04 15:36:34 +01:00
parent 0e49790d85
commit 0310fc83be
1 changed files with 5 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
content/u/blog/only-ipv6-only/contents.lr
View file

@ -1,4 +1,4 @@
title: Only IPv6 Only.
title: Only IPv6 Only
---
pub_date: 2020-03-04
---
@ -92,7 +92,7 @@ companies merge networks, even [when you only run
docker](../how-ipv4-stops-me-from-working-in-the-train/):
with [private ip addresses](https://en.wikipedia.org/wiki/Private_network) you can
easily run into overlapping addresses. This costs time and in the end
resources.
resources, not in theory, but in practice.
## Going IPv6 only
@ -106,11 +106,11 @@ Internet. But how does this work in practice?
It is very easy to create a static website on an IPv6 only webserver
and have it reachable from IPv6 and the legacy Internet:
you can either [create an IPv6 only virtual
machine](../ipv6-only-hosting/), setup a webserver on it and use the
[IPv4 to IPv6 proyx](../ipv4-to-ipv6-proxy/).
machine](../../products/ipv6-only-hosting/), setup a webserver on it and use the
[IPv4 to IPv6 proyx](../../products/ipv4-to-ipv6-proxy/).
Or, if you want to have it much easier, you could go with
[IPv6 enabled webhosting](../zerocarbon-webhosting-with-ipv6/)
[IPv6 enabled webhosting](../../products/zerocarbon-webhosting-with-ipv6/)
directly.