#22462·netbox

Native L2VPN Pseudowire (PW) Termination to an IP Address

Author: bctiemannCreated Jun 16, 2026Updated Sep 17, 2026
Labelstype: featurestatus: under reviewpending closurenetbox

NetBox version

v4.6.2

Feature type

New functionality

Proposed functionality

Add support for terminating an L2VPN directly to an IP address (with an associated ID), as a first-class L2VPN termination type — alongside the existing circuit/interface terminations.

Use case

Background / Current behavior

NetBox currently supports two L2VPN termination types:

L2VPN circuit/interface termination to a physical/L2 interface (e.g. lag-200:3252)

L2VPN router-interface termination to an L3 interface (e.g. LAG200.3252)

Both display correctly under L2VPN terminations and in the interface overview. However, there is no native way to model an L2VPN pseudowire (PW) termination that points at an IP address (the far-end/L3 exit of an L2 environment).

Problem

To capture the pseudowire far-end IP today, the customer must use a custom field (e.g. cf_pw_far_end_ip) piggybacked onto an existing termination. This workaround:

Hides the PW from the L2VPN terminations view entirely — the PW is not represented as its own termination.

Forces the IP/ID to be randomly attached to an unrelated termination, which is confusing and unmaintainable.

Requested behavior

Can we allow an L2VPN to terminate to an IP address + ID, so the IP appears in the termination Object field just like the existing two termination types.

Database changes

Unknown

External dependencies

No response