Project

General

Profile

Bug #2004

Client Specific Override ->Tunnel Network

Added by W FM almost 8 years ago. Updated over 7 years ago.

Status:
Resolved
Priority:
Low
Assignee:
-
Category:
OpenVPN
Target version:
-
Start date:
11/09/2011
Due date:
% Done:

0%

Estimated time:
Affected Version:
2.0
Affected Architecture:

Description

Tunnel Network description says:
This is the virtual network used for private communications between this client and the server expressed using CIDR (eg. 10.0.8.0/24). The first network address is assumed to be the server address and the second network address will be assigned to the client virtual interface.

Apologies if I am reading the above incorrectly however looks like the first address is actually assigned to the ovpn client (not the server/pfsense).

For example
Tunnel network = 10.10.10.9/30
assigns 10.10.10.9 to the client

client log:
add dev tun0 local 10.10.10.9 peer 10.10.10.10

Associated revisions

Revision 298fe5ae (diff)
Added by Jim Pingle almost 8 years ago

Fix order of client/server IPs and add a note, and clarify variable names. Fixes #2004.

Revision 035c5573 (diff)
Added by Jim Pingle almost 8 years ago

Fix order of client/server IPs and add a note, and clarify variable names. Fixes #2004.

History

#2 Updated by W FM almost 8 years ago

.8 shows same result

Tunnel network = 10.10.10.8/30
assigns 10.10.10.9 to the client

client log:
openvpn2664: /sbin/ip addr add dev tun0 local 10.10.10.9 peer 10.10.10.10

#3 Updated by Jim Pingle almost 8 years ago

Ah, yeah you're right, the parameters to ifconfig-push in the csc file are backwards. It should be the other way to conform with the openvpn standard. I'll commit a fix shortly.

#4 Updated by Jim Pingle almost 8 years ago

  • Status changed from Rejected to Feedback

#5 Updated by Chris Buechler over 7 years ago

  • Status changed from Feedback to Resolved

Also available in: Atom PDF