ipVanish OpenVPN Setup

Post new topic   Reply to topic    DD-WRT Forum Index -> Advanced Networking
Goto page Previous  1, 2, 3, 4
Author Message
ThirdStarr
DD-WRT Novice


Joined: 22 Feb 2018
Posts: 3

PostPosted: Thu Feb 22, 2018 17:31    Post subject: Unable to setup OpenVPN client after update Reply with quote
Yesterday after successfully setting up IpVanish with OpenVPN, I found this thread about ipVanish OpenVPN Setup and decided to update my .chk and .bin file for Netgear R6400.
The updates appeared to be successful and I even updated the CA Cert from the link in this thread, but now I get the following message in my SysLog and OpenVPN is not connecting

Jan 1 00:00:16 DD-WRT user.info : openvpn : OpenVPN daemon (Client) successfully stopped
Jan 1 00:00:16 DD-WRT daemon.debug ntpclient[1026]: Connecting to 2.pool.ntp.org [2001:1900:201e:6:6e62:6dff:fee5:821] ...
Jan 1 00:00:16 DD-WRT daemon.err ntpclient[1026]: Failed connecting to 2.pool.ntp.org [2001:1900:201e:6:6e62:6dff:fee5:821]: Address family not supported by protocol
Jan 1 00:00:16 DD-WRT daemon.debug ntpclient[1026]: Connecting to 212.18.3.19 [212.18.3.19] ...
Feb 22 12:21:34 DD-WRT daemon.info ntpclient[1026]: Time set from 212.18.3.19 [212.18.3.19].
Feb 22 12:21:34 DD-WRT daemon.err process_monitor[1025]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Feb 22 12:21:34 DD-WRT daemon.debug process_monitor[1025]: Restarting cron (time sync change)
Feb 22 12:21:34 DD-WRT user.info : cron : cron daemon successfully stopped
Feb 22 12:21:34 DD-WRT user.info : process_monitor : Process Monitor successfully stopped
Feb 22 12:21:34 DD-WRT user.info : cron : cron daemon successfully started
Feb 22 12:21:34 DD-WRT cron.info cron[1050]: (CRON) STARTUP (fork ok)
Feb 22 12:21:35 DD-WRT daemon.err openvpn[931]: RESOLVE: Cannot resolve host address: atl-a26.ipvanish.com:443 (Try again)
Feb 22 12:21:35 DD-WRT daemon.notice openvpn[931]: Socket Buffers: R=[180224->180224] S=[180224->180224]
Feb 22 12:21:35 DD-WRT daemon.notice openvpn[931]: UDPv4 link local: (not bound)
Feb 22 12:21:35 DD-WRT daemon.notice openvpn[931]: UDPv4 link remote: [AF_INET]205.185.209.28:443
Feb 22 12:21:35 DD-WRT daemon.notice openvpn[931]: SIGTERM[hard,init_instance] received, process exiting
Feb 22 12:21:36 DD-WRT user.info : process_monitor : Process Monitor hanging, send SIGKILL
Feb 22 12:21:36 DD-WRT user.info : process_monitor successfully started
Feb 22 12:21:36 DD-WRT daemon.debug process_monitor[1052]: We need to re-update after 3600 seconds
Feb 22 12:21:36 DD-WRT daemon.info process_monitor[1052]: set timer: 3600 seconds, callback: ntp_main()
Feb 22 12:21:43 DD-WRT user.info : NAS : NAS lan (wl0 interface) successfully started
Feb 22 12:21:43 DD-WRT user.info : NAS : NAS lan (wl1 interface) successfully started
Feb 22 12:21:43 DD-WRT user.info : syslogd : syslog daemon successfully stopped
Feb 22 07:21:43 DD-WRT syslog.info syslogd exiting
Feb 22 07:21:43 DD-WRT syslog.info syslogd started: BusyBox v1.28.0
Feb 22 12:21:43 DD-WRT user.info : httpd : http daemon successfully stopped

How and what do I need to modify to get it working again.

Thanks
Sponsor
spuriousoffspring
DD-WRT Guru


Joined: 05 Apr 2017
Posts: 981
Location: Louisiana, USA

