Business Community > Routers > TL-ER6020 VPN lack of stability SafeStream Gigabit Multi-WAN VPN Router
< Routers

TL-ER6020 VPN lack of stability SafeStream Gigabit Multi-WAN VPN Router

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

TL-ER6020 VPN lack of stability SafeStream Gigabit Multi-WAN VPN Router

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
TL-ER6020 VPN lack of stability SafeStream Gigabit Multi-WAN VPN Router
TL-ER6020 VPN lack of stability SafeStream Gigabit Multi-WAN VPN Router
2019-12-31 00:30:52 - last edited 2021-04-19 11:37:18
Model: TL-ER6020  
Hardware Version: V2
Firmware Version: 2.0.2 Build 20180702 Rel.59031

Hi anyone found stability or the way to have stability even via dynamic reconnect on L2TP wan VPN interface on these routers?

 

sample log, even after reboot, noting use most any other VPN with this site and do not have issues...

 

Log List

Refresh

Delete All

ID Time Module Level Content
1 2019-12-31 11:30:12 L2TP NOTICE WAN1: L2TP client was disconnected.
2 2019-12-31 11:30:12 PPP WARNING WAN1: LCP sending TERMINAL-REQUEST timeout.
3 2019-12-31 11:29:53 PPP NOTICE WAN1: IPCP negotiation succeeded. (Local=10.0.1.233, Peer=1.0.0.1, DNS1=10.0.1.1, DNS2=0.0.0.0, MTU=1500)
4 2019-12-31 11:29:50 PPP NOTICE WAN1: pfr7ik authenticated.
5 2019-12-31 11:29:49 PPP NOTICE WAN1: LCP negotiation succeeded. (MTU=1500, AUTH=)
6 2019-12-31 11:29:49 L2TP NOTICE WAN1: L2TP client began connecting.
7 2019-12-31 11:29:48 IPsec NOTICE WAN1: Phase 2 of IKE negotiation succeeded. (Peers=10.0.1.19<->167.160.56.87)
8 2019-12-31 11:29:48 L2TP NOTICE WAN1: L2TP client was disconnected.
9 2019-12-31 11:29:48 PPP WARNING WAN1: LCP sending TERMINAL-REQUEST timeout.
10 2019-12-31 11:29:47 IPsec NOTICE WAN1: Phase 1 of IKE negotiation succeeded. (Peers=10.0.1.19<->167.160.56.87)
11 2019-12-31 11:29:47 IPsec NOTICE WAN1: IKE negotiation began in initiator mode. (Mode=Main Mode, Peers=10.0.1.19<->167.160.56.87)
12 2019-12-31 11:29:29 PPP NOTICE WAN1: IPCP negotiation succeeded. (Local=10.0.1.120, Peer=1.0.0.1, DNS1=10.0.1.1, DNS2=0.0.0.0, MTU=1500)
13 2019-12-31 11:29:26 PPP NOTICE WAN1: pfr7ik authenticated.
14 2019-12-31 11:29:25 PPP NOTICE WAN1: LCP negotiation succeeded. (MTU=1500, AUTH=)
15 2019-12-31 11:29:24 L2TP NOTICE WAN1: L2TP client began connecting.
16 2019-12-31 11:29:23 IPsec NOTICE WAN1: Phase 2 of IKE negotiation succeeded. (Peers=10.0.1.19<->45.56.155.251)
17 2019-12-31 11:29:23 L2TP NOTICE WAN1: L2TP client was disconnected.
18 2019-12-31 11:29:23 PPP WARNING WAN1: LCP sending TERMINAL-REQUEST timeout.
19 2019-12-31 11:29:23 IPsec NOTICE WAN1: Phase 1 of IKE negotiation succeeded. (Peers=10.0.1.19<->45.56.155.251)
20 2019-12-31 11:29:22 IPsec NOTICE WAN1: IKE negotiation began in initiator mode. (Mode=Main Mode, Peers=10.0.1.19<->45.56.155.251)
21 2019-12-31 11:29:17 L2TP NOTICE WAN1: L2TP client failed to connect the server.
22 2019-12-31 11:29:17 PPP NOTICE WAN1: LCP negotiation succeeded. (MTU=1500, AUTH=)
23 2019-12-31 11:29:16 L2TP NOTICE WAN1: L2TP client began connecting.
24 2019-12-31 11:29:15 IPsec NOTICE WAN1: Phase 2 of IKE negotiation succeeded. (Peers=10.0.1.19<->167.160.56.86)
25 2019-12-31 11:29:15 IPsec NOTICE WAN1: Phase 1 of IKE negotiation succeeded. (Peers=10.0.1.19<->167.160.56.86)
26 2019-12-31 11:29:14 IPsec NOTICE WAN1: IKE negotiation began in initiator mode. (Mode=Main Mode, Peers=10.0.1.19<->167.160.56.86)
27 2019-12-31 11:28:19 L2TP NOTICE WAN1: L2TP client was disconnected.
28 2019-12-31 11:28:19 PPP WARNING WAN1: LCP sending TERMINAL-REQUEST timeout.
29 2019-12-31 11:17:10 Web NOTICE 192.168.0.128 logged into the web interface successfully.
30 2018-01-01 00:01:00 PPP NOTICE WAN1: IPCP negotiation succeeded. (Local=10.0.1.148, Peer=1.0.0.1, DNS1=10.0.1.1, DNS2=0.0.0.0, MTU=1500)
31 2018-01-01 00:00:56 PPP NOTICE WAN1: pfr7ik authenticated.
32 2018-01-01 00:00:56 PPP NOTICE WAN1: LCP negotiation succeeded. (MTU=1500, AUTH=)
33 2018-01-01 00:00:55 L2TP NOTICE WAN1: L2TP client began connecting.
34 2018-01-01 00:00:54 IPsec NOTICE WAN1: Phase 2 of IKE negotiation succeeded. (Peers=10.0.1.19<->167.160.56.86)
35 2018-01-01 00:00:53 IPsec NOTICE WAN1: Phase 1 of IKE negotiation succeeded. (Peers=10.0.1.19<->167.160.56.86)
36 2018-01-01 00:00:52 IPsec NOTICE WAN1: IKE negotiation began in initiator mode. (Mode=Main Mode, Peers=10.0.1.19<->167.160.56.86)
37 2018-01-01 00:00:43 PPP NOTICE WAN1: IPCP negotiation succeeded. (Local=10.0.1.19, Peer=1.0.0.1, DNS1=10.0.1.1, DNS2=0.0.0.0, MTU=1460)
38 2018-01-01 00:00:40 PPP NOTICE WAN1: pfr7ik authenticated.
39 2018-01-01 00:00:39 PPP NOTICE WAN1: LCP negotiation succeeded. (MTU=1460, AUTH=)
40 2018-01-01 00:00:39 L2TP NOTICE WAN1: L2TP client began connecting.
41 2018-01-01 00:00:32 DHCP Client NOTICE WAN1: DHCP client getting IP succeeded. (IP-Address=192.168.13.3, Mask=255.255.255.0, Gateway=192.168.13.1)
42 2018-01-01 00:00:32 DHCP Server NOTICE DHCP Server allocated IP address 192.168.0.128 for the client[MAC: 10:bf:48:d3:58:08].
43 2018-01-01 00:00:25 DHCP Client NOTICE WAN1: DHCP client releasing IP address succeeded. (IP-Address=0.0.0.0)
44 2018-01-01 00:00:05 DHCP Server INFO

