Solved

Netgear Site-Site IPsec VPN - Can't ping past gateway!

Posted on 2013-01-13
2
2,356 Views
Last Modified: 2013-01-27
Hi,

i have a setup with 2 x Netgear FVS318N routers connecting two offices via an IPsec VPN tunnel.

I can ping the gateway's LAN IP from location to location, however I cannot ping any nodes past the gateway

VPN Setup is like this

Head-Office:
FQDN: klmelbourne.smbnetworks.com.au
LAN IP: 192.168.0.0
Subnet: 255.255.255.0

Remote Office:
FQDN: klspringvale.smbnetworks.com.au
LAN IP: 192.168.150.0
Subnet: 255.255.255.0

Each office has an ADSL Modem setup in bridge mode, which then connects to the WAN port on the FVS318N router.

I can ping 192.168.0.2 (the FVS318N) from Remote Office.
I can ping 192.168.150.1 (the FVS318N) from Head-Office.

But thats it.
0
Comment
Question by:cgruber
2 Comments
 
LVL 12

Accepted Solution

by:
TomRScott earned 500 total points
ID: 38773049
Check for firewall rules denying ICMP. If not readily apparent, try adding a rule to allow ICMP service between the two networks via the VPN tunnel.

Make sure to properly reference the zones correctly. The subnet that is remote relative to another subnet is in the VPN zone whereas the local is in the LAN zone.

Also check how the VPN tunnel is setup. Is it possible that the VPN tunnel is defined/configured in such a way that confuses the remote internal gateway address for the remots subnet address. I have seen that in the past and the result is as you describe.

 - Tom
0
 
LVL 23

Expert Comment

by:Erik Bjers
ID: 38824797
I have not done a VPN with Netgear in many many years but I have created them with many other platforms.  I can not tell you exactly what setting to check on your Netgear but I can try to point you in the right direction.

To me this seems like an issue with either routing on your internal networks or with the VPN configuration so I will give you a few things to check,

1) Look at the FVS318s at either end and check the VPN configuration to make sure that the remote and local networks are set to the subnet and not to an individual IP, for instance 192.168.0.0 /24 and not 192.168.0.1 /36.

2) If you have more than one subnet behind either side of the VPN check your internal routing device and make sure it is forwarding traffic for the Subnets on the other side of the VPN to the FVS318

Good luck

eb
0

Featured Post

Microsoft Certification Exam 74-409

Veeam® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

It’s 2016. Password authentication should be dead — or at least close to dying. But, unfortunately, it has not traversed Quagga stage yet. Using password authentication is like laundering hotel guest linens with a washboard — it’s Passé.
Getting hacked is no longer a matter or "if you get hacked" — the 2016 cyber threat landscape is now titled "when you get hacked." When it happens — will you be proactive, or reactive?
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…

772 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question