Ok finally I got my VPN issue to move 1 step. My Vonage Adapter was causing port to be blocked I think. Now Amahi dashboard shows my VPN as active. This morning I tried HDA connect from my work and I get following any ideas ?
Fri Jul 23 07:45:57 2010 OpenVPN 2.1_rc15 i686-pc-mingw32 [SSL] [LZO2] [PKCS11] built on Nov 19 2008
Fri Jul 23 07:45:57 2010 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Fri Jul 23 07:45:57 2010 NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Fri Jul 23 07:45:58 2010 LZO compression initialized
Fri Jul 23 07:45:58 2010 Control Channel MTU parms [ L:1542 D:138 EF:38 EB:0 ET:0 EL:0 ]
Fri Jul 23 07:45:58 2010 Data Channel MTU parms [ L:1542 D:1450 EF:42 EB:135 ET:0 EL:0 AF:3/1 ]
Fri Jul 23 07:45:58 2010 Local Options hash (VER=V4): '41690919'
Fri Jul 23 07:45:58 2010 Expected Remote Options hash (VER=V4): '530fdded'
Fri Jul 23 07:45:58 2010 Socket Buffers: R=[8192->8192] S=[8192->8192]
Fri Jul 23 07:45:58 2010 UDPv4 link local: [undef]
Fri Jul 23 07:45:58 2010 UDPv4 link remote: **.***.***.**:1194
Fri Jul 23 07:46:58 2010 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Fri Jul 23 07:46:58 2010 TLS Error: TLS handshake failed
Fri Jul 23 07:46:58 2010 TCP/UDP: Closing socket
Fri Jul 23 07:46:58 2010 SIGUSR1[soft,tls-error] received, process restarting
Fri Jul 23 07:46:58 2010 Restart pause, 2 second(s)
Fri Jul 23 07:47:00 2010 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Fri Jul 23 07:47:00 2010 NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Fri Jul 23 07:47:00 2010 Re-using SSL/TLS context
Fri Jul 23 07:47:00 2010 LZO compression initialized
Fri Jul 23 07:47:00 2010 Control Channel MTU parms [ L:1542 D:138 EF:38 EB:0 ET:0 EL:0 ]
Fri Jul 23 07:47:00 2010 Data Channel MTU parms [ L:1542 D:1450 EF:42 EB:135 ET:0 EL:0 AF:3/1 ]
Fri Jul 23 07:47:00 2010 Local Options hash (VER=V4): '41690919'
Fri Jul 23 07:47:00 2010 Expected Remote Options hash (VER=V4): '530fdded'
Fri Jul 23 07:47:00 2010 Socket Buffers: R=[8192->8192] S=[8192->8192]
Fri Jul 23 07:47:00 2010 UDPv4 link local: [undef]
Fri Jul 23 07:47:00 2010 UDPv4 link remote: **.***.***.**:1194
Fri Jul 23 07:47:41 2010 TCP/UDP: Closing socket
Fri Jul 23 07:47:41 2010 SIGTERM[hard,] received, process exiting
VPN Active but didn't connect
-
- Posts: 59
- Joined: Tue May 25, 2010 8:42 am
- Location: USA
Re: VPN Active but didn't connect
Looks like a failure to connect.
Maybe you work is blocking this type of traffic. Wouldn't be uncommon.
I tried to connect to your VPN, and it worked fine for me (except it didn't let me in because of my invalid username / password).
Maybe you work is blocking this type of traffic. Wouldn't be uncommon.
I tried to connect to your VPN, and it worked fine for me (except it didn't let me in because of my invalid username / password).
Code: Select all
Fri Jul 23 11:20:45 2010 OpenVPN 2.1_rc15 i686-pc-mingw32 [SSL] [LZO2] [PKCS11] built on Nov 19 2008
Fri Jul 23 11:20:45 2010 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Fri Jul 23 11:20:45 2010 NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Fri Jul 23 11:20:46 2010 LZO compression initialized
Fri Jul 23 11:20:46 2010 Control Channel MTU parms [ L:1542 D:138 EF:38 EB:0 ET:0 EL:0 ]
Fri Jul 23 11:20:46 2010 Data Channel MTU parms [ L:1542 D:1450 EF:42 EB:135 ET:0 EL:0 AF:3/1 ]
Fri Jul 23 11:20:46 2010 Local Options hash (VER=V4): '41690919'
Fri Jul 23 11:20:46 2010 Expected Remote Options hash (VER=V4): '530fdded'
Fri Jul 23 11:20:46 2010 Socket Buffers: R=[8192->8192] S=[8192->8192]
Fri Jul 23 11:20:46 2010 UDPv4 link local: [undef]
Fri Jul 23 11:20:46 2010 UDPv4 link remote: **.***.***.**:1194
Fri Jul 23 11:20:46 2010 TLS: Initial packet from **.***.***.**:1194, sid=4adfe860 59f6ebd5
Fri Jul 23 11:20:46 2010 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Fri Jul 23 11:20:46 2010 VERIFY OK: depth=1, /C=US/ST=CA/L=SanJose/O=HomeHDA/OU=VPN/CN=yourhda.com/emailAddress=info@homehda.com
Fri Jul 23 11:20:46 2010 VERIFY OK: depth=0, /C=US/ST=CA/L=SanJose/O=HomeHDA/OU=VPN/CN=server/emailAddress=info@homehda.com
Fri Jul 23 11:20:49 2010 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
Fri Jul 23 11:20:49 2010 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Fri Jul 23 11:20:49 2010 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
Fri Jul 23 11:20:49 2010 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Fri Jul 23 11:20:49 2010 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA
Fri Jul 23 11:20:49 2010 [server] Peer Connection Initiated with **.***.***.**:1194
Fri Jul 23 11:20:50 2010 SENT CONTROL [server]: 'PUSH_REQUEST' (status=1)
Fri Jul 23 11:20:50 2010 AUTH: Received AUTH_FAILED control message
Fri Jul 23 11:20:50 2010 TCP/UDP: Closing socket
Fri Jul 23 11:20:50 2010 SIGTERM[soft,auth-failure] received, process exiting
Fri Jul 23 11:20:56 2010 OpenVPN 2.1_rc15 i686-pc-mingw32 [SSL] [LZO2] [PKCS11] built on Nov 19 2008
Fri Jul 23 11:20:56 2010 ERROR: Exit Event ('openvpngui_exit_event_0') is signaled
Fri Jul 23 11:20:56 2010 Exiting
- Guillaume Boudreau
-
- Posts: 59
- Joined: Tue May 25, 2010 8:42 am
- Location: USA
Re: VPN Active but didn't connect
darn....thanks for checking Bro.
Is there way to bypass that from work ? any workaround ?
Is there way to bypass that from work ? any workaround ?
Re: VPN Active but didn't connect
Only workaround you could try is to use a non-blocked port.
My guess is you won't be blocked if you try to use TCP port 443.
You'd need to change the OpenVPN config file on your server, and manually edit the HDAConnect config file to use TCP instead of UDP, and connect to remote port 443 instead of 1194.
Then forward public TCP port 443 to internal port 1194 (per your OpenVPN config) on your router.
My guess is you won't be blocked if you try to use TCP port 443.
You'd need to change the OpenVPN config file on your server, and manually edit the HDAConnect config file to use TCP instead of UDP, and connect to remote port 443 instead of 1194.
Then forward public TCP port 443 to internal port 1194 (per your OpenVPN config) on your router.
- Guillaume Boudreau
-
- Posts: 59
- Joined: Tue May 25, 2010 8:42 am
- Location: USA
Re: VPN Active but didn't connect
Can anyone give me directions on how to edit config file on server side ? I will try to use this method to see if I can logon to my VPN at work. Thanks
-
- Posts: 59
- Joined: Tue May 25, 2010 8:42 am
- Location: USA
Re: VPN Active but didn't connect
can anyone help me out on how to edit my VPN config files on server so that I can VPN from work. thanks
Re: VPN Active but didn't connect
You'll have to login as root (type su in terminal) and follow these :
and save the file, then restart the server.

Code: Select all
cd /
cd etc
cd openvpn
gedit amahi.conf

Who is online
Users browsing this forum: No registered users and 10 guests