I have tried adding routes for the ip pool, I am at a loss on why this isn't working. makes this router pointless....super frustrating PLEASE HELP

I see your post on the 3rd hasn't been replied to. Has anyone contacted you yet?

cmaslin wrote

I see your post on the 3rd hasn't been replied to. Has anyone contacted you yet?

NO ONE HAS CONTACTED ME...:confused:

Mizel wrote

NO ONE HAS CONTACTED ME...:confused:

I have nearly the same problem. I opened a new ticket but TPlink support is slow. It took two+ weeks to escalate an email support thread and they kept asking questions that I had already answered.

Frustrating.

Was this ever resolved? I am having the same issue.

I have the same issue, was this ever resolved?

I was able to resolve this as there were two issues.

1. The local cable company provided the modem/router at the remote end. By default, all of the protocol helpers were disabled, ie, IPsec passthrough was disabled. Since I was getting a public IP on my TPlink, it did not occur to me that the cable modem may not be completely transparent. Apparently, it is a "Feature" designed to encourage upgrades to business level services.

2. The second issue was a conflicting route left over from previous testing.

I was previously trying to get a remote TP-Link router to connect to a pfSense main router via IPsec, but I never got that working. TP-Link ER-604W on both ends (One is static IP, the other uses DDNS) is working nicely.

Hi guys,
I encountered the same problem, I believe it to be a bug in the router firmware and have reported it as such, however I'm happy to tell you that there is a workaround.

The basic issue is that the router does not send back the correct routing table entries to the client after connection in all cases.
You can verify this yourself in windows by checking the routing table.

I'll illustrate this with my own configuration.

my LAN network address is 172.16.106.0
when I initially set up client - network VPN, I followed the example in the guide, and created an address pool in the range 10.10.10.10. - 10.10.10.50 for VPN clients.
When I connected to the VPN, as you have all seen, it connected fine, but I was unable to contact any machine on my LAN.
What I discovered from the windows routing table, was that no route had been created for the 172.16.106 network.
Instead, a route to 10.0.0.0 had been created, which didn't make a great deal of sense.

However, I found that if I manually created a route to 172.16.106.0 then miraculously everything started to work.
To do this manually, check what your VPN client address is (in my case it was 10.10.10.10), and add the route in an administrator command prompt with (again using my network as an example)
route add 172.16.106.0 mask 255.255.255.0 10.10.10.10

There is also an automated way to achieve the same objective by changing the address pool so that the range is contained within the same superset as the LAN addresses.
In my example, I set the pool address range to be 172.16.108.1 - 172.16.108.50

Now when I connect to the VPN, the router creates for me a route for 172.16.0.0 which includes both the VPN client range, and the LAN subnet, so everything works as expected.

I hope that works for everyone.

P

Hello - I tried using your method on the LAN & VPN (adjusted for my subnets) to setup the er6120 for the site-to-site pptp vpn connection -

- I'm trying to use the er6120 to connect to a remote win 2008 pptp server where I see the same problem; the WAN makes the vpn connection (and the er6120 can be ping'd from the remote network side) but nothing on the er6120 LAN side can ping anything on the remote pptp side -

- the LAN side does not appear to be routing correctly to the WAN side - using your method (above), it still does not resolve the issue -

- I need to force all traffic through the VPN connection but I don't see any settings for that so I'm trying your method for routing -

My setup:

ER6120 <--> cable modem router <--> INTERNET <--> University (ISP) <--> Win 2008 RRAS PPTP (appropriate firewall exceptions; works for all other clients)

TL-ER6120 (NAT mode)
LAN = x.x.171.124
LAN DHCP = x.x.171.x to y

WAN = dynamic IP to cable modem / router = 192.168.1.1 (reserved dhcp static)
VPN - L2TP/PPTP - PPTP Client = server x.x.175.x with Remote Subnet x.x.175.0/24 (active and connected; assigned ip from remotepptp server)

Route Table
No. Destination Gateway Flags Logical Interface Physical Interface Metric
1 0.0.0.0/0 192.168.1.1 GS eth1 WAN1 0
2 x.x.171.0/24 N/A C eth0 LAN 0
3 x.x.175.0/24 x.x.175.x S pptp-vpn-0 WAN1 0
4 x.x.175.x N/A HP pptp-vpn-0 WAN1 2
5 192.168.1.0/24 N/A C eth1 WAN1 0

Any suggestions?

(yes, I've posted to support at TP-Link; they pointed to faqid=411 which is not a solution and that is how I setup the er6120 in the first place)

regards, chris o.

hi!

Have you found solution on this issue?? Sounds that no one answering from TP-LINK support team..

I'm having Same issue ...VPN connection was successfully established however I can't Ping the Server [ IP: 192.168.1.2 ].. or any computer on that network except for the TP-Link LAN IP 192.168.1.1

Here is my Setup..





Appreciate your help...

Thanks