Multi-WAN oVPN Server, single WAN oVPN Client - Server can't ping client

[naughtyusmaximus]

I have an OpenVPN server with a multi wan setup, and a single WAN OpenVPN client across the globe somewhere.  People on the LAN side of the openVPN client can ping clients on the LAN side of the server network, but not the other way around.  If I connect via ssh to the server, I can ping clients on the client LAN side, so I know that it is close to working…

OpenVPN Server: 192.168.10.1
OpenVPN Client: 192.168.30.1

192.168.30.x can ping and connect to 192.168.10.x
192.168.10.x can not ping or connect to 192.168.30.x

I know this has been posted before, and I've searched and read the articles I think are relevant.  The common solution is to create a rule on the LAN side of the server above all load balancing rules which will allow traffic to the VPN subnet.  I believe I have created this rule properly, but of course I still can't ping the clients from here.

My rule is as follows:

 TCP/UDP  	 LAN net  	 *  	 192.168.30.0/24  	 *  	 *  	    	 Allow Connect Indo 
```Any help would be greatly appreciated!

[nastraga]

Hi,

If you're interested in pinging across the link, I advise you change your rule to allow Protocol -> ANY, instead of TCP/UDP.  Pinging requires ICMP traffic.