Bug #11006: L2TP Server and Client both use "l2tpX" for interface names - pfSense - pfSense bugtracker

Custom queries

2.4.5-p1 - Resolved/Closed
2.5.0 - Resolved/Closed
2.5.1 - Resolved/Closed
2.5.2 - Resolved/Closed
2.6.0 - Resolved/Closed
2.7.0 - Resolved/Closed
2.7.1 - All Open Issues
2.7.1 - Resolved/Closed
2.7.2 - Resolved/Closed
2.8.0 - All Open Bugs
2.8.0 - All Open Features
2.8.0 - All Open Issues
2.8.0 - All Open Regressions
2.8.0 - Feedback
2.8.0 - Needs Attention
2.8.0 - New/Confirmed
2.8.0 - Pull Requests
2.8.0 - Regressions affecting 2.7.0
2.8.0 - Resolved/Closed
21.02.2/2.5.1 - Resolved/Closed
21.05 Plus - All Closed Issues
21.05.1 Plus Target - All Closed Issues
21.05.1 Target - All Closed Issues
22.01 Plus - All Closed Issues
22.01 Target - All Closed Issues
22.05 Plus - All Closed Issues
22.05 Target - All Closed Issues
23.01 Plus - All Closed Issues
23.01 Target - All Closed Issues
23.05 Plus - All Closed Issues
23.05 Target - All Closed Issues
23.05.1 Plus - All Closed Issues
23.05.1 Target - All Closed Issues
23.09 Plus - All Closed Issues
23.09 Target - All Closed Issues
23.09.1 Plus - All Closed Issues
23.09.1 Plus - All Open Issues
23.09.1 Target - All Closed Issues
23.09.1 Target - All Open Issues
24.03 Plus - All Closed Issues
24.03 Plus - All Open Issues
24.03 Plus - Feedback Issues
24.03 Plus - Needs Attention/Work
24.03 Plus - New/Confirmed/In Progress Issues
24.03 Plus - Pull Request Review
24.03 Plus - Waiting on Merge
24.03 Target - All Closed Issues
24.03 Target - All Open Issues
All Open Issues assigned to Me
All Open Pull Requests
Any Target - All Open Regressions
Any Target - Feedback Issues
CE-Next - All Closed Issues (Move to specific target)
CE-Next - All Open Issues
CE-Next - Feedback (Likely needs target changed)
New Issues by Category - Future Target
New Issues by Category - No Target
New Issues by Category - No Target+Future
No Target - All Open Issues (Base Only)
No Target - New Issues (Base Only)
No Target - New Issues (Base and Packages)
Release Notes - Plus Target Version (DO NOT EDIT)
Release Notes - Target Version (DO NOT EDIT)

Actions

Copy link

Bug #11006

closed

L2TP Server and Client both use "l2tpX" for interface names

Added by Evgeny Korostelev over 3 years ago. Updated over 3 years ago.

Status:

Resolved

Priority:

Very Low

Assignee:

Viktor Gurov

Category:

L2TP

Target version:

2.5.0

Start date:

10/25/2020

Due date:

% Done:

100%

Estimated time:

Plus Target Version:

Release Notes:

Affected Version:

All

Affected Architecture:

Description

Sorry for my english :(
When pfSense have role L2TP server and L2TP client and have some count of every type connection (Server and Client), then happens overlay of name connection, etc l2tp1 can be how incoming or outgoing L2TP connection.

When happens name overlay - then connection stay active, but not working, it can't be rename from ngX to l2tpX

History
Notes
Property changes
Associated revisions

Actions

Copy link

Updated by Evgeny Korostelev over 3 years ago

Every type (server or client) of connection has name l2tpX
on the same digital index, the connection name may coincide, which will lead to the inoperability of this connection

Actions

Copy link

Updated by Jim Pingle over 3 years ago

Subject changed from overlay of names of network connections to L2TP Server and Client both use "l2tpX" for interface names
Category set to L2TP
Priority changed from Normal to Very Low
Affected Version set to All

I see what you mean and have adjusted the subject to match. Both the L2TP Server and L2TP interfaces use "l2tpX" for the interface names.

PPPoE avoids this by using "poesX" for the server interface names and "pppoeX" for clients.

Given the rarity of both the L2TP server and client being in use on the same firewall, this doesn't seem like it would affect many people. L2TP client use is already rare, and few people use the L2TP server as well.

Actions

Copy link

Updated by Viktor Gurov over 3 years ago

Jim Pingle wrote:

I see what you mean and have adjusted the subject to match. Both the L2TP Server and L2TP interfaces use "l2tpX" for the interface names.

PPPoE avoids this by using "poesX" for the server interface names and "pppoeX" for clients.

PPPoE server uses "ngX" for interface names, another issue

Given the rarity of both the L2TP server and client being in use on the same firewall, this doesn't seem like it would affect many people. L2TP client use is already rare, and few people use the L2TP server as well.

Fix:
https://gitlab.netgate.com/pfSense/pfSense/-/merge_requests/37
it also hides l2tp server interfaces from interface list

Actions

Copy link