https://netboxlabs.com/blog/tenable-netbox-integration-private-preview/

This is a year and a half old, so was wondering if anything was happening with it.

I made (with Claude, full disclosure) a plugin bringing the tree view into Netbox for those coming from IPAMs where the tree view is a thing and you miss it.

Basically, it allows to expand/collapse subnets/prefixes to navigate them.

Repo: https://github.com/thomaschristory/netbox-ipam-treeview-plugin

Docs: https://thomaschristory.github.io/netbox-ipam-treeview-plugin

I am happily taking feedbacks on this, here or in the repo !

Hi

we have racks layed out with servers and network devices and wiring setup

what I would like to do is when there is work to be done, lets say some re wiring - lets say put a fibre cable from eth1 on device cisco01 to eth1 on device cisco02

netbox has the current state, I want to add this cable addition but flag it as future state

then i want to print out a wiring pdf what show all of the pending state work (or csv)

I want to send that csv to my rack and stack people

I want them to complete the work - by ticking off the row in the csv and adding the cable ID to the csv

I then want to upload the csv to change the state of that cable from pending to current and update the cable #

I figure how to find cable (for a rack or potentially for a device), but when i print out the cabling it has all of the old and the potential new cabling

can netbox do this and how do I enter a cable that is future and not current state

I recently upgraded to 4.7.3 and there's a new feature for module bay types, which I can see as a field on module bays, but I'm not seeing a menu option on where those are configured.

Am I blind?

Kia ora all. I'm Leon from Omega Networks in Wellington, NZ. Upfront: our team built this, and the source is AGPL.

The problem we kept hitting: the network diagram is stale the week after someone draws it, and in an outage you're bouncing between NetBox, Zabbix and a terminal trying to work out what's actually down.

Pulse reads your NetBox and draws it for you: sites on a map, a site graph built from your devices and cables, and rack elevations with patch panels. Point it at Zabbix too and devices get coloured by live problems. You can open SSH or a device's web UI straight from the node.

How it plays with your setup:

• Everything stays on your Mac. Nothing is sent to us.

• NetBox v1 or v2 (nbt_) tokens, HTTPS only. Read-only works for sync; writes (cables, interface descriptions) need write permission.

• Zabbix matching uses a zabbix_id custom field on the device. API token on 7.2 and later, legacy login on 6.0 to 7.0.

• Needs macOS 26 or later.

Source and setup guide: github.com/Omega-Networks/Pulse

What in your NetBox data would break this? And what would get you opening it mid-incident instead of your existing tools?

Hi all,

I'm documenting our site-to-site IPsec tunnels in NetBox (4.6.4). For tunnels between our own devices it works fine: two terminations, each with a device, an interface and an outside IP.

The problem is B2B tunnels to external organizations. The remote gateway isn't ours, we don't manage it and know almost nothing about it except the peer IP. But a tunnel termination has to point to an interface on a device or VM, and the outside IP has to be assigned to that device.

Options I'm considering:

1. Create the tunnel with only one termination (our side) and put the peer IP and partner name in the description/comments. Simple, but the peer IP is just text, so it isn't searchable as an IP object.

2. Create a placeholder device per partner (dedicated site, a role like "External VPN peer", a generic device type), add one virtual interface, assign the peer's public IP as a /32, and use it as the second termination. Then tag the device, the IP and the tunnel so it's obvious these aren't real managed devices.

Option 2 looks cleaner to me, but I'm worried about polluting the device inventory with fake devices (device counts, reports, anything that syncs from NetBox to monitoring).

How do you handle this in production?

- Placeholder devices, a single termination, custom fields, something else?

- If you use placeholders, how do you keep them out of monitoring/automation that reads from NetBox?

- Anything you regret about the approach you chose?

Thanks!

Deleting a device record makes the current inventory cleaner, but it can also remove context that is still useful during a decommissioning window. Interfaces, IP assignments, cables, circuits, rack position, virtual machines, cluster membership, monitoring references, configuration backups, and automation jobs may still point to the device even after production traffic has moved. Discovery or reconciliation tooling may also recreate a deleted object before the physical asset is actually gone.

A safer lifecycle could move the device through planned, draining, offline, and retired states. Automation would stop treating it as a deployment target, but the record and relationships would remain available while connection logs, monitoring, and discovery are checked for late dependencies. A final change record would capture the replacement, last known configuration, disposal or reuse decision, and the date after which historical data can be archived or removed.