PostPosted: Thu Feb 22, 2018 17:50    Post subject: Reply with quote
Looks like the problem is with NTP. The time on your router has to match the VPN server you’re connecting to.
I do remember reading on the Marvel Forum about an issue with NTP on some of the latest builds. Not sure if this would apply to you, but may be worth checking into.

Try pool.ntp.org. This will automatically choose the closest, operational time server to you.
Also, make sure time zone is correct.

If you’re still having trouble connecting to VPN, try a different IPVanish Server. They go offline from time to time.

_________________
DD-WRT Installation & Setup TUTORIAL
http://www.dd-wrt.com/phpBB2/viewtopic.php?t=311117

WRT32X DD-WRT Installation Procedure
https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=315569

IPVanish OpenVPN Client Setup TUTORIAL
http://www.dd-wrt.com/phpBB2/viewtopic.php?t=308565

FIRMWARE: OpenWrt SNAPSHOT r8217-2cc821e / LuCI Master (git-18.276.41146-280dd33)
MODEM: ARRIS SURFBoard SB8200
ROUTER: Linksys WRT32X
USB NAS: Western Digital BLACK 1 TB Hardrive + Startech USB 3.0 External SATA III Enclosure
ThirdStarr
DD-WRT Novice


Joined: 22 Feb 2018
Posts: 3

PostPosted: Thu Feb 22, 2018 19:29    Post subject: Reply with quote
Thank you for everyone's assistance. As suggested I disabled OpenVPN Client, Saved, Applied, Rebooted the router. Waited 10 mins then Enabled OpenVPN Client, Saved, Applied, Rebooted. Here are the logs:

Jan 1 00:00:15 DD-WRT user.info : ttraff : traffic counter daemon successfully started
Jan 1 00:00:15 DD-WRT daemon.warn openvpn[844]: WARNING: --keysize is DEPRECATED and will be removed in OpenVPN 2.6
Jan 1 00:00:15 DD-WRT daemon.warn openvpn[844]: WARNING: file '/tmp/openvpncl/credentials' is group or others accessible
Jan 1 00:00:15 DD-WRT daemon.notice openvpn[844]: OpenVPN 2.4.4 arm-unknown-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] built on Feb 17 2018
Jan 1 00:00:15 DD-WRT daemon.notice openvpn[844]: library versions: OpenSSL 1.1.0g 2 Nov 2017, LZO 2.09
Jan 1 00:00:15 DD-WRT daemon.notice openvpn[931]: MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:16

Jan 1 00:00:15 DD-WRT daemon.warn openvpn[931]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Jan 1 00:00:15 DD-WRT user.info : dnsmasq : dnsmasq daemon successfully stopped
Jan 1 00:00:15 DD-WRT user.info : dnsmasq : dnsmasq daemon successfully started
Jan 1 00:00:16 DD-WRT user.info : vpn modules : vpn modules successfully unloaded
Jan 1 00:00:16 DD-WRT user.info : httpd server started at port 80
Jan 1 00:00:16 DD-WRT user.info : process_monitor successfully started
Jan 1 00:00:16 DD-WRT user.info : wland : WLAN daemon successfully stopped
Jan 1 00:00:16 DD-WRT user.info : wland : WLAN daemon successfully started
Jan 1 00:00:16 DD-WRT user.info : WAN is up. IP: 73.19.193.181
Jan 1 00:00:16 DD-WRT user.info : openvpn : OpenVPN daemon (Client) successfully stopped
Jan 1 00:00:16 DD-WRT daemon.debug ntpclient[1026]: Connecting to 2.pool.ntp.org [2600:3c00::f03c:91ff:fee0:f8fe] ...
Jan 1 00:00:16 DD-WRT daemon.err ntpclient[1026]: Failed connecting to 2.pool.ntp.org [2600:3c00::f03c:91ff:fee0:f8fe]: Address family not supported by protocol
Jan 1 00:00:16 DD-WRT daemon.debug ntpclient[1026]: Connecting to 212.18.3.19 [212.18.3.19] ...
Feb 22 18:59:02 DD-WRT daemon.info ntpclient[1026]: Time set from 212.18.3.19 [212.18.3.19].
Feb 22 18:59:02 DD-WRT daemon.err process_monitor[1025]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Feb 22 18:59:02 DD-WRT daemon.debug process_monitor[1025]: Restarting cron (time sync change)
Feb 22 18:59:02 DD-WRT user.info : cron : cron daemon successfully stopped
Feb 22 18:59:03 DD-WRT user.info : process_monitor : Process Monitor successfully stopped
Feb 22 18:59:03 DD-WRT user.info : cron : cron daemon successfully started
Feb 22 18:59:03 DD-WRT cron.info cron[1050]: (CRON) STARTUP (fork ok)
Feb 22 18:59:04 DD-WRT daemon.err openvpn[931]: RESOLVE: Cannot resolve host address: atl-a26.ipvanish.com:443 (Try again)
Feb 22 18:59:04 DD-WRT daemon.notice openvpn[931]: Socket Buffers: R=[180224->180224] S=[180224->180224]
Feb 22 18:59:04 DD-WRT daemon.notice openvpn[931]: UDPv4 link local: (not bound)
Feb 22 18:59:04 DD-WRT daemon.notice openvpn[931]: UDPv4 link remote: [AF_INET]205.185.209.28:443