DHCPS initialization succeeded
 

 
  1      
 
  1      
 
#1
Options
4 Reply
Re:TL-ER6020 VPN lack of stability SafeStream Gigabit Multi-WAN VPN Router
2019-12-31 02:01:23 - last edited 2021-04-19 11:37:18

@GuyLoucks 

 

For TP-Link L2TP/PPTP WAN VPN, it's as a dailup way, seemly used for getting IP address only. Because it doesn't support encryption, so it's hardly used for VPN.

 

If you want to establish VPN, you can use the VPN module of the router. It supports PPTP/L2TP/IPsec VPN and supports encryption.

  0  
  0  
#2
Options
Re:TL-ER6020 VPN lack of stability SafeStream Gigabit Multi-WAN VPN Router
2019-12-31 06:15:42 - last edited 2021-04-19 11:37:18

@Andone 

Hi,

hmm, ok they've the selection on the WAN interface will look at cooking up a VPN l2tp connection profile, although with the devices stability to date and a few write ups I've read this will be the last item I think I'll try. right now a raspberry pi and couple USB Ethernet would Leave this device to the dark ages.

Guy

  0  
  0  
#3
Options
Re:TL-ER6020 VPN lack of stability SafeStream Gigabit Multi-WAN VPN Router
2021-05-11 16:01:12