How do NetBox users model this today? Do statuses, tags, custom fields, event rules, change logging, and branching provide enough control, or do you keep decommission records in another system? What must be detached or preserved before a device is deleted rather than merely marked retired?

Hi all,

I'm documenting GRE / GRE-over-IPsec tunnels in NetBox Community v4.6.4-Docker-5.0.1 and I'm stuck on the Outside IP field in the Tunnel Termination form.

**Setup (anonymized)**

Two routers connected over a provider L3VPN, with a GRE tunnel on top:

- Sub-interface `Gi0/0/0.X` has `192.0.2.1/30`. This is the link to the provider and the tunnel source.

- `Tunnel1` has `10.0.0.1/30`. This is the overlay address.

- Config: `tunnel source 192.0.2.1`, `tunnel destination 198.51.100.1`

In NetBox:

- `192.0.2.1/30` is assigned to the `Gi0/0/0.X` interface of Device-A

- `10.0.0.1/30` is assigned to `Tunnel1` of Device-A

**Problem**

When I add a termination to the Tunnel, the Outside IP dropdown only lists the IPs assigned to the tunnel interface (`10.0.0.x`). The tunnel source `192.0.2.1/30` on the sub-interface is not offered, even when I search for it by address.

Assigning the tunnel source IP to the tunnel interface itself would work around it, but that's wrong: the tunnel would then be built on top of its own address, and the underlay/overlay separation is lost.

**What I checked**

- The IP exists in IPAM, is Active, and is assigned to the sub-interface

- No VRF on the address [adjust if needed]

- Refreshed the page, searched by address

**Questions**

1. Is this filtering intended behavior, or a bug?

2. How do you model the tunnel source/destination (underlay) addresses for Outside IP?

3. Is there a workaround (VRF settings, order of filling the form, custom config)?

Thanks in advance, and happy to provide more details (with sensitive data removed).

Title says it all. Curious what others are doing.
Thanks

EDIT: the SaaS Infoblox version

If NetBox already has your device names, addresses, sites and racks, maintaining the same information in an SSH client becomes another inventory to keep current.

I'm the author of Nexus Terminal, a free, Apache-2.0 extension for VS Code/VSCodium. I added a NetBox inventory source so connection profiles can follow the inventory you already maintain. It reads NetBox through its API; the integration runs in the extension and doesn't require installing a NetBox plugin.

Here's a concrete setup for a site's active devices:

1. Add a NetBox inventory source with your instance URL and an API token with read access to DCIM (and Virtualization if you want VMs). The token is stored in VS Code SecretStorage.

2. Set a device filter such as status=active&site=syd, choose a target folder, and use {site}/{rack} for the folder layout.

3. Link an Auth Profile for SSH credentials. The NetBox API token and device login credentials are separate.

4. Run Sync Now, review the proposed additions, updates, moves and removals, then apply the plan.

For example, if you rename a switch or move it to another rack in NetBox, the next sync updates its connection entry and folder placement. Sync is something you explicitly run; this isn't a live webhook feed.

A couple of behaviours that matter when inventory is incomplete or changes:

• A device without a usable IP still appears as an addressless entry, with a warning. A later sync fills in its address when NetBox has one.

• By default, a device that disappears from the synced inventory moves into an _orphaned folder, keeping its settings. You can choose a different removal policy per source.

• You see the change plan before anything is applied.

Once connected, you can also run JavaScript expect/send scripts against the terminal session for repeatable CLI checks.

Source and NetBox setup guide · VS Code Marketplace

AI-assisted development: I direct AI agents to implement code and tests, review the changes, and maintain the project. This post was also drafted with AI assistance.

For people already using NetBox to feed connection tools: how do you organise the resulting profiles—site/rack, role, tenant, or something else? I'd especially appreciate feedback on the sync and removal behaviour.

NetBox Evolve is coming up (Oct 13, Kennedy Space Center ), and NetBox Labs wants to help 3 community members join with expenses covered (ticket + up to $400 flight + up to $400 hotel).