Feb 22 18:59:04 DD-WRT daemon.notice openvpn[931]: SIGTERM[hard,init_instance] received, process exiting
Feb 22 18:59:05 DD-WRT user.info : process_monitor : Process Monitor hanging, send SIGKILL
Feb 22 18:59:05 DD-WRT user.info : process_monitor successfully started
Feb 22 18:59:05 DD-WRT daemon.debug process_monitor[1052]: We need to re-update after 3600 seconds
Feb 22 18:59:05 DD-WRT daemon.info process_monitor[1052]: set timer: 3600 seconds, callback: ntp_main()
Feb 22 18:59:11 DD-WRT user.info : NAS : NAS lan (wl0 interface) successfully started
Feb 22 18:59:11 DD-WRT user.info : NAS : NAS lan (wl1 interface) successfully started
Feb 22 18:59:11 DD-WRT user.info : syslogd : syslog daemon successfully stopped
Feb 22 13:59:11 DD-WRT syslog.info syslogd exiting
Feb 22 13:59:11 DD-WRT syslog.info syslogd started: BusyBox v1.28.0
Feb 22 18:59:11 DD-WRT user.info : httpd : http daemon successfully stopped
Feb 22 18:59:11 DD-WRT user.info : httpd server shutdown
Feb 22 18:59:12 DD-WRT user.info : httpd server started at port 80

I've also noticed that the Time Stamp is 5 hours faster than my actual time zone
and I have it set to New York time
ThirdStarr
DD-WRT Novice


Joined: 22 Feb 2018
Posts: 3

PostPosted: Fri Feb 23, 2018 13:16    Post subject: Reply with quote
Here's what I'm having an issue with, no matter what NTP server, Time Setting, or IP Vanish Server and port I use the time is incorrect by 5 plus hours.

