Networking
Bamboozle's cloud networking lets you control how your servers connect to each other and to the internet. Navigate to Cloud → Networking to access all networking resources.
Networks
A network is a private virtual Layer 2 segment your servers communicate on. Each project comes with a default public network already configured — new servers connect to this automatically.
Creating a network
Click + Create Network to open the creation wizard.
Network
Give the network a name. This is for your reference only.
Subnet
A subnet defines the IP address range (CIDR block) and DHCP settings for the network.
- Network Address (CIDR) — e.g.
192.168.1.0/24. This defines the range of private IPs that will be assigned to servers on this network. - Gateway IP — The default gateway for servers on this subnet (usually the first usable IP, e.g.
192.168.1.1). - DHCP — Enable to automatically assign IPs to servers joining the network.
DNS
Enter one or more DNS nameservers for servers on this network to use for domain resolution. You can use public resolvers (e.g. 8.8.8.8, 1.1.1.1) or your own.
Routers
A router connects your private networks to the public internet (or to each other). You need a router to assign Floating IPs and to give servers on private networks outbound internet access.
Creating a router
Click + Create Router.
- External Network — Select the upstream public network this router connects to. This provides internet access.
- Interfaces — After creation, add interfaces to connect the router to your internal networks.
Adding an interface
Open the router, go to Interfaces, and click + Add Interface. Select the subnet you want the router to connect to. This makes the router the gateway for that subnet.
Floating IPs
A Floating IP is a public IP address that you control independently of any specific server. You can assign it to a server, then reassign it to a different server at any time — without changing DNS or your server's configuration.
Allocating a Floating IP
Click + Allocate Floating IP. Select the external network pool and confirm. The IP is reserved for your project until you release it.
Assigning to a server
From the Floating IP list, click Associate next to the IP and select the server port to attach it to. The server immediately becomes reachable on that public IP.
Releasing a Floating IP
Click Disassociate to detach it from a server, then Release to return it to the pool. Released IPs are no longer billed and cannot be recovered.
Floating IPs are billed from the moment they are allocated, even if not attached to a server.
Security Groups
Security groups are virtual firewalls you attach to servers to control inbound (ingress) and outbound (egress) network traffic.
Default security group
Every project has a default security group. It is automatically applied to new servers unless you specify otherwise. By default it allows all outbound traffic and blocks all inbound traffic except responses to established connections.
Creating a security group
Click + Create Security Group, give it a name and optional description.
Adding rules
Open a security group and navigate to Ingress Rules or Egress Rules.
Click + Add Rule and fill in:
| Field | Description |
|---|---|
| Direction | Ingress (inbound) or Egress (outbound) |
| Protocol | TCP, UDP, ICMP, or Any |
| Port / Port Range | Single port (e.g. 22) or range (e.g. 8000-9000). Leave blank for all ports. |
| Remote | The source/destination — either a CIDR range (e.g. 0.0.0.0/0 for anywhere) or another security group. |
Common rules:
| Purpose | Direction | Protocol | Port | Remote |
|---|---|---|---|---|
| Allow SSH | Ingress | TCP | 22 | Your IP or 0.0.0.0/0 |
| Allow HTTP | Ingress | TCP | 80 | 0.0.0.0/0 |
| Allow HTTPS | Ingress | TCP | 443 | 0.0.0.0/0 |
| Allow ping | Ingress | ICMP | — | 0.0.0.0/0 |
| Allow all outbound | Egress | Any | — | 0.0.0.0/0 |
For production servers, restrict SSH access to your own IP rather than 0.0.0.0/0.
Attaching to a server
Security groups can be applied during server creation or added/removed afterwards via the server's Security Groups page.
Load Balancers
Load balancers distribute incoming traffic across multiple servers, improving availability and scalability. Navigate to Networking → Load Balancers to manage them.
A load balancer sits in front of a pool of servers (a backend pool). Incoming requests are distributed across pool members according to the selected algorithm (round-robin, least connections, etc.).