Project

General

Profile

Bug #4273

OpenVPN options route-nopull and route-noexec swapped

Added by Andreas Winge almost 5 years ago. Updated almost 5 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
OpenVPN
Target version:
Start date:
01/24/2015
Due date:
% Done:

0%

Estimated time:
Affected Version:
2.2
Affected Architecture:

Description

From the pfsense GUI:
Don't pull routes - Don't add or remove routes automatically. Instead pass routes to --route-up script using environmental variables.
If checked route-nopull in put in the configuration file.

Don't add/remove routes - This option effectively bars the server from adding routes to the client's routing table, however note that this option still allows the server to set the TCP/IP properties of the client's TUN/TAP interface.
If checked route-noexec in put in the configuration file.

The manpage for OpenVPN states:

--route-noexec
    Don't add or remove routes automatically. Instead pass routes to --route-up script using environmental variables. 
--route-nopull
    When used with --client or --pull, accept options pushed by server EXCEPT for routes and dhcp options like DNS servers.

    When used on the client, this option effectively bars the server from adding routes to the client's routing table, however note that this option still allows the server to set the TCP/IP properties of the client's TUN/TAP interface. 

Associated revisions

Revision 580f5eee (diff)
Added by Chris Buechler almost 5 years ago

these descriptions were flipped. Ticket #4273

Revision 5e3affe2 (diff)
Added by Chris Buechler almost 5 years ago

these descriptions were flipped. Ticket #4273

History

#1 Updated by Chris Buechler almost 5 years ago

  • Status changed from New to Resolved

Thanks. Yeah the descriptions were backwards, fixed.

Also available in: Atom PDF