Project

General

Profile

Actions
Copy link

Bug #6729

closed

L2TP+IPSEC 2.3.2-RELEASE

Added by Andrey Kartashov almost 9 years ago. Updated almost 9 years ago.

Status:
Not a Bug
Priority:
Normal
Assignee:
-
Category:
L2TP
Target version:
-
Start date:
08/18/2016
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.3.2
Affected Architecture:

Description

I was stuck for two days making this work. Connection was successful but something wrong was with Filtering. Finally!
In L2TP settings when number of users added it creates devices l2tp{i}, so the first one gets l2tp0 ... l2tp0 but Filtering uses alias L2TP { l2tp }. So I manually replaced alias in /etc/inc/filter.inc to L2TP { l2tp0 } and the first user works well. I believe to fix the issue alias should be L2TP { l2tp0, all the devices, l2tpn }

Actions
Copy link
 #1

Updated by Jim Pingle almost 9 years ago

  • Category set to L2TP
  • Status changed from New to Not a Bug

The rules are correct, but if changing that fixed it for you, that implies the individual L2TP interfaces are not being added to the "l2tp" group.

The group add action is handled in /usr/local/sbin/vpn-linkup and it works when I try it. The moment I connect a client, it shows up in the group and its traffic is passed by the rules on the L2TP tab.

Please post on the forum for assistance in tracking down the root cause of your issue, and open a new ticket if one is found.

Actions
Copy link

Also available in: Atom PDF