OpenVPN with my Router Problem

Zerkelele

Hello,
I was trying to get a VPN with my router. So I did everything that was listed here: http://www.asus.com/support/Knowledge-Detail/11/2/RTAC68U/1A935B95-C237-4281-AE86-C824737D11F9/

But I can't seem to fix this problem.

When I login to OpenVPN, it shows that it is Reconnecting as you can see here:
https://gyazo.com/bbdd55ff28833038267a2ab16307d2d2

When I try to connect to OpenVPN with the login information I got from here: https://gyazo.com/78fbba1044985c0933c312ec90789f07
(i also made a VPN Client with the same login and password

I get this in the OpenVPN client:

Sun Mar 13 22:01:05 2016 OpenVPN 2.3.10 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [PKCS11] [IPv6] built on Feb 1 2016
Sun Mar 13 22:01:05 2016 Windows version 6.2 (Windows 8 or greater)
Sun Mar 13 22:01:05 2016 library versions: OpenSSL 1.0.1r 28 Jan 2016, LZO 2.09
Sun Mar 13 22:01:08 2016 UDPv4 link local: [undef]
Sun Mar 13 22:01:08 2016 UDPv4 link remote: [AF_INET]10.0.0.100:1194
Sun Mar 13 22:02:08 2016 [UNDEF] Inactivity timeout (--ping-restart), restarting
Sun Mar 13 22:02:08 2016 SIGUSR1[soft,ping-restart] received, process restarting
Sun Mar 13 22:02:10 2016 UDPv4 link local: [undef]
Sun Mar 13 22:02:10 2016 UDPv4 link remote: [AF_INET]10.0.0.100:1194
Sun Mar 13 22:03:10 2016 [UNDEF] Inactivity timeout (--ping-restart), restarting
Sun Mar 13 22:03:10 2016 SIGUSR1[soft,ping-restart] received, process restarting
Sun Mar 13 22:03:12 2016 UDPv4 link local: [undef]
Sun Mar 13 22:03:12 2016 UDPv4 link remote: [AF_INET]10.0.0.100:1194
Sun Mar 13 22:04:12 2016 [UNDEF] Inactivity timeout (--ping-restart), restarting
Sun Mar 13 22:04:12 2016 SIGUSR1[soft,ping-restart] received, process restarting
Sun Mar 13 22:04:14 2016 UDPv4 link local: [undef]
Sun Mar 13 22:04:14 2016 UDPv4 link remote: [AF_INET]10.0.0.100:1194
Sun Mar 13 22:05:14 2016 [UNDEF] Inactivity timeout (--ping-restart), restarting
Sun Mar 13 22:05:14 2016 SIGUSR1[soft,ping-restart] received, process restarting
Sun Mar 13 22:05:16 2016 UDPv4 link local: [undef]
Sun Mar 13 22:05:16 2016 UDPv4 link remote: [AF_INET]10.0.0.100:1194
Sun Mar 13 22:06:16 2016 [UNDEF] Inactivity timeout (--ping-restart), restarting
Sun Mar 13 22:06:16 2016 SIGUSR1[soft,ping-restart] received, process restarting
Sun Mar 13 22:06:18 2016 UDPv4 link local: [undef]
Sun Mar 13 22:06:18 2016 UDPv4 link remote: [AF_INET]10.0.0.100:1194
Sun Mar 13 22:07:18 2016 [UNDEF] Inactivity timeout (--ping-restart), restarting
Sun Mar 13 22:07:18 2016 SIGUSR1[soft,ping-restart] received, process restarting
Sun Mar 13 22:07:20 2016 UDPv4 link local: [undef]
Sun Mar 13 22:07:20 2016 UDPv4 link remote: [AF_INET]10.0.0.100:1194
Sun Mar 13 22:08:20 2016 [UNDEF] Inactivity timeout (--ping-restart), restarting
Sun Mar 13 22:08:20 2016 SIGUSR1[soft,ping-restart] received, process restarting
Sun Mar 13 22:08:22 2016 UDPv4 link local: [undef]
Sun Mar 13 22:08:22 2016 UDPv4 link remote: [AF_INET]10.0.0.100:1194
Sun Mar 13 22:09:22 2016 [UNDEF] Inactivity timeout (--ping-restart), restarting
Sun Mar 13 22:09:22 2016 SIGUSR1[soft,ping-restart] received, process restarting
Sun Mar 13 22:09:24 2016 UDPv4 link local: [undef]
Sun Mar 13 22:09:24 2016 UDPv4 link remote: [AF_INET]10.0.0.100:1194

And it just keeps repeating.

I have also added a VPN Client as seen here:
https://gyazo.com/5abac79766020d315906fac8c71c26d7
https://gyazo.com/87d83e8d41b1ecfe66dd000d56106a7d

Anyone know how I can fix this, and get OpenVPN to work with my Router, thanks.

Im not good at these kind of things, so please, try to help a fellow noob out!

Thanks

Superion

Zerkelele, I'm an absolute newbie at this myself, but from my own recent struggles, I'll try to get you started.

Your messages, like in my case, seem to indicate that your OpenVPN client's communication--its packets--aren't getting through to the server (you don't have the server logs, so I'm just guessing based on your client logs and how it resembled my own issues).

Did you set up port forwarding on what I call your "incoming gateway device"? That would be your modem, connection box, or whatever device is connecting your house to the Internet. We tend to forget that these devices act as rudimentary firewalls themselves, and need to be configured to forward the necessary ports in order for communications to get through.