Project

General

Profile

Feature #4732

Add MS-CHAPv2 option to L2TP Configuration

Added by Jose Luis Duran over 4 years ago. Updated almost 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
L2TP
Target version:
Start date:
05/26/2015
Due date:
% Done:

100%

Estimated time:

Description

If you need to validate L2TP/IPSec users with a Windows-based RADIUS Server (NPS/IAS), choosing CHAP from VPN:L2TP Configuration, Authentication Type will use MD5 CHAP, and the Windows Server will complaint that a reversibly encrypted password does not exist.

From the MPD documentation page, chap is an alias for chap-md5 chap-msv1 chap-msv2. As a proposed solution, I'm explicitly setting MS-CHAPv2.

Associated revisions

Revision 92c57679
Added by Matthew Smith about 4 years ago

Merge pull request #1689 from jlduran/l2tp-mschapv2

History

#1 Updated by Jose Luis Duran over 4 years ago

I have opened a Pull Request (#1689) to discuss this subject.

#2 Updated by Chris Buechler over 4 years ago

  • Target version changed from 2.2.3 to 2.3
  • Affected Architecture deleted (All)

thanks, we'll review for 2.3.

#3 Updated by Jim Thompson about 4 years ago

  • Assignee set to Matthew Smith

#4 Updated by Matthew Smith about 4 years ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100

I reviewed the code and tested it's effect on the config file generation and it looks ok. It has been merged.

#5 Updated by Matthew Smith about 4 years ago

  • Status changed from Resolved to Feedback

#6 Updated by Chris Buechler almost 4 years ago

  • Status changed from Feedback to Resolved

works

Also available in: Atom PDF