Additional IPv4 addresses
Add extra IPv4 addresses to a VM, billing, and guest OS configuration
Purchase extra IPv4 addresses for a VM from the same network prefix as its primary IPv4. Manage them on the VM detail page under Settings → Additional IPv4 addresses at /platform/virtual-machines/{id}.
NodeRings allocates the address, updates billing, syncs your firewall address book, and pushes the change to Proxmox. You configure the address inside the guest OS yourself — NodeRings does not apply it through cloud-init on running VMs.
Requirements
| Requirement | Details |
|---|---|
| Primary IPv4 | The VM must already have a primary IPv4 from the provider's IPAM. DHCP-only VMs without a static primary cannot add additional IPv4 addresses. |
| Plan addon | The provider must offer the ADDITIONAL-IP addon on your plan (fixed or usage-based, matching the plan billing type). |
| Limit | Up to 10 additional IPv4 addresses per VM. |
| Network | Each extra address comes from the same prefix as the VM primary IP (same gateway and subnet length). |
Add an additional IPv4 address
Open VM settings
Go to Platform → Virtual machines → select your VM → scroll to Additional IPv4 addresses on the detail page.
Add additional IPv4 address
Click Add additional IPv4 address. NodeRings assigns the next free address from your prefix and shows the new IP and gateway.
Configure inside the guest
SSH into the VM and add the address on your primary interface (see Guest OS configuration below).
The UI shows how many additional IPv4 addresses you have, the billed quantity, and copy buttons for the address and gateway.
Remove an additional IPv4 address
Click Remove latest on the most recently added address. NodeRings:
- Releases the IP back to IPAM
- Decrements ADDITIONAL-IP addon billing quantity
- Updates Proxmox firewall (ipfilter) on the hypervisor
- Removes the address from firewall address groups used in your rulesets
If you configured the IP inside the guest, remove it there as well so the OS does not keep a stale alias.
Removal always drops the latest additional IPv4 address, not a specific row you pick. Plan removals accordingly if you use multiple extras.
Billing
Billing follows your VM plan billing type. The provider sets prices; amounts below are typical template defaults and may differ on your marketplace plan.
| Plan type | How additional IPv4 addresses are billed |
|---|---|
| Fixed (subscription) | Monthly flat fee per additional IPv4 address. Adding mid-period triggers a prorated charge for the remaining VM billing period (billing month ≈ 730 hours, not a calendar month). |
| Usage-based | Per hour each additional IPv4 address is attached (additional-ip-hours), with a monthly cap per address. |
Examples (template defaults):
- Fixed plan: about $2.00/month per IP (prorated if you add late in the period)
- Usage plan: about $0.06/hour per IP, capped at about $2.00/month per IP
When you add an IP, the UI may show a billing message with the immediate charge (fixed plans) or a note that usage is metered (usage plans). See Billing for invoices and subscriptions.
Removing an additional IPv4 address stops future billing for that address. Fixed-plan mid-period removals do not refund the current period; usage plans stop metering from release time.
What NodeRings updates automatically
| Layer | Behavior |
|---|---|
| IPAM | Allocates or releases IPv4 from the VM primary prefix |
| Proxmox | Operator reconciles ipfilter IPSets so the VM may use the new address (anti-spoofing / firewall) |
| NodeRings firewall | Address book entries for /32 hosts used in address groups |
| Guest OS | Not configured automatically on existing VMs — you add the alias manually |
Provisioning a new VM with additional IPv4 addresses at create time still only sets the primary IP via cloud-init; any extras added later are manual inside the guest.
Guest OS configuration
Use the IP address, gateway, and prefix length shown in the UI (prefix matches your primary IP, often /24 or /32 depending on the provider prefix).
Linux (temporary — lost on reboot)
Replace interface name and values with yours:
# Example: add 10.0.0.6/24 on eth0
ip addr add 10.0.0.6/24 dev eth0
# Verify
ip addr show eth0Linux (persistent)
Use your distro's network manager:
- Netplan (Ubuntu): add a secondary address under the matching
ethernetsentry, thennetplan apply - NetworkManager:
nmcli con mod … +ipv4.addresses 10.0.0.6/24then reactivate the connection - ifcfg / RHEL: add
IPADDR1,PREFIX1, or analiasfile under/etc/sysconfig/network-scripts/(legacy layouts)
Use the same gateway as your primary IP only if your setup requires explicit routes; many secondary addresses on the same subnet need no extra default route.
Windows
Settings → Network → adapter → IP assignment → Edit → add a secondary IPv4, or use netsh interface ip add address.
If you add a restrictive firewall ruleset, allow traffic to and from the new address (or update address groups). Proxmox ipfilter allows the IP on the hypervisor, but your NodeRings rules still apply.
Marketplace and checkout
Some plans include ADDITIONAL-IP as an optional addon at VM create time. You can also add addresses after the VM is running from the VM settings card — you do not need to recreate the VM.
On the marketplace, look for Additional IPv4 on fixed or usage plans. Addon billing type must match the plan (fixed addon on subscription plans, usage addon on usage plans).
Troubleshooting
| Symptom | What to check |
|---|---|
| Add button disabled | VM has no primary IPv4, or you already have 10 additional IPv4 addresses |
| Addon / billing error | Plan may not include ADDITIONAL-IP, or billing type mismatch — contact the provider |
| IP shows in UI but not reachable | Configure the alias inside the guest; confirm firewall rules allow the address |
| Cannot ping from internet | Provider routing, firewall rules, or missing guest config — verify all three layers |
For provider-side limits (prefix full, operator delay), open a support ticket.
Next
- Virtual machines — fleet and VM detail
- Firewall — rulesets and address groups
- Billing — invoices and subscriptions