Connection required IP address #1192

Closed
opened 2025-12-29 16:29:56 +01:00 by adam · 1 comment
Owner

Originally created by @bitratio on GitHub (Aug 24, 2017).

Currently, the connections between devices require an IP address.

We have interfaces that are either part of MLAGS or LAGS or are just plain layer2 links between switching and routers and thus do not have address space assigned.

Can we have a feature where we can make a device interface part of a LAG or LACP or just select that it's a layer2 trunk or access port with no address space assigned?

Cheers

Will

Originally created by @bitratio on GitHub (Aug 24, 2017). Currently, the connections between devices require an IP address. We have interfaces that are either part of MLAGS or LAGS or are just plain layer2 links between switching and routers and thus do not have address space assigned. Can we have a feature where we can make a device interface part of a LAG or LACP or just select that it's a layer2 trunk or access port with no address space assigned? Cheers Will
adam closed this issue 2025-12-29 16:29:56 +01:00
Author
Owner

@jeremystretch commented on GitHub (Aug 24, 2017):

Currently, the connections between devices require an IP address.

You can connect interfaces regardless of whether they have an IP address assigned. The button with a plus sign adds an IP address; the button with two arrows facing each other connects interfaces.

@jeremystretch commented on GitHub (Aug 24, 2017): > Currently, the connections between devices require an IP address. You can connect interfaces regardless of whether they have an IP address assigned. The button with a plus sign adds an IP address; the button with two arrows facing each other connects interfaces.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#1192