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

Assigning IP addresses to interfaces connected by a cable only shows on one of the endpoints #4940

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

Originally created by @baguilartech on GitHub (May 22, 2021).

NetBox version

v2.11.3

Python version

3.6

Steps to Reproduce

  1. Create two devices each with their set of interfaces
  2. Connect a cable between Device A:Interface A and Device B:Interface B
  3. Assign an IP address to Device A:Interface A
  4. Navigate to the interfaces tab of Device B and find Interface B connected to Device A:Interface A. IP address will not be assigned under Device B's interface page

Further observations: Happens also when IPs are assigned to interfaces using IP import.

Expected Behavior

It would make sense that if a cable connects two endpoints together and if there is an address assigned to an interface on either side, then for troubleshooting and route tracing, the IP of the configured interface should be logically visible on both endpoints' interface listing.

Observed Behavior

Here is a device that has been connected to multiple switches on different interfaces and had IPs assigned to it on it's page:
Screen Shot 2021-05-21 at 3 39 04 PM

Here is the one of the switches on the interface connected to that device:
Screen Shot 2021-05-21 at 3 41 45 PM

And another separate switch exhibiting same behavior:
Screen Shot 2021-05-21 at 3 42 13 PM

Originally created by @baguilartech on GitHub (May 22, 2021). ### NetBox version v2.11.3 ### Python version 3.6 ### Steps to Reproduce 1. Create two devices each with their set of interfaces 2. Connect a cable between Device A:Interface A and Device B:Interface B 3. Assign an IP address to Device A:Interface A 4. Navigate to the interfaces tab of Device B and find Interface B connected to Device A:Interface A. IP address will not be assigned under Device B's interface page Further observations: Happens also when IPs are assigned to interfaces using IP import. ### Expected Behavior It would make sense that if a cable connects two endpoints together and if there is an address assigned to an interface on either side, then for troubleshooting and route tracing, the IP of the configured interface should be logically visible on both endpoints' interface listing. ### Observed Behavior Here is a device that has been connected to multiple switches on different interfaces and had IPs assigned to it on it's page: ![Screen Shot 2021-05-21 at 3 39 04 PM](https://user-images.githubusercontent.com/5866029/119205230-90875080-ba4c-11eb-943c-a7c3088a0389.png) Here is the one of the switches on the interface connected to that device: ![Screen Shot 2021-05-21 at 3 41 45 PM](https://user-images.githubusercontent.com/5866029/119205270-aa289800-ba4c-11eb-8f0e-f1b3fabec934.png) And another separate switch exhibiting same behavior: ![Screen Shot 2021-05-21 at 3 42 13 PM](https://user-images.githubusercontent.com/5866029/119205285-b6acf080-ba4c-11eb-9c00-fe140527bca3.png)
adam added the type: bug label 2025-12-29 19:22:28 +01:00
adam closed this issue 2025-12-29 19:22:28 +01:00
adam commented 2025-12-29 19:22:28 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 25, 2021):

This is intended behavior. Assigning an IP address to an interface in NetBox implies that the IP address is configured on that interface. Each interface would have its own IP address.

@jeremystretch commented on GitHub (May 25, 2021): This is intended behavior. Assigning an IP address to an interface in NetBox implies that the IP address is configured on that interface. Each interface would have its own IP address.
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 type: bug
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#4940
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?