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

Merge branch 'master' of git+ssh://code.ungleich.ch/ungleich-public/ungleich-staticcms

Browse source
This commit is contained in:
sanghee 2020-03-04 15:35:03 +01:00
commit 9c58eb4f13
3 changed files with 68 additions and 11 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

34
content/u/products/ipv4-to-ipv6-proxy/contents.lr
View file

@ -1,4 +1,4 @@
_discoverable: no
_discoverable: yes
---
_hidden: no
---
@ -6,3 +6,35 @@ title: IPv4 to IPv6 Proxy
---
subtitle: Make your IPv6 resources reachable from the IPv4 world
---
description1:
## Introduction
The IPv4-to-IPv6 proxy allows your IPv6 only resources to be reachable
from the legacy IP (IPv4) Internet. It supports the following
protocols:
* HTTP
* HTTPS
* IMAPS
## When to use the IPv4-to-IPv6 proxy?
If you have a website that is running on an IPv6 only webserver, you
can use this service to enable access from the IPv4 Internet to it.
It can be used with [IPv6onlyhosting.com](../ipv6-only-hosting) VMs or
other IPv6 only services in the Internet.
## Pricing
The IPv4-to-IPv6 proxy is free for up to 10 domains per VM for VM
customers.
* Up to 10 domains (for non VM customers): 5 CHF/month (0.5 CHF/domain)
* Up to 100 domains: 30 CHF/month (0.3 CHF/domain)
* Up to 1000 domains: 100 CHF/month (0.1 CHF/domain)
* Above 1000 domains: on request
The pricing includes traffic.

10
content/u/products/webhosting-with-ipv6/contents.lr → content/u/products/zerocarbon-webhosting-with-ipv6/contents.lr
View file

@ -1,4 +1,4 @@
_discoverable: no
_discoverable: yes
---
_hidden: no
---
@ -13,7 +13,7 @@ header:
#### generic-header ####
headers:
Zero Carbon
Zero Carbon
Web
Hosting
----
@ -68,7 +68,7 @@ offer1_text:
* Suitable for starting
---
offer1_link: https://ungleich.ch/product/0carbonwebhosting-s/
offer1_link: https://ungleich.ch/product/0carbonwebhosting-s/
---
offer2_title: Webhosting-M 22.5 CHF/Month
---
@ -82,7 +82,7 @@ offer2_text:
* Suitable for most websites
---
offer2_link: https://ungleich.ch/product/0carbonwebhosting-m/
offer2_link: https://ungleich.ch/product/0carbonwebhosting-m/
---
offer3_title: Webhosting-L 157.5 CHF/Month
---
@ -96,4 +96,4 @@ offer3_text:
* Suitable for websites publishing big data
---
offer3_link: https://ungleich.ch/product/0carbonwebhosting-l/
offer3_link: https://ungleich.ch/product/0carbonwebhosting-l/