Project

General

Profile

Actions
Copy link

Bug #3831

closed

VPN PPTP, RADIUS issued IPs and secondary RADIUS server

Added by Vyachelav B about 11 years ago. Updated almost 10 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
PPTP
Target version:
-
Start date:
08/29/2014
Due date:
% Done:

0%

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

Description

I have two AD DC with NAP role installed (RADIUS) and two pfSense gateways (CARP configuration). We use VPN PPTP connection to access internet. I want both gateways to authenticate users on both DC (in case of failover). Also I set static ip-address in dial-in settings for AD internet-user. But when I enable secondary RADIUS server in settings all IPs get from dynamic ip-range which have been setted on VPN PPTP page. If secondary RADIUS disabled - IPs get from AD.

I attached raw pptp logs with only primary RADIUS server and with both primary and secondary RADIUS servers. Dynamic IP-range starting from 10.20.16.10, user have static IP for dial-in 10.20.16.240.

Files

Download all files
only_primary.txt (8.64 KB) only_primary.txt Vyachelav B, 08/29/2014 12:55 AM
primary_and_secondary.txt (8.63 KB) primary_and_secondary.txt Vyachelav B, 08/29/2014 12:55 AM
Actions
Copy link
 #1

Updated by Vyachelav B about 11 years ago

Forgot to mention. Checked this behaviour on 2.1.4-release and 2.2-ALPHA (20 Aug 2014).

Actions
Copy link
 #2

Updated by Vyachelav B almost 11 years ago

Found that problem in MPD (and libradius library). (http://sourceforge.net/p/mpd/discussion/44693/thread/e738def4)

Actions
Copy link
 #3

Updated by Chris Buechler almost 10 years ago

  • Category set to PPTP
  • Status changed from New to Closed

PPTP has been removed in 2.3, won't fix.

Actions
Copy link

Also available in: Atom PDF