@GuyLoucks  I have the same problem.

 

I have 2 Windows Server RRAS, L2TP VPN, and

two TL-ER6120 Router.

Router A  -> Windows Server VPN1

Router B  -> Windows Server VPN2

I try to do this to establish a "Site to Site" VPN connection betwen Router A and B. 

 

Both Router will get

"WAN1: LCP sending TERMINAL-REQUEST timeout."

and disconnected then reconnect in about within about a hour.

 

There were time it stuck at

"WAN1: IKE negotiation began in initiator mode. (Mode=Main Mode, Peers=72.12.141.146<->72.12.141.106)"

Loop repeating, it was resolved by restarting the router..

 

58 2021-05-11 11:22:11 PPP NOTICE WAN1: IPCP negotiation succeeded. (Local=172.16.10.8, Peer=172.16.10.1, DNS1=172.16.0.1, DNS2=0.0.0.0, MTU=1400)
59 2021-05-11 11:22:11 PPP NOTICE WAN1: VPN.Router authenticated.
60 2021-05-11 11:22:11 PPP NOTICE WAN1: LCP negotiation succeeded. (MTU=1400, AUTH=mschap2)
61 2021-05-11 11:22:10 L2TP NOTICE WAN1: L2TP client began connecting.
62 2021-05-11 11:22:09 IPsec NOTICE WAN1: Phase 2 of IKE negotiation succeeded. (Peers=72.12.141.146<->72.12.141.106)
63 2021-05-11 11:22:09 IPsec NOTICE WAN1: Phase 1 of IKE negotiation succeeded. (Peers=72.12.141.146<->72.12.141.106)
64 2021-05-11 11:22:09 IPsec NOTICE WAN1: IKE negotiation began in initiator mode. (Mode=Main Mode, Peers=72.12.141.146<->72.12.141.106)
65 2021-05-11 11:20:45 L2TP NOTICE WAN1: L2TP client was disconnected.
66 2021-05-11 11:20:45 PPP WARNING WAN1: LCP sending TERMINAL-REQUEST timeout.
67 2021-05-11 11:20:38 IPsec NOTICE

WAN1: Phase 2 of IKE negotiation succeeded. (Peers=72.12.141.146<->72.12.141.106)

 

 

 

  0  
  0  
#4
Options
Re:TL-ER6020 VPN lack of stability SafeStream Gigabit Multi-WAN VPN Router
2021-05-12 08:23:33

@ErwinMusk 

yeah, mine is now a doorstop went to a WRTAC3200 or whatever they were runs std Linux ish and can reliably do the task. Busybox, netbsd, and a Raspberry Pi can probably do these bits now...

The platform had an opportunity, I've found this with a lot of the supply channels if you get to tech they want you to pay to fix their code, although did have one email me the sources... still using that USB serial... bug free, think I even sent them the fix for being helpful.

  0  
  0  
#5
Options

Information

Helpful: 1

Views: 1843

Replies: 4

About Us
Press
Copyright © TP-Link Corporation Limited. All rights reserved.