How is my colocation connected to the Internet?

One RJ45 Ethernet uplink is available per colocation. It does not have any (port) filters, your device is directly connected to the IPv6 Internet and must be secured accordingly, so unnecessary and unprotected listening network services must be avoided. We have listed 5 basic Linux hardening rules in our GitHub Wiki.

The well-known IP protocol is used on the routing level. So far no special features but please note: You are booking an IPv6-only colocation! That means in the first place: You get a public IPv6 address, but no IPv4 address. If you establish a (SSH, HTTPS, …) connection to the computer of your colocation, then this always happens via IPv6.

But what does IPv6-only colocation mean in detail?

It means that our entire internal network is based on the IPv6 standard and your devices must be able to handle static IPv6 addresses. This is the case for all commercially available systems, especially for single board computers with modern Linux versions (e.g. Raspberry Pi OS).

Outgoing IPv4 works fine

However it does not mean that your colocation cannot reach IPv4 addresses on the Internet. Like most IPv6 hosters, we provide a NAT64/DNS64 service that automatically converts between the two protocol versions (unnoticed by your devices). So in your operating system you only have to make the usual network settings, but no additional ones, to reach (almost) the whole Internet. Almost because NAT64/DNS64 requires the use of DNS hostnames in communication, which is practically always the case in reality. However, if you need to address IPv4 addresses directly or have other special cases, our colocation may be less suitable for you. Please familiarize yourself with the advantages and disadvantages of NAT64/DNS64 in these cases.

More network details can be found here:

Leave a Reply