Pls Help! Static routes on connecting clients

[ajl119]

Hello,
Please can someone help me, I am stuck trying to figure out how to push static routes to clients connecting to our 'OpenVPN Access Server'. I am getting completely lost because all the manuals seem to reference just 'OpenVPN', and not 'OpenVPN Access Server'.

Our 'OpenVPN Access Server' is located in the DMZ (10.0.1.0/24) and we are currently using Bridged mode.
I need the connecting clients to have a static route added that tells them the LAN (10.0.0.0/24) is via the DMZ's default gateway (10.0.1.254).
I would also like to have them use the DNS servers behind the 'OpenVPN Access Server'.

I have added the string 'push "route 10.0.0.0 255.255.255.0"' into the 'Server Config Directives' field on the Advanced VPN settings page of the 'OpenVPN Access Server's web interface but this doesn't work.
I have also added the string 'pull' into the 'Client Config Directives' field on the Advanced VPN settings page of the 'OpenVPN Access Server's web interface but this also doesn't work.

I have tried un-installing the Connect client just encase a new profile was not being updated etc.

I understand that this is cannot work on Linux and I will need to use an up script for that (something else I will need help with), but right now I cannot even get this route to be added on Windows or Mac clients using the 'Connect client' downloaded through the client web interface.

Please help, I am so confused right now as all the manuals reference OpenVPN and not OpenVPN Access Server
I just don't understand why it is so difficult to setup what must be one of the most common requirements!

Thanks for your help.

[ddog800]

Have you tried just configuring the routes in the Access Server GUI rather than mucking around in the config file? I had a similar setup and was able to get it working that way. I had some issues configuring via the GUI using direct routing (no NAT), but was eventually able to get it up after much gnashing of teeth. However, when I tested the routing w/ NAT option worked it immediately for me without hassle.

As always, YMMV depending on your exact configuration.

Edit: Also, are you actually verifying that the route hasn't been added by looking at the routing table on the client machine or just basing it off the fact that routing isn't working? The reason I ask is that sometimes the routes are pushed through OK, but there are other factors that can cause the actual routing to fail. For Windows you can check the routing table by dropping to a CMD prompt and typing route print and on Linux you can use (as root) route -n or netstat -rn