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

Endpoint wrong if bridged device in cable path #7226

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

Originally created by @lagrip on GitHub (Nov 14, 2022).

NetBox version

v.3.3.7

Python version

3.10

Steps to Reproduce

  1. Create the following devices: Switch, Patchpanel with Front- and Rear-Ports, PoE Injector, Access Point
  2. Set both Ports of PoE Injector in bridged mode
  3. Connect the devices as show below
[ switch]                [ Patchpanel ]                       [ PoE Inj ]                  [ AP]
 [ iface ] ------- [ front]         [ rear] ----------- [ iface ]  [ iface ] ------- [ iface ]
            cable1                            cable2       |             |    cable3
                                                            +-- bridge --+

Expected Behavior

On the interface tab of the switch the interface should show the endpoint on the 'connection' row. In this case the access point.

Observed Behavior

On the 'connection' row it shows the next component. In this case the PoE Injector. This is OK for the "Link Peers" but not for the endpoint.
By the way: The cable trace works fine. It shows all components and cable from the switch to the AP. Thus, the information is available, but on the interface tab it shows a wrong device.

Originally created by @lagrip on GitHub (Nov 14, 2022). ### NetBox version v.3.3.7 ### Python version 3.10 ### Steps to Reproduce 1. Create the following devices: Switch, Patchpanel with Front- and Rear-Ports, PoE Injector, Access Point 2. Set both Ports of PoE Injector in bridged mode 3. Connect the devices as show below ``` [ switch] [ Patchpanel ] [ PoE Inj ] [ AP] [ iface ] ------- [ front] [ rear] ----------- [ iface ] [ iface ] ------- [ iface ] cable1 cable2 | | cable3 +-- bridge --+ ``` ### Expected Behavior On the interface tab of the switch the interface should show the endpoint on the 'connection' row. In this case the access point. ### Observed Behavior On the 'connection' row it shows the next component. In this case the PoE Injector. This is OK for the "Link Peers" but not for the endpoint. By the way: The cable trace works fine. It shows all components and cable from the switch to the AP. Thus, the information is available, but on the interface tab it shows a wrong device.
adam closed this issue 2025-12-29 20:20:39 +01:00
adam commented 2025-12-29 20:20:39 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 16, 2022):

This is working as intended. An interface always represents the end of a cable path. When tracing a cable, NetBox will follow a bridged relationship from the end of one cable path to the beginning of another cable path for convenience, but these are still two separate paths. An interface will only ever show the far end of its directly connected cable path for various reasons, mostly relating to performance and validation.

(If you want to show the end-to-end path, I'd suggest changing the PoE injector terminations to front & rear ports.)

@jeremystretch commented on GitHub (Nov 16, 2022): This is working as intended. An interface always represents the end of a cable path. When tracing a cable, NetBox will follow a bridged relationship from the end of one cable path to the beginning of _another_ cable path for convenience, but these are still two separate paths. An interface will only ever show the far end of its directly connected cable path for various reasons, mostly relating to performance and validation. (If you want to show the end-to-end path, I'd suggest changing the PoE injector terminations to front & rear ports.)
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
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#7226
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?