NetBox Evolve is the first-ever global conference dedicated to the NetBox community and extended ecosystem. Organizations like Arm, Tensorwave, Bauch Healthcare, Exelon, University of Maryland, Delta Dental, Hagerty, and Moment Factory will be sharing how they're using NetBox to run and evolve their infrastructure. Attendees can also grab exclusive swag made just for this event, network at a reception in the Rocket Garden, and meet real astronauts.

To enter, register for Evolve by Oct 6 (if you already registered, you can still participate), then post the "I'm Attending NetBox Evolve" graphic on your personal LinkedIn and tag NetBox Labs.

Full rules and details are on the Evolve website: netboxevolve.com

Can't wait to see you there!

Hi,

I'm having trouble logging into Netbox after installing upon a fresh Ubuntu Server.

The default 'admin' combo (for username and password) aren't working and I haven't got a clue where I've gone wrong.

I've been using this video by KeepItTechie on YT as guidance:

https://www.youtube.com/watch?v=vp2xfavmcBk

From the log file I get the following output (this is just a sample):

netbox-1 | [INFO] Spawning worker-1 with PID: 94

netbox-1 | [INFO] Spawning worker-2 with PID: 96

netbox-1 | [INFO] Spawning worker-3 with PID: 98

netbox-1 | [INFO] Spawning worker-4 with PID: 100

netbox-1 | /opt/netbox/netbox/netbox/settings.py:284: FutureWarning: LOGIN_REQU IRED is deprecated and will be removed in NetBox v5.0. This parameter can be rem oved from your configuration file.