Jan 1 00:00:15 DD-WRT daemon.warn openvpn[847]: WARNING: --keysize is DEPRECATED and will be removed in OpenVPN 2.6
Jan 1 00:00:15 DD-WRT daemon.warn openvpn[847]: WARNING: file '/tmp/openvpncl/credentials' is group or others accessible
Jan 1 00:00:15 DD-WRT daemon.notice openvpn[847]: OpenVPN 2.4.4 arm-unknown-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] built on Feb 17 2018
Jan 1 00:00:15 DD-WRT daemon.notice openvpn[847]: library versions: OpenSSL 1.1.0g 2 Nov 2017, LZO 2.09
Jan 1 00:00:15 DD-WRT daemon.notice openvpn[931]: MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:16
Jan 1 00:00:15 DD-WRT daemon.warn openvpn[931]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Jan 1 00:00:15 DD-WRT user.info : dnsmasq : dnsmasq daemon successfully stopped
Jan 1 00:00:15 DD-WRT user.info : dnsmasq : dnsmasq daemon successfully started
Jan 1 00:00:16 DD-WRT user.info : vpn modules : vpn modules successfully unloaded
Jan 1 00:00:16 DD-WRT user.info : httpd server started at port 80
Jan 1 00:00:16 DD-WRT user.info : process_monitor successfully started
Jan 1 00:00:16 DD-WRT user.info : wland : WLAN daemon successfully stopped
Jan 1 00:00:16 DD-WRT user.info : wland : WLAN daemon successfully started
Jan 1 00:00:16 DD-WRT user.info : WAN is up. IP: 73.19.193.181
Jan 1 00:00:16 DD-WRT user.info : openvpn : OpenVPN daemon (Client) successfully stopped
Jan 1 00:00:16 DD-WRT daemon.debug ntpclient[1026]: Connecting to pool.ntp.org [208.75.89.4] ...
Feb 23 12:48:58 DD-WRT daemon.info ntpclient[1026]: Time set from pool.ntp.org [208.75.89.4].
Feb 23 12:48:58 DD-WRT daemon.err process_monitor[1025]: cyclic NTP Update success (servers pool.ntp.org)
Feb 23 12:48:58 DD-WRT daemon.debug process_monitor[1025]: Restarting cron (time sync change)
Feb 23 12:48:58 DD-WRT user.info : cron : cron daemon successfully stopped
Feb 23 12:48:58 DD-WRT user.info : process_monitor : Process Monitor successfully stopped
Feb 23 12:48:58 DD-WRT user.info : cron : cron daemon successfully started
Feb 23 12:48:58 DD-WRT cron.info cron[1045]: (CRON) STARTUP (fork ok)
Feb 23 12:48:59 DD-WRT daemon.err openvpn[931]: RESOLVE: Cannot resolve host address: atl-a05.ipvanish.com:1194 (Try again)
Feb 23 12:48:59 DD-WRT daemon.notice openvpn[931]: Socket Buffers: R=[180224->180224] S=[180224->180224]
Feb 23 12:48:59 DD-WRT daemon.notice openvpn[931]: UDPv4 link local: (not bound)
Feb 23 12:48:59 DD-WRT daemon.notice openvpn[931]: UDPv4 link remote: [AF_INET]205.185.209.15:1194
Feb 23 12:48:59 DD-WRT daemon.notice openvpn[931]: SIGTERM[hard,init_instance] received, process exiting
Feb 23 12:49:00 DD-WRT user.info : process_monitor : Process Monitor hanging, send SIGKILL
Feb 23 12:49:00 DD-WRT user.info : process_monitor successfully started
Feb 23 12:49:00 DD-WRT daemon.debug process_monitor[1047]: We need to re-update after 3600 seconds
Feb 23 12:49:00 DD-WRT daemon.info process_monitor[1047]: set timer: 3600 seconds, callback: ntp_main()
Feb 23 12:49:07 DD-WRT user.info : NAS : NAS lan (wl0 interface) successfully started
Feb 23 12:49:07 DD-WRT user.info : NAS : NAS lan (wl1 interface) successfully started
Feb 23 12:49:07 DD-WRT user.info : syslogd : syslog daemon successfully stopped
Feb 23 07:49:07 DD-WRT syslog.info syslogd exiting
Feb 23 07:49:07 DD-WRT syslog.info syslogd started: BusyBox v1.28.0
Feb 23 12:49:07 DD-WRT user.info : httpd : http daemon successfully stopped
Feb 23 12:49:07 DD-WRT user.info : httpd server shutdown
Feb 23 12:49:07 DD-WRT user.info : httpd server started at port 80
Feb 23 12:49:07 DD-WRT user.info : resetbutton : resetbutton daemon successfully stopped
Feb 23 12:49:07 DD-WRT user.info : resetbutton : resetbutton daemon successfully started

Any suggestions?
autotech40
DD-WRT Novice


Joined: 08 Feb 2018
Posts: 16

PostPosted: Sat Feb 24, 2018 18:15    Post subject: Reply with quote
I couldnt get policy based routing to work,i used a cidr calculator to get the right ips.but since switching to kong r31575m,router has been rock solid and ipvanish has been up strong for 3 days. I think i will run the ipvanish app on the tv stick when the air mouse gets deleverd,since the vpn app block the remote app i use on my phone. Over all very happy now with router and ipvanish.
SumitJain
DD-WRT Novice


Joined: 14 Apr 2018
Posts: 1

PostPosted: Sat Apr 14, 2018 13:22    Post subject: DNS Server Reply with quote
There is simply a good way to try various DNS servers including the open DNS servers.

Technofizi[/url]
Goto page Previous  1, 2, 3, 4 Display posts from previous:    Page 4 of 4
Post new topic   Reply to topic    DD-WRT Forum Index -> Advanced Networking All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum