On 10/12/2013 04:07 PM, Jim Harle wrote:
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: [email protected]
[mailto:[email protected]] On Behalf Of Ilan Almog
Sent: Saturday, October 12, 2013 10:14 AM To:
[email protected] 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.
<snip>
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?
Hi Ilan,
I would think it's a policy/rule setting of the RV042 that prevents
clients from seeing each other, not the Shrew client.
_______________________________________________
vpn-help mailing list
[email protected]
https://lists.shrew.net/mailman/listinfo/vpn-help
