FAQ - Networks
Can other projects see or access my internal networks
No. User-created networks are completely isolated from each other (even within a project).
Which IPv4/IPv6 ranges can I use for my internal networks?
Since the networks are fully isolated you can use all IPv4/IPv6 addresses. However we recommend that you use private addresses according to RFC 1918 (IPv4) or Link-Local / Unique-Local addresses (IPv6).
Does an instance necessarily need a public floating IP address?
Public IP addresses (so called floating IPs) are only required if an instance needs to be accessible from the outside. If an instance has no assigned floating IP and is connected to a virtual router, the connections that are initiated by the instance are established through the floating IP of the router (e.g. for OS updates or client services).
The public IPv4 address is not visible inside the instance even though it has been assigned a floating IP. Does the IP have to be configured inside the instance manually?
No! Inside the instance only the internal IP addresses are configured (per DHCP by default). The assignment to a floating IP takes place outside the instance.
I can not access my instance via SSH / RDP. What could be the issue?
Usually the the cause of such connection problems are missing or missconfigured security rules. You can find a short tutorial for configuring security groups here.
I can access my instance via SSH / RDP however errors occur e.g. during updates. What could be the reason?
Such problems can be caused by errors in name resolution. When creating a subnet you should always configure at least one DNS server. You can use the Heidelberg University DNS servers for this: 129.206.100.126 or 129.206.210.127