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

++blog update

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

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

@ -19,7 +19,7 @@ body:
## TL;DR
IPv6 is a solution to the address sparsity in legacy IP (IPv4).
Only if you remove legacy IP, you really profit from IPv6.
Only if you stop using legacy IP, you really profit from IPv6.
The good news is, this has become rather easy nowadays.
## Current situation
@ -38,7 +38,7 @@ It is just a matter of time, until others have to follow.
## Legacy IP world reachability
One clarification just at the start: even if you go IPv6 only,
One clarification: even if you go IPv6 only,
**you can, will and want still legacy IP world reachability**.
When you surf with your mobile phone, when your home or company
@ -49,14 +49,15 @@ Also, if you are running a server, a virtual server, a website or any
other service, you probably want to be reachable from legacy IP
clients.
Good news is: **you don't need a dedicated legacy IP address**.
Good news is: **you don't need a dedicated legacy IP address** for any
of this.
Neither to reach the legacy Internet, nor to be reachable.
## History repeats
You might remember that in the nineties, https-webservers required
a dedicated **IP address per domain**. That's true, if **example.com**
You might remember that in the nineties, https webservers required
a dedicated **IP address per domain**. That's true. If **example.com**
and **example.org** were both using SSL certificates, the webserver
required at least 2 IP addresses. Later the SSL protocol was improved
to allow domain names to share one IP address. Today one IP address
@ -77,6 +78,23 @@ website](https://www.cio.gov/assets/resources/internet-protocol-version6-draft.p
For a good reason, because they want to reduce complexity. And costs,
obviously.
While there might be situations in which dual stack is required, in
general
* dual stack is more complex
* dual stack does not remove the costs
* dual stack almost always can be replaced by IPv6 only plus a gateway
translator
Even if you are not using public IPv4 space, you can still save costs
with going IPv6 only: whenever you connect to a VPN, whenever
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.
## Going IPv6 only
This brings us to the main topic of this article: going IPv6 only.
@ -89,6 +107,13 @@ 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/).
Or, if you want to have it much easier, you could go with
[IPv6 enabled webhosting](../zerocarbon-webhosting-with-ipv6/)
directly.
## Going IPv6 only network