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

NAT: add support for prefix translation (1:1 nat) #4633

New Issue
Closed
opened 2025-12-29 19:18:55 +01:00 by adam · 2 comments
adam commented 2025-12-29 19:18:55 +01:00
Owner
Copy Link

Originally created by @c-po on GitHub (Mar 8, 2021).

Environment

  • Python version: 3.9.1
  • NetBox version: v2.10.3

Proposed Functionality

The current state of Netbox supports configuration of 1:1 NAT for individual IP addresses. This is expressed in the UI as:
image

There is yet no support for 1:1 NAT based on the entire IP prefix.

Use Case

Connect customer equipment to your network but the customer requires a strict address plan which overlaps with the local IP networks. One can simply configure a 1:1 prefix NAT to make the entire IPv4 /22 network available, but this would require to maintain all 1024 IP addresses and their corresponding translations. By adding support for 1:1 NAT this is eliminated.

Database Changes

External Dependencies

Originally created by @c-po on GitHub (Mar 8, 2021). <!-- NOTE: IF YOUR ISSUE DOES NOT FOLLOW THIS TEMPLATE, IT WILL BE CLOSED. This form is only for proposing specific new features or enhancements. If you have a general idea or question, please start a discussion instead: https://github.com/netbox-community/netbox/discussions NOTE: Due to an excessive backlog of feature requests, we are not currently accepting any proposals which significantly extend NetBox's feature scope. Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * Python version: 3.9.1 * NetBox version: v2.10.3 <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality The current state of Netbox supports configuration of 1:1 NAT for individual IP addresses. This is expressed in the UI as: ![image](https://user-images.githubusercontent.com/25299219/110358202-6d97f380-803c-11eb-96cb-6b4cd30bf6a7.png) There is yet no support for 1:1 NAT based on the entire IP prefix. <!-- Convey an example use case for your proposed feature. Write from the perspective of a NetBox user who would benefit from the proposed functionality and describe how. ---> ### Use Case Connect customer equipment to your network but the customer requires a strict address plan which overlaps with the local IP networks. One can simply configure a 1:1 prefix NAT to make the entire IPv4 /22 network available, but this would require to maintain all 1024 IP addresses and their corresponding translations. By adding support for 1:1 NAT this is eliminated. <!-- Note any changes to the database schema necessary to support the new feature. For example, does the proposal require adding a new model or field? (Not all new features require database changes.) ---> ### Database Changes <!-- List any new dependencies on external libraries or services that this new feature would introduce. For example, does the proposal require the installation of a new Python package? (Not all new features introduce new dependencies.) --> ### External Dependencies
adam added the type: featurepending closurestatus: under review labels 2025-12-29 19:18:55 +01:00
adam closed this issue 2025-12-29 19:18:55 +01:00
adam commented 2025-12-29 19:18:55 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jun 13, 2021):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Jun 13, 2021): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 19:18:55 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jul 13, 2021):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Jul 13, 2021): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
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 pending closure status: under review 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#4633
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?