Correction #11019
closedFeedback on pfSense Configuration Recipes — Configuring a Single Multi-Purpose OpenVPN Instance
0%
Description
Page: https://docs.netgate.com/pfsense/en/latest/recipes/openvpn-multi-purpose.html
Feedback:
On the "OpenVPN Client specific overrides" section, it should note that for "Remote Access" networks, a custom option is needed on the OpenVPN server config when overriding the tunnel subnet to a different one. E.g. in the server custom options, add:
route "tunnelnetwork netmask"
Updated by Jim Pingle over 3 years ago
- Status changed from New to Rejected
That whole thing needs rewritten for subnet topology, it has several outdated techniques. If routes need to be added or pushed there are GUI fields for that, no need to use custom options.
Closing this since it would be covered by a rewrite.
Updated by Marcos M over 3 years ago
Indeed a rewrite would be good.
The remote IPv4 Remote field is missing from the Remote Access server mode which was the reason for the custom option.