[vpn-help] RV042 VPN works great for multiple clients, clients cannot see / ping each other

[Jim Harle]

FWIW I just connected two Shrew 2.2.2 Windows clients to the same Cisco ASA gateway, and they could ping/connect to open ports on each other's virtual private interfaces as their Windows firewalls would allow, so I don't believe any "client-to-client" blockage is inherent in the Shrew tunnels.

-----Original Message-----
From: vpn-help-bounces at lists.shrew.net [mailto:vpn-help-bounces at lists.shrew.net] On Behalf Of Ilan Almog
Sent: Saturday, October 12, 2013 10:14 AM
To: vpn-help at lists.shrew.net
Subject: [vpn-help] RV042 VPN works great for multiple clients, clients cannot see / ping each other

Hello all!

I have been using Shrew to maintain (for a couple of years already) a 
very stable VPN with a Cisco RV042 without any issues after it was 
properly configured.

GroupVPN is the setting on the RV042. As there are few clients (road 
warriors), I just assign a unique IP for each and there is no conflict 
or knocking the other client out.

The clients can access any device and service in the LAN behind the 
RV042. Likewise, any device within the LAN is able to access any 
client's services/files etc.

However, no client is able to see / ping another client!
I've tried several routing configurations under the Policy tab of Shrew, 
several IP/netmask combinations for the clients -- nothing worked.

Is this possible to be done or is there something inherent in the way 
the tunnels are established that clients really cannot see each other?

Kindly advise.

Cheers,

-- Ilan

_______________________________________________
vpn-help mailing list
vpn-help at lists.shrew.net
https://lists.shrew.net/mailman/listinfo/vpn-help