starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

NAT Modelization #5525

New Issue
Closed
opened 2025-12-29 19:28:59 +01:00 by adam · 1 comment
adam commented 2025-12-29 19:28:59 +01:00
Owner
Copy Link

Originally created by @thomas-rotszyld on GitHub (Oct 18, 2021).

NetBox version

v2.11.12

Feature type

Change to existing functionality

Proposed functionality

Currently, there is no way to modelize a same Real IP Nated with differents IP Addresses (for several external links).

Change NAT Modelization Feature.
For IPAddress: OnetoOne NAT: Add also onetomany towards Device Models
Add Prefix Range NAT (For modelling pool Range NAT):
Same as IP Address: IP RANGE INSIDE, IP RANGE OUTSIDE, and add onetomany toward device Models.

In IP Address View:
Add a panel showing IPAddress or/and (Prefix Range NAT if the prefix includes the IP)
IP Prefix view:
Add panel showing IP Range NAT

Use case

Currently, NAT modelization in Netbox is done by the usage of foreign key for NAT INSIDE & NAT OUTSIDE IP Address.

Nevertheless, an IP can natted by several different IPS (through different external links).
I will be really interesting to have the possibility to model this use case.. and to identify which device is performing the NAT in the Netbox.

Also, when natting a full range, It will be also useful to model to apply the modelling to prefix and not IP Address.

Database changes

two new models with for IP NAT & PREFIX NAT:
IP NAT INSIDE/ IP PREFIX INSIDE
IP NAT OUSIDE/ IP PREFIX OUTSIDE
NAT DEVICES -> onetomany device model

External dependencies

no new dependencies

Originally created by @thomas-rotszyld on GitHub (Oct 18, 2021). ### NetBox version v2.11.12 ### Feature type Change to existing functionality ### Proposed functionality Currently, there is no way to modelize a same Real IP Nated with differents IP Addresses (for several external links). Change NAT Modelization Feature. For IPAddress: OnetoOne NAT: Add also onetomany towards Device Models Add Prefix Range NAT (For modelling pool Range NAT): Same as IP Address: IP RANGE INSIDE, IP RANGE OUTSIDE, and add onetomany toward device Models. In IP Address View: Add a panel showing IPAddress or/and (Prefix Range NAT if the prefix includes the IP) IP Prefix view: Add panel showing IP Range NAT ### Use case Currently, NAT modelization in Netbox is done by the usage of foreign key for NAT INSIDE & NAT OUTSIDE IP Address. Nevertheless, an IP can natted by several different IPS (through different external links). I will be really interesting to have the possibility to model this use case.. and to identify which device is performing the NAT in the Netbox. Also, when natting a full range, It will be also useful to model to apply the modelling to prefix and not IP Address. ### Database changes two new models with for IP NAT & PREFIX NAT: IP NAT INSIDE/ IP PREFIX INSIDE IP NAT OUSIDE/ IP PREFIX OUTSIDE NAT DEVICES -> onetomany device model ### External dependencies no new dependencies
adam added the type: featurestatus: duplicate labels 2025-12-29 19:28:59 +01:00
adam closed this issue 2025-12-29 19:28:59 +01:00
adam commented 2025-12-29 19:29:00 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 18, 2021):

Thank you for submitting this issue, however it appears that this topic has already been raised. Please see issue #1202 for further discussion.

@jeremystretch commented on GitHub (Oct 18, 2021): Thank you for submitting this issue, however it appears that this topic has already been raised. Please see issue #1202 for further discussion.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label status: duplicate type: feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#5525
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?