[vpn-help] VPN Tunnel connection Established, but no traffic passthrough

[Kevin VPN]

On 03/12/2012 11:47 AM, Alexis La Goutte wrote:
> Hi Henry,
>
> I'm no sure but the Pool Address don't the same with LAN (use a other Pool
> )
>
> Regards,
>
> On Thu, Mar 8, 2012 at 1:34 PM, Henry<henrysoo at gmail.com>  wrote:
>
>> Hi guys,
>>
>> I just set up Netgear FVS318G as gateway-to-client with Shrew VPN
>> Client. My problem is, the VPN tunnel connection established, but the
>> PING does not work when ping the local devices reside on the LAN side
>> of FVS318G. I cannot see any LAN resource as no traffic passing
>> through the VPN Tunnel.
>>
>> My configurations are:
>>
>> My PC (LAN IP: 192.168.2.10) with Shrew VPN client Installed -->  The
>> Internet -->  BiPAC 7700N [(LAN IP: 10.1.1.1/24, DMZ set to FVS318G
>> (WAN IP: 10.1.1.2, LAN IP: 192.168.1.1/24, First Pool: starting
>> 192.168.1.190 Ending IP: 192.168.1.199)]
>>
>> The Shrew VPN client configuration was set up by using the guide
>> www.shrew.net/support/wiki/HowtoNetgear. Under Topology Entry, Type:
>> Include, Address 192.168.1.0, Netmask: 255.255.255.0 were configured.
>>
>> I know the BiPAC 7700N does not allow VPN. But as I set the FVS318G in
>> DMZ (the DMZ works as I could vpn to FVS318G by Shrew VPN client),
>> would that be possible the BiPAC 7700N drop the VPN traffic still? I
>> also changed different IP Schemes in First Pool under Mode Config.But
>> it did the same, the VPN Tunnel established, but cannot ping the VPN
>> gateway and cannot access local resources behind the gateway.
>>

Hi Henry,

Alexis has correctly pointed out a problem.  The pool of addresses given 
out to VPN clients cannot overlap with the LAN subnet.  Try using a 
different Pool, for instance 192.168.50.190-192.168.50.199.