Project

General

Profile

Actions
Copy link

Bug #2561

closed

OpenVPN :: Client Specific Override ::

Added by Darwin Mach over 12 years ago. Updated over 12 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
OpenVPN
Target version:
-
Start date:
07/25/2012
Due date:
% Done:

0%

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

Description

Say for example my main OpenVPN server is set up to use 192.168.2.0/24 as the Tunnel Network.

I use the web interface to create a Client Specific Override for a particular user to use 192.168.3.0/24 as the Tunnel Network.

When I connect to the VPN, it picks up an address from the 192.168.3.0/24 subnet, but...

Issue: no traffic routed from 192.168.3.0/24. I can't access anything, and the pfsense routing table doesn't have any entry corresponding to 192.168.3.0/24 (it does have a routing entry for 192.168.2.0/24, however)

Actions
Copy link
 #1

Updated by Chris Buechler over 12 years ago

  • Status changed from New to Rejected

not a legit bug report, that's a support request. Please post to the forum or mailing list.

Actions
Copy link

Also available in: Atom PDF