Here you will find an overview of important network-related topics. gridscale offers the use of public IPs as well as the use of internal networks.
Each server can be assigned both an IPv4 and an IPv6 address. You can either select existing ones or create a new one with one click. IP addresses can be connected either directly in the creation process or afterwards.
All purchased public IPs overview are visible in the “IP-Manager”.
A public IP is assigned to a connected Server via DHCP. You can also assign the IP in a static mode but you have to choose the correct WAN Interface on your server.
IP and Server Network Ordering
By default the first connected network will be your WAN interface in the server. If you need your WAN on another interface (mostly for Firewalls as there is a management interface on the first one) you have to connect the private network first and the public one afterwards.
A click on the network tile shows the MAC addresses, which are numerically ordered.
Multiple Public IP Addresses
In case you need more than one IP on a server you can assign a second one via “IP-Manager” (or choose an existing one) and you have to set this one to “Failover IP”. Setting an IP address as a failover enables you to use it to manually configure a group of redundancy within your infrastructure, or simply allow you to transfer traffic between configured servers with ease. Failover IPs need a manual configuration on your server (e.g. Alias) through the interface.
We do not allow CARP on our Public Network.
We give you the freedom to use servers without external IPs - for example, servers that should only be accessible in an internal network. A Private Network functions as a Layer 2 network.
Networking Between Accounts
Private Networks cannot span over projects and other public accounts. If you have to setup an internal network over projects you can upgrade to our Partner Panel and use the extended Software-Defined Network (SDN) feature.
There is no option to use VLAN in our private networks. In case you need this for any reason you can setup a VLAN on your server’s network interface.
VLAN is supported by our SDN, which is explicitly available by upgrading to our Partner Panel.
Security Zones connect your managed database service to your infrastructure, and the network configuration is completely automated. For increased security they are private networks located in a separate zone and are not connected to the public Internet, allowing your service to run encapsulated. You can either use the default Security Zone or create and name your own Zone. A Security Zone will be created automatically when you create a platform service.
Our PaaS works only with IPv6. After creation of a service like MySQL you have to connect your server with the assigned Security Zone - you easily can do that by Drag and Drop. After connecting your server with your private Security Zone an IPv6 will automatically be assigned to that interface.
To receive a private IP Address, you will need to enable DHCP on your private network.
DHCP is also available for Virtual Switches and should be configured by the Partner.
By default, the DHCP server provides IP addresses in ascending order to servers connected to the private network. The default network range is 192.168.121.0/24 - and this can be customised via the api, with future support coming to the panels.
Warning: changing the DHCP range manually will override any previously saved confiration and IP leases if they’re not within the new range.
Once a server is connected, the servers private IP Address can be seen via the network relation via the API, or via the network relations within the Panel.
Turning off DHCP, will not reset the configuration, and the server will keep it’s private IP on the network interface until restarted.
Note: if you have a server connected to multiple DHCP networks, make sure to customise the IP range served via DHCP, servers connected to multiple networks with overlapping ranges can cause unintended network issues.
It is possible to specify a DNS or Gateway Server IP Address via the API. We do not provide DNS or Gateway functionality, but reserve the addresses for you to provide these services if you wish. Just fix the IPs to your DHCP option servers connected to the network.
These IP addresses must reside within the networks IP range.
Subnets can be reserved via the api. Keep a few things in mind when reserving a subnet:
- The subnet must exist within the IP range: the default is 192.168.121.0/24.
- The subnet cannot confict with DNS/Gateway addresses given.
- The subnet should not conflict with any IP which you have fixed to a server.
Fixing IP Addresses
Once a server is connected to a private network with DHCP enabled, it’ll dynamically receive an IP address. If you would like a specific IP address to be fixed to that server, you can do so via the API.
Fixed IPs have to be within the network range, and have to be outside of the reserved subnets or reserved gateway/DNS addresses.