Directly attached IPs

There are two main ways to use public IP-space (globally accessible IP-space) in Binero cloud, directly attached IPs and Floating IPs. Directly attached IPs are assigned directly on the instances network interface (port). This means that when you run for instance ip addr show or ipconfig /all inside an instance operating system, you would (with a directly attached IP) see the public IP assigned on the interface. When using a floating IP, the result would instead be the ip from the private subnet that you assigned to the instance. The floating IP is then redirected (by using DNAT or SNAT) to and from the instance using the router.

Another key difference is that a directly attached IP is the only way to consume a public IPv4 without using a router. A router, in fact, cannot be connected to a directly attached IP or route traffic for one. Its possible to connect a router to an instance that has a directly attached IP but since they will both provide a default route, it will require configuration of the instance to use a manual IP and also use static routes on the instance facing the router. This is not a recommended approach.


Directly attached IPs are not designed to work well with routers. They are intended for single instances that just want an internet connection and nothing else.

Key differences to floating IPs

  • Since a directly attached IP is setup on the instance, nothing is “in front” of the IP. No NAT or firewall (unless using security groups). This might be an upside for some applications that does not work well through NAT or admins that want to manage their entire network stack on the instance.

  • Directly attached IPs have a slight performance improvement over routers because of no NAT and no virtualized network. This performance will be negligible in most use-cases.

  • Directly attached IPs does not combine with the majority of the networking functions in the platform which will rely on a router to work. For instance Load Balancer or Security groups.


For a more versatile approach to networking, we recommend using Floating IPs. The primary use-case for directly attached IPs would be single instances as its a less complicated method to reach the internet as well as publish services from an instance to be available on the internet.

Setting up a directly attached IP

The process for setting up a directly attached IP on an instance is not differing from any other method of setting up an IP in the platform except you would chose an IP from one of our exernal ranges instead of selecting one from a private subnet. Which range to choose would depend on in which availability zone your instance is located:

  • europe-se-1-1a-net0 for instances placed in europe-se-1a availability zone

  • europe-se-1-1b-net0 for instances placed in europe-se-1b availability zone

Doing so, would place a public IP directly on the interface (NIC) of the instance and you would be able to see it by running for instance ip addr show in linux.