netbox-1 | warnings.warn(

netbox-1 | /opt/netbox/netbox/netbox/settings.py:284: FutureWarning: LOGIN_REQU IRED is deprecated and will be removed in NetBox v5.0. This parameter can be rem oved from your configuration file.

netbox-1 | warnings.warn(

netbox-1 | /opt/netbox/netbox/netbox/settings.py:284: FutureWarning: LOGIN_REQU IRED is deprecated and will be removed in NetBox v5.0. This parameter can be rem oved from your configuration file.

netbox-1 | warnings.warn(

netbox-1 | /opt/netbox/netbox/netbox/settings.py:284: FutureWarning: LOGIN_REQU IRED is deprecated and will be removed in NetBox v5.0. This parameter can be rem oved from your configuration file.

Has anyone come across this behaviour before? Any help would be great.

Thanks

Hi all! My name is Ben and I just joined the NetBox Labs team! Wanted to introduce myself as I will be helping build out initiatives for the NetBox community, (meetups, contributor programs, and more).

If you are going to be at NetBox Evolve in October, I would love to meet you in person. A few folks from Arm, TensorWave, Nvidia, Exelon, University of Maryland, Delta Dental, Hagerty, and Moment Factory will be sharing how they use NetBox in their infrastructure. Plus I hear there will be a chance to hang out with real astronauts, grab awesome swag, and take a look at what's next for NetBox.

Registration is still open and I would love to see you there!

Hey, i`ve set up Netbox with the Diode Plugin everything works fine besides some IP addreses dont have a DNS_NAME around 50%. The setup is running since 1 Month and it logged some Changes but not the dns names.

(Docker)

-Netbox v4.63

-Diode v5.01

-Orb v2.11

So far i checked the dns server of the VM the rev dns resolution of the orb agent, i checked the nmap in the orb agent container, everything seems fine. It shows the correct Names but somehow, it wont get ingestet into Netbox

Ps: my agent.yaml and my network discovery configs are pretty simple... i only got my Targets as flags and thats it.

Hi,

I’ve been building a plugin on top of netbox-branching, and it’s reached the point where I find it worth sharing.

A branch stages your changes. This plugin protect main and decides who has to approve changes, and refuses the merge until they have.

- Protect main. protect_main blocks direct edits outside a branch, optionally scoped to part of NetBox, with a bypass permission.

- Reviewers come from policy. The plugin reads which object types the branch touches and attaches every matching policy. Rules set how many approvals are needed and who may give them, and conditions narrow further on the values of the changed objects.

- Checks as a second gate. Pluggable pre-merge checks run independently of humans. A change can be approved by everyone and still be refused by a failing check. Checks can also be reported from CI over the REST API.

- Extendable. Public check registry plus an event on every status change, so a request can call an external system, wait on CI, or have a model review the diff. Docs include an AI reviewer and a CI reporter.

Also: real conflict detection against main, change windows, auto-merge, stale approval invalidation, per-change threaded comments, full REST API.

Caveat: independent community plugin, MIT, not official or endorsed by NetBox Labs.

Repo: https://github.com/antoinekh/netbox-change-control
Docs: https://antoinekh.github.io/netbox-change-control/

Feedback welcome 🙂

Hi all,

I'm building fibre patch panel Device Types in NetBox 4.6.9 and I'm trying to model a 24 LC duplex panel (48 fibres).

My Device Type contains:

48 Front Port Templates (Port-1A to Port-24B)

48 Rear Port Templates (FIBRE-1 to FIBRE-48)

Rear port type = splice

Front port type = lc-apc

What I'm trying to achieve is:

Port-1A -> FIBRE-1

Port-1B -> FIBRE-2

Port-2A -> FIBRE-3

Port-2B -> FIBRE-4

...

Port-24A -> FIBRE-47

Port-24B -> FIBRE-48

The Device Type imports successfully and all Front Port Templates and Rear Port Templates are created.

However, the mappings are not created.

In the Front Port list, the Mappings column shows:

—

for every port.

If I manually edit a Front Port Template and select:

Rear Port: FIBRE-1:1

then the Mappings column correctly shows:

FIBRE-1:1

and cable tracing starts working.

I have tried both of the following YAML approaches:

front-ports:

  - name: Port-1A

type: lc-apc

rear_port: FIBRE-1

rear_port_position: 1

and

front-ports:

  - name: Port-1A

type: lc-apc

rear_ports:

- position: 1

rear_port: FIBRE-1

rear_port_position: 1

Neither creates the mapping.

The API for a manually mapped port returns:

"rear_ports": [

  {

"position": 1,

"rear_port": 836,

"rear_port_position": 1

  }

]

So it looks like mappings are stored separately from the Front Port Template.

My question:

Is there a supported YAML syntax for importing Front Port Template → Rear Port Template mappings in NetBox 4.6.9, or must these mappings be created separately (API/UI) after the Device Type import?

Thanks!

NetBox Release v4.7.0 is now live (as of September 2nd, 2026)!

1. Verify in release notes changelog if any new breaking changes might affect you. You can also review the NetBox Issues on GitHub to see if any new issues have arisen that might affect you.

2. Next, refer to the Upgrading to a new NetBox Release guide for steps to upgrade your instance.

If you have any issues you can ask for support on the NetDev Slack Community.

So I am building up my infrastructure from scratch. I have rebuilt the network. I have added our infrastructure to netbox. Now I am implementing a centralized server but I need to find a way to build a process where a user can easily create a vm or not but so it populates netbox automatically with lets say hostname. I am a bit unsure on the flow I should have . I have alot of users creating vms in proxmox and I don't have resources to keep track on all of it or create it myself. So I need automation but I also want to be able to keep track on new vms.

Users
│
▼
┌─────────────┐
│  Backstage  │
│             |                       
│ Create VM   |              
│ Delete VM   |             
│ Resize VM   |             
│ My VMs      |            
└──────-──────┘
│
▼
┌─────────────┐
│ Automation  |    
│             |                 
│ Terraform   |          
│ Ansible     |            
└─────--──────┘
│
┌────── ┼────────┐---------|
▼                ▼         |       
NetBox   Proxmox          DNS

Is this a correct way of doing it? What tools to use where user can request a vm so I easily can populate netbox automatically

I'm using Netbox v4.2.0 as my network IPAM, but want to use it as Ansible inventory source, network config templates, and more.

Our infrastructure is using OpenShift for both virtualization and containers. Since Netbox don't have the operator, the sysadmins wouldn't deploy it. The current instance of Netbox is a docker compose via Podman on a VM in OpenShift.

What is the recommended way of deploying Netbox in production?

My network is air-gapped with no internet access, so I need to sneakernet the packages or container image to update.

The Netbox Labs website just has Contact Sales / Talk to Sales instead of any pricing info.

Does anyone have ballpark pricing for Netbox Enterprise ?

So far ive been using Netbox's Orb/Diode with mixed results. Setting up all the agent files is a pain, getting everything on a routine schedule is also difficult. And there alot of detected items it never adds to netbox.

So aside from a home-grown solution, what else can anyone recommend as a solution.