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

Trace functionality not shown bridge or wireless link #5867

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

Originally created by @Abulhallaj on GitHub (Jan 3, 2022).

NetBox version

v3.1.3

Python version

3.8

Steps to Reproduce

We have some wireless radio devices that connect sites. in every site the LAN interfaces on this devices is connected to Switch and documented, also WLAN interfaces are connected together via wireless link. In every device we create a bridge1 interface and bridged the WLAN and LAN interface into it.

Expected Behavior

------------------
|                |
|      SW01      |
|                |
-----| LAN |------
        |
        | Cable
        |
-----| LAN |------
|                |  \
|WirelessDevice01|   bridge1
|                |  /
-----| WLAN |-----
        |
        | Wireless Link
        |
-----| WLAN |-----
|                |  \
|WirelessDevice02|   bridge1
|                |  /
-----| LAN |------
        |
        | Cable
        |
-----| LAN |------
|                |
|      SW02      |
|                |
------------------

Observed Behavior

The Cable trace just shown the Cable path and not the bridge area or wireless link was shown in trace as excepted. wireless link can traced exclusively but just shown wireless link.

Originally created by @Abulhallaj on GitHub (Jan 3, 2022). ### NetBox version v3.1.3 ### Python version 3.8 ### Steps to Reproduce We have some wireless radio devices that connect sites. in every site the **LAN** interfaces on this devices is connected to Switch and documented, also **WLAN** interfaces are connected together via wireless link. In every device we create a **bridge1** interface and bridged the **WLAN** and **LAN** interface into it. ### Expected Behavior ``` ------------------ | | | SW01 | | | -----| LAN |------ | | Cable | -----| LAN |------ | | \ |WirelessDevice01| bridge1 | | / -----| WLAN |----- | | Wireless Link | -----| WLAN |----- | | \ |WirelessDevice02| bridge1 | | / -----| LAN |------ | | Cable | -----| LAN |------ | | | SW02 | | | ------------------ ``` ### Observed Behavior The Cable trace just shown the Cable path and not the bridge area or wireless link was shown in trace as excepted. wireless link can traced exclusively but just shown wireless link.
adam closed this issue 2025-12-29 19:33:38 +01:00
adam commented 2025-12-29 19:33:38 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 3, 2022):

This is expected behavior. Any number of interfaces can be attached to a bridge group, so the cable trace cannot assume the next hop. If you'd like to enable tracing directly across these, you can bridge the LAN and WLAN interfaces to one another directly.

@jeremystretch commented on GitHub (Jan 3, 2022): This is expected behavior. Any number of interfaces can be attached to a bridge group, so the cable trace cannot assume the next hop. If you'd like to enable tracing directly across these, you can bridge the LAN and WLAN interfaces to one another directly.
adam commented 2025-12-29 19:33:39 +01:00
Author
Owner
Copy Link

@Abulhallaj commented on GitHub (Jan 4, 2022):

@jeremystretch

you can bridge the LAN and WLAN interfaces to one another directly.

I also do that and that's not work
image
image
image

@Abulhallaj commented on GitHub (Jan 4, 2022): @jeremystretch > you can bridge the LAN and WLAN interfaces to one another directly. I also do that and that's not work ![image](https://user-images.githubusercontent.com/20490198/148009624-d7c0de06-deba-4a9f-91c3-5b5f60411635.png) ![image](https://user-images.githubusercontent.com/20490198/148009669-6fd1445c-2a99-497e-8237-4b43a0f6c3d8.png) ![image](https://user-images.githubusercontent.com/20490198/148009733-2bbdcd8b-4b18-4ea2-bbc4-7c6f0fe0b681.png)
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#5867
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?