Project

General

Profile

Actions

Bug #10531

closed

L2TP client not able to use shared secret

Added by Viktor Gurov about 2 years ago. Updated about 2 years ago.

Status:
Resolved
Priority:
Normal
Category:
L2TP
Target version:
Start date:
05/06/2020
Due date:
% Done:

0%

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

Description

It is not possible to use Shared Secret by L2TP client,
no such field in WebGUI

http://mpd.sourceforge.net/doc5/mpd48.html#48:

set l2tp secret secret
 Sets the L2TP tunnel secret. Used to authenticate tunnel connection and encrypt important control packets avpairs. For server side, 
 only one unique secret supported for every pair of listening IP (set l2tp self ...) and peer ip (set l2tp peer ...). If several 
 secrets defined, only the first matching will be used for all incoming connections.

 NOTE: This options is not related with usual PPP authentication. Windows client does not support tunnel authentication.

see also #10527

Actions #2

Updated by Jim Pingle about 2 years ago

  • Status changed from New to Pull Request Review
Actions #3

Updated by Renato Botelho about 2 years ago

  • Status changed from Pull Request Review to Feedback
  • Assignee set to Renato Botelho
  • Target version set to 2.4.5-p1

PR has been merged. Thanks!

Actions #5

Updated by Jim Pingle about 2 years ago

  • Status changed from Feedback to Pull Request Review
Actions #6

Updated by Jim Pingle about 2 years ago

  • Status changed from Pull Request Review to Feedback

PR merged

Actions #7

Updated by Jim Pingle about 2 years ago

  • Status changed from Feedback to Resolved

Shared secret is now correctly populated in the client configuration and the client can connect to a server with a matching shared secret.

Actions

Also available in: Atom PDF