[SOLVED] NetBox IPAM does not request IP

C

capm

New Member
Jun 1, 2026
5
0
1
Core Issue: After setting up NetBox IPAM, creating a Container or adding an Interface to an existing one, does not make an API call to NetBox.

PVE 9.1.1
Tested against NetBox v4.5.2 and v4.6.2

Steps taken....

Added IPAM
Name, token, url. When this is added, I do see an API call to /api/ipam/aggregates/

Add Zone
Add a Simple Zone, with the newly create IPAM. No other options are changed.

Add VNet
Add a new VNet, associated with the previous Zone

Add Subnet
Add a new subnet, 192.168.123.0/24, no other options, no DHCP ranges.

This results in 2 API requests,
GET /api/ipam/prefixes/?q=192.168.123.0
POST /api/ipam/prefixes/

And I can see the newly created Prefix, if I include the gateway, it will also allocate that IP.

Create Container
Pretty normal until the Network tab, I make sure my bridge is set to the VNet created above.
Set IPV4 to DHCP.

Now I would expect this would request a new IP but it doesn't. Instead, I get a 'dynamic' IPV6 address, despite IPV6 having
been left on Static.

Not sure what to try next, I've read every post/page related to NetBox IPAM, most people seem to have an issue starting the container, but I just can't get an IP.
What also kind of maddening, this is my ~5th attempt, but earlier on I did get it to make the API requests, but it still wasn't applying to the container interface.
And I haven't even been able to get back to that point.
 
Last edited:
capm said:
Core Issue: After setting up NetBox IPAM, creating a Container or adding an Interface to an existing one, does not make an API call to NetBox.

PVE 9.1.1
Tested against NetBox v4.5.2 and v4.6.2

Steps taken....

Added IPAM
Name, token, url. When this is added, I do see an API call to /api/ipam/aggregates/

Add Zone
Add a Simple Zone, with the newly create IPAM. No other options are changed.

Add VNet
Add a new VNet, associated with the previous Zone

Add Subnet
Add a new subnet, 192.168.123.0/24, no other options, no DHCP ranges.

This results in 2 API requests,
GET /api/ipam/prefixes/?q=192.168.123.0
POST /api/ipam/prefixes/

And I can see the newly created Prefix, if I include the gateway, it will also allocate that IP.

Create Container
Pretty normal until the Network tab, I make sure my bridge is set to the VNet created above.
Set IPV4 to DHCP.

Now I would expect this would request a new IP but it doesn't. Instead, I get a 'dynamic' IPV6 address, despite IPV6 having
been left on Static.

Not sure what to try next, I've read every post/page related to NetBox IPAM, most people seem to have an issue starting the container, but I just can't get an IP.
What also kind of maddening, this is my ~5th attempt, but earlier on I did get it to make the API requests, but it still wasn't applying to the container interface.
And I haven't even been able to get back to that point.
Click to expand...
Nice, glad you found the issue. That “allocate DHCP” option is easy to overlook, especially when the rest of the IPAM setup looks correct.Good to know the NetBox integration starts making the API calls once that’s enabled.
 
You must log in or register to reply here.
Top Bottom
Back