Project

General

Profile

Actions

Bug #11006

closed

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

Added by Evgeny Korostelev 12 months ago. Updated 11 months ago.

Status:
Resolved
Priority:
Very Low
Assignee:
Category:
L2TP
Target version:
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

Actions #1

Updated by Evgeny Korostelev 12 months 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 #2

Updated by Jim Pingle 12 months 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 #3

Updated by Viktor Gurov 12 months 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 #4

Updated by Renato Botelho 12 months ago

  • Status changed from New to Feedback
  • Assignee set to Viktor Gurov
  • Target version set to 2.5.0

PR has been merged. Thanks!

Actions #5

Updated by Viktor Gurov 12 months ago

  • % Done changed from 0 to 100
Actions #6

Updated by Evgeny Korostelev 11 months ago

Works fine !
Thanks a lot !!!
Best of the best !!!

Actions #7

Updated by Renato Botelho 11 months ago

  • Status changed from Feedback to Resolved
Actions

Also available in: Atom PDF