Networking for VMs

Every Cloud VM ships with networking ready to use: a public IPv4 address, a metered outbound bandwidth allowance, and DHCP on the primary interface. This page explains the defaults and the controls available to you.

Default network setup

The VM list shows the assigned public IP under the IP Address column once provisioning completes (for example 103.149.10.116).

Inside the guest

The primary NIC uses virtio-net. Most cloud images bring the interface up automatically via DHCP at boot. To check:

$
ip -4 addr show
$
ip route

You should see a public IP on the primary interface and a default route via the IBEE gateway.

Firewalls

Cloud VMs deploy with no firewall attached — all traffic is allowed unless your guest OS enforces it. To restrict traffic at the platform level, attach an IBEE firewall:

• Define inbound rules for ports/protocols you want to expose (SSH, HTTP/HTTPS, custom).
• Define outbound rules if you need to constrain egress.
• Attach the firewall to one or more VMs from the firewall detail page.

Inside the guest, you can also run ufw, firewalld, or Windows Defender Firewall — they stack with platform firewalls.

DNS

Use IBEE DNS (or any external DNS provider) to point a domain at your VM:

1. Create a zone for your domain.
2. Add an A record for the VM’s public IP, or an AAAA record for its IPv6.
3. Add a CNAME for www if needed.

For TLS, IBEE issues and renews SSL certificates once your DNS resolves.

Bandwidth and overage

Each plan includes a monthly outbound bandwidth allowance (for example 2 TB on std.1.c2.m8). The Monitoring tab’s Network chart shows current inbound and outbound throughput.

• Inbound traffic is unmetered.
• Outbound usage above the included allowance is billed per GB; see your plan summary for the rate.

Load balancing

To put a load balancer in front of multiple VMs, use Load Balancer:

• Create the load balancer in the same region as your VMs.
• Attach the VMs as backends and configure a health check.
• Optionally terminate TLS at the load balancer.

Private networking

VMs in the same region share a regional backplane and can communicate using their public IPs without traversing the internet (traffic stays within the IBEE network). Private VPCs and dedicated subnets are on the roadmap; check the changelog or Networking overview for the current state.

Troubleshooting

VM has no public IP after deploy Refresh the VM list — the column updates after provisioning completes. If it stays blank for more than a few minutes, open the Activity feed; a failed VM create will surface here.

Can’t SSH but the VM is Running

• Confirm a firewall isn’t blocking port 22.
• Use the Console to log in and check sshd status, then verify your SSH key was injected (~/.ssh/authorized_keys).
• If the wrong key was added at deploy time, replace it via the console and add the right one.

Bandwidth chart looks flat or empty The chart smooths over its time range. Switch to 30m for short-window detail.

Related pages

• Create a VM
• Firewalls
• DNS
• Load Balancer
• SSL Certificates