No – we have not implemented any dynamic limitations. You always get the full performance of the components used.
FAQ - Network & IPs
In the public network, filters are active that prevent, for example, IP or MAC addresses that do not belong to you from being used. Of course, multicast and ARP will also be filtered. In the public network we support the usual MTU of 1500, in private networks there are no filters (not even on MACs) – here you have your own L2 domains with an MTU of up to 9000.
You can create as many private networks as you like, but there is a limitation to a maximum of 8 connected networks per server (the public network also counts here).
Each network connected to the server is its own virtual network card with its own MAC address.
You can assign both IPv4 and IPv6 to each server when you create it or later in the server element itself.
But we also give you the freedom to use servers without external IPs – e.g. for servers that should only be accessible in an internal network.
If you need more than one IPv4/IPv6 on a server, you can add additional IPs in the IP manager and mark them as failover. These IPs can then be manually configured on each of your servers.
Each server can have a maximum of one automatically configured IPv4 and one automatically configured IPv6 address.
However, you can configure any number of IP addresses in the IP Manager to “failover” and then manually set them in your server’s network configuration.
With a failover IP we do not interfere in the configuration and “activate” the IP addresses for all your servers.
If you start a server, then you can tell us under which of your IP addresses the server should be accessible and we configure the network interface automatically for you via DHCP.
However, there are situations where you may want to take control of the configurations. For example, if you want to use an IP address between multiple servers without talking to our API. This is what failover IPs are for. By setting an IP address to failover, we do not interfere with the configuration and “unlock” the IP addresses for all your servers. This way we offer you the possibility to set them up manually in the network configuration of your server.
With this function you can create and operate real HA solutions in the same way as in a physical data center. We wanted to transfer this standard into the cloud and found a very good solution with the failover IPs from gridscale.
We do not intervene in the connection of servers in the internal network. You can freely define IPs (or even your own VLAN tags). It is an absolutely transparent layer-2 connection.
No. You must either run your own DHCP server or statically configure the IPs in the private networks. However, we have an increasing demand for DHCP functions for internal networks. If you also have the need, then write us a short message and help us to prioritize this function in our roadmap.
Your question not found? - Write us your message
Not registered yet?
Sign up and create your first cloud server in seconds