TinCanTech wroteI ditched windows completely and never looked back 8-)
I do not disagree but it's a big discussion.
TinCanTech wroteopapanik wrote1. added routing from 10.20.31.0/24 (VPN addresses) to 10.20.30.10 (LAN IP of windows VPN server)
You might expect this to work .. but .. instead, select a host you want to be able to ping over the VPN and add static routes to it.
I am not really sure I understand what you say I should switch it to. This was according to the HOWTO:
"The last step, and one that is often forgotten, is to add a route to the server's LAN gateway which directs 192.168.4.0/24 to the OpenVPN server box (you won't need this if the OpenVPN server box is the gateway for the server LAN)."
and as far as I can tell it is the reason I can ping from any LAN machine to the VPN client. It is referred as static routing on the router.
TinCanTech wroteNO .. you do not require routing both ways because the server LAN host will only see the VPN IP.
Thanks for clearing this.
TinCanTech wroteDo not try to use the server log at high verb-age to confirm packet transmission, that is not what the log is telling you. Use Wireshark on the server (or other sniffer) to determine where the packets are discarded.
True but at least as a quick and dirty trick I could confirm the ping is routed from the client through the VPN and reaches the server, no? The problem begins there..
