On 11/07/14 10:00, Philipp Hagemeister wrote:
On modern systems, topology subnet should always be set, but it's missing in the configuration file. Add it with a short explanation.
NACK There are a few annoying issues with topology subnet esp when using server side things like route <remote subnet> <mask>
that will *fail* with 'topology subnet' ; until this is fixed this should NOT be considered the default.
JJK
Signed-off-by: Philipp Hagemeister <phi...@phihag.de> --- sample/sample-config-files/server.conf | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/sample/sample-config-files/server.conf b/sample/sample-config-files/server.conf index f483b6b..6a2b4c2 100644 --- a/sample/sample-config-files/server.conf +++ b/sample/sample-config-files/server.conf @@ -86,6 +86,13 @@ key server.key # This file should be kept secret # 2048 bit keys. dh dh1024.pem +# Network topology +# Should be subnet (addressing via IP) +# unless Windows clients v2.0.9 and lower have to +# be supported (then net30, i.e. a /30 per client) +# Defaults to net30 (not recommended) +;topology subnet + # Configure server mode and supply a VPN subnet # for OpenVPN to draw client addresses from. # The server will take 10.8.0.1 for itself, ------------------------------------------------------------------------------ Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft _______________________________________________ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel