Is it possible to reconnect VPN automatically?

[SHAH]

Is it possible in "Merlin" firmware to "auto-connect" VPN after it gets disconnect? Whether i use openVPN or L2TP ? please help ?

 

[RMerlin]

Is it possible in "Merlin" firmware to "auto-connect" VPN after it gets disconnect? Whether i use openVPN or L2TP ? please help ?

For OpenVPN, change the Poll Interval value from "0" to the frequency (in minutes) at which you want the tunnel to be checked.

No idea about L2TP, I never used it.

 

[SHAH]

thanks for the support. its working now. if you know about l2tp as well or u can try please let me know.

 

[Speedy1205]

thanks for the support. its working now. if you know about l2tp as well or u can try please let me know.

well in the GUI there isn't much option for the l2tp.... there is the profile name, Server, Username and Password. So there isn't any GUI option to change for reconnect.

Why you want to use the L2TP ? Is OpenVPN not a bit more secure ?

 

[SHAH]

well in the GUI there isn't much option for the l2tp.... there is the profile name, Server, Username and Password. So there isn't any GUI option to change for reconnect.

Why you want to use the L2TP ? Is OpenVPN not a bit more secure ?

im using HMA VPN and they recommend for better speed and latency use L2TP :/ thats the only reason im leaning towards it.

 

[micjustin33]

Read about VPN kill Switch might it will be helpful for you

 

[shpankey]

im using HMA VPN and they recommend for better speed and latency use L2TP :/ thats the only reason im leaning towards it.

HMA's L2TP is definitely much faster w/ better latency than their OpenVPN servers. I just wanted to add that fact, as it's something I came to find out on my own, the hard way. Don't even bother w/ their OpenVPN servers, they are terribly slow.

 

[SHAH]

HMA's L2TP is definitely much faster w/ better latency than their OpenVPN servers. I just wanted to add that fact, as it's something I came to find out on my own, the hard way. Don't even bother w/ their OpenVPN servers, they are terribly slow.

thanks man for confirming it. Its really pain it gets disconnect after 15 to 16hrs then i have to connect again :S

 

[Speedy1205]

can you check the exactly process running for the VPN (with top or whatever) and send the system log from the router. I can have a look into this. I just need some more input and than I can check if there can be done some manually. As I don't use this I need some input.

 

[SHAH]

here is the log...

can you check the exactly process running for the VPN (with top or whatever) and send the system log from the router. I can have a look into this. I just need some more input and than I can check if there can be done some manually. As I don't use this I need some input.

Apr 29 16:56:04 pppd[595]: Connection terminated.
Apr 29 16:56:04 pppd[595]: Modem hangup
Apr 29 16:56:14 pppd[595]: Connected to 00:90:1a:a4:3e:8d via interface eth0
Apr 29 16:56:14 pppd[595]: Connect: ppp0 <--> eth0
Apr 29 16:56:15 pppd[595]: PAP authentication succeeded
Apr 29 16:56:15 pppd[595]: peer from calling number 00:90:1A:A4:3E:8D authorized
Apr 29 16:56:15 pppd[595]: local IP address
Apr 29 16:56:15 pppd[595]: remote IP address
Apr 29 16:56:15 pppd[595]: primary DNS address 182.176.100.139
Apr 29 16:56:15 pppd[595]: secondary DNS address 116.71.241.216
Apr 29 16:56:15 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_eth0)!
Apr 29 16:56:15 rc_service: ip-up 1032:notify_rc stop_upnp
Apr 29 16:56:15 miniupnpd[673]: received signal 15, good-bye
Apr 29 16:56:15 rc_service: ip-up 1032:notify_rc start_upnp
Apr 29 16:56:15 rc_service: waitting "stop_upnp" via ip-up ...
Apr 29 16:56:16 ddns: clear ddns cache file for server/hostname change
Apr 29 16:56:17 miniupnpd[1069]: HTTP listening on port 44069
Apr 29 16:56:17 miniupnpd[1069]: Listening for NAT-PMP traffic on port 5351
Apr 29 16:56:17 ddns update: ez-ipupdate: starting...
Apr 29 16:56:17 ddns update: connected to ns1.asuscomm.com (103.10.4.108) on port 80.
Apr 29 16:56:17 WAN Connection: WAN was restored.
Apr 29 16:56:18 ddns update: Asus update entry:: return: HTTP/1.1 200 OK^M Date: Tue, 29 Apr 2014 11:49:47 GMT^M Server: Apache/2.4.9 (Unix) PHP/5.4.14^M X-Powered-By: PHP/5.4.14^M Content-Length: 0^M Connection: close^M Content-Type: text/html^M ^M
Apr 29 16:56:18 ddns update: retval= 0, ddns_return_code (,200)
Apr 29 16:56:18 ddns update: asusddns_update: 0
Apr 29 16:56:18 ddns: ddns update ok
Apr 29 17:03:43 pppd[595]: Protocol-Reject for unsupported protocol 0x8061
Apr 29 17:14:33 pppd[595]: Protocol-Reject for unsupported protocol 0x8095
Apr 29 17:22:18 pppd[595]: Protocol-Reject for unsupported protocol 0xc091
Apr 29 17:38:03 pppd[595]: Protocol-Reject for unsupported protocol 0xee00
Apr 29 17:40:47 pppd[595]: Protocol-Reject for unsupported protocol 0xde21
Apr 29 17:53:22 pppd[595]: Protocol-Reject for unsupported protocol 0xc061
Apr 29 18:10:55 pppd[595]: Protocol-Reject for unsupported protocol 0x8001
Apr 29 18:21:00 kernel: br0: received packet on eth1 with own address as source address
Apr 29 18:23:25 kernel: br0: received packet on eth2 with own address as source address
Apr 29 18:23:32 kernel: br0: received packet on eth1 with own address as source address
Apr 29 18:27:58 kernel: br0: received packet on eth2 with own address as source address
Apr 29 18:30:09 pppd[595]: Protocol-Reject for unsupported protocol 0x8061
Apr 29 18:35:53 pppd[595]: Protocol-Reject for unsupported protocol 0x8061
Apr 29 18:55:05 miniupnpd[1069]: sendto(udp): Operation not permitted
Apr 29 19:18:52 pppd[595]: Protocol-Reject for unsupported protocol 0x8001
Apr 29 19:20:53 kernel: br0: received packet on eth1 with own address as source address
Apr 29 19:28:34 miniupnpd[1069]: sendto(udp): Operation not permitted
Apr 29 19:57:15 pppd[595]: Protocol-Reject for unsupported protocol 0xf801
Apr 29 20:00:05 pppd[595]: Protocol-Reject for unsupported protocol 0xaa23
Apr 29 20:00:56 rc_service: httpd 509:notify_rc restart_vpncall
Apr 29 20:01:18 pppd[1248]: pppd 2.4.5 started by admin, uid 0
Apr 29 20:01:18 pppd[1248]: Connect: ppp5 <--> l2tp (160.200.46.192)
Apr 29 20:01:18 pppd[1248]: Overriding mtu 1500 to 1400
Apr 29 20:01:18 pppd[1248]: Overriding mru 1500 to mtu value 1400
Apr 29 20:01:18 pppd[1248]: Overriding mru 1500 to mtu value 1400
Apr 29 20:01:19 pppd[1248]: CHAP authentication succeeded
Apr 29 20:01:19 pppd[1248]: local IP address
Apr 29 20:01:19 pppd[1248]: remote IP address
Apr 29 20:01:19 pppd[1248]: primary DNS address 208.67.222.222
Apr 29 20:01:19 pppd[1248]: secondary DNS address 208.67.220.220
Apr 29 20:01:45 pppd[1248]: Protocol-Reject for unsupported protocol 0x4021
Apr 29 20:12:33 pppd[595]: Protocol-Reject for unsupported protocol 0xc095
Apr 29 20:16:17 pppd[595]: Protocol-Reject for unsupported protocol 0xc421
Apr 29 20:18:29 pppd[1248]: Protocol-Reject for unsupported protocol 0x221
Apr 29 20:26:28 kernel: br0: received packet on eth2 with own address as source address
Apr 29 20:26:31 kernel: br0: received packet on eth1 with own address as source address
Apr 29 20:38:28 pppd[595]: Protocol-Reject for unsupported protocol 0xc061
Apr 29 20:57:18 pppd[1248]: Protocol-Reject for unsupported protocol 0xdf
Apr 29 20:57:39 pppd[1248]: Protocol-Reject for unsupported protocol 0x23
Apr 29 20:58:56 pppd[1248]: Protocol-Reject for unsupported protocol 0xe821
Apr 29 20:59:38 pppd[1248]: Protocol-Reject for unsupported protocol 0x1
Apr 29 21:04:48 pppd[1248]: Protocol-Reject for unsupported protocol 0x79
Apr 29 21:09:20 pppd[1248]: Protocol-Reject for unsupported protocol 0xa1
Apr 29 21:12:03 pppd[595]: Protocol-Reject for unsupported protocol 0xc061
Apr 29 21:12:38 pppd[1248]: Protocol-Reject for unsupported protocol 0x23
Apr 29 21:16:54 pppd[595]: Protocol-Reject for unsupported protocol 0x8091
Apr 29 21:21:27 pppd[1248]: Protocol-Reject for unsupported protocol 0x23
Apr 29 21:27:44 pppd[1248]: Protocol-Reject for unsupported protocol 0x71
Apr 29 21:28:16 pppd[1248]: Protocol-Reject for unsupported protocol 0x24
Apr 29 21:29:09 pppd[1248]: Protocol-Reject for unsupported protocol 0xe1
Apr 29 21:29:48 pppd[1248]: Protocol-Reject for unsupported protocol 0x2a26
Apr 29 21:30:09 kernel: br0: received packet on eth2 with own address as source address
Apr 29 21:32:14 kernel: br0: received packet on eth2 with own address as source address
Apr 29 21:32:18 kernel: br0: received packet on eth1 with own address as source address
Apr 29 21:34:53 kernel: br0: received packet on eth2 with own address as source address
Apr 29 21:34:53 kernel: br0: received packet on eth2 with own address as source address
Apr 29 21:34:55 kernel: br0: received packet on eth1 with own address as source address
Apr 29 21:35:38 kernel: br0: received packet on eth2 with own address as source address
Apr 29 21:35:47 kernel: br0: received packet on eth1 with own address as source address
Apr 29 21:41:15 kernel: br0: received packet on eth2 with own address as source address
Apr 29 21:41:45 kernel: br0: received packet on eth1 with own address as source address
Apr 29 21:48:08 kernel: br0: received packet on eth2 with own address as source address
Apr 29 21:48:19 kernel: br0: received packet on eth1 with own address as source address
Apr 29 21:54:41 pppd[1248]: Protocol-Reject for unsupported protocol 'Bridging PDU' (0x31)
Apr 29 21:55:36 pppd[1248]: Protocol-Reject for unsupported protocol 0x4b
Apr 29 21:56:43 pppd[1248]: Protocol-Reject for unsupported protocol 0x221
Apr 29 21:59:09 pppd[1248]: Protocol-Reject for unsupported protocol 0x1e20
Apr 29 22:04:46 pppd[1248]: Protocol-Reject for unsupported protocol 0xd061
Apr 29 22:05:02 kernel: br0: received packet on eth2 with own address as source address
Apr 29 22:05:04 kernel: br0: received packet on eth1 with own address as source address
Apr 29 22:05:07 kernel: br0: received packet on eth2 with own address as source address
Apr 29 22:05:16 kernel: br0: received packet on eth1 with own address as source address
Apr 29 22:05:22 pppd[1248]: Protocol-Reject for unsupported protocol 0x1e20
Apr 29 22:09:21 pppd[1248]: Protocol-Reject for unsupported protocol 0x7f
Apr 29 22:09:52 pppd[1248]: Protocol-Reject for unsupported protocol 0xfe43
Apr 29 22:11:07 pppd[1248]: Protocol-Reject for unsupported protocol 0x221
Apr 29 22:11:22 pppd[1248]: Protocol-Reject for unsupported protocol 'Individual Link Encryption' (0x55)
Apr 29 22:11:58 pppd[1248]: LCP: Rcvd Code-Reject for code 138, id 51
Apr 29 22:19:55 pppd[1248]: Protocol-Reject for unsupported protocol 0xfee7
Apr 29 22:25:25 pppd[1248]: Protocol-Reject for unsupported protocol 0x4021

 

[bushidodragon76]

RMerlin great job with the firmware, the first thing I did to my new RT68u was to install your firmware. I've been following this and other questions about open vpn in the hope I could find an answer to my problem. I'm using your latest firmware although I had the same issue with earlier version too and my vpn provider is Private Internet Access. I've played around with the poll, connection retry and TLS renegotiation in an attempt to get the vpn to reconnect after dropping but in very case it refuses to. The message I keep getting is " openvpn[2007]: RESOLVE: Cannot resolve host address: uk-london.privateinternetaccess.com: Name or service not known". I can get it to reconnect by just pushing the apply button at the bottom. Is there something I'm missing or a script that I can add to sort this issue? Thx

Sent from my GT-N5100 using Tapatalk

 

[RMerlin]

RMerlin great job with the firmware, the first thing I did to my new RT68u was to install your firmware. I've been following this and other questions about open vpn in the hope I could find an answer to my problem. I'm using your latest firmware although I had the same issue with earlier version too and my vpn provider is Private Internet Access. I've played around with the poll, connection retry and TLS renegotiation in an attempt to get the vpn to reconnect after dropping but in very case it refuses to. The message I keep getting is " openvpn[2007]: RESOLVE: Cannot resolve host address: uk-london.privateinternetaccess.com: Name or service not known". I can get it to reconnect by just pushing the apply button at the bottom. Is there something I'm missing or a script that I can add to sort this issue? Thx

Sent from my GT-N5100 using Tapatalk

If you are sure the host address is correct, there could be a timing issue between the WAN connection, name resolution, and the VPN client starting. Try replacing the server hostname by its IP.

 

[busch09]

For OpenVPN, change the Poll Interval value from "0" to the frequency (in minutes) at which you want the tunnel to be checked.

No idea about L2TP, I never used it.

Where /How Do you set this in todays version?
I dont see a server poll 0 line on vpn client setup page

 

[CaptainSTX]

Check that the command below is in the custom configuration section. It is included in the PIA OVPN files that you download from their configuration generator.

resolv-retry infinite