Trying unsuccessfully connect to vpngate OpenVPN. No problem with OpenVPN gui under windows. But in gargoyle I can not find my mistake.
I'm using freely available VPNgate servers.
.ovpn file:
client
remote 178.252.xx.xx 995
proto tcp
dev tun
ca ca.crt
cert client.crt
key client.key
resolv-retry infinite
nobind
persist-key
persist-tun
verb 3
cipher AES-128-CBC
auth SHA1
;dhcp-option DNS 8.8.8.8
;mute-replay-warnings
;mute 20
Any idea?
OpenVPN client connection problem
Moderator: Moderators
OpenVPN client connection problem
- Attachments
-
- clip2.jpg (146.33 KiB) Viewed 4851 times
-
- clip.jpg (189.62 KiB) Viewed 4851 times
Netgear WNDR3700v1 Gargoyle 1.6.0
Re: OpenVPN client connection problem
I just checked out the files provided by vpngate, and the problem is likely that vpngate embeds the keys and certificates in the openvpn config file, which is not supported by gargoyle -- these need to be separate files.
Look at the code under the <ca> <cert> and <key> headings in the vpngate config file. Remove that code and save as separate files without the headers/footers (e.g. the <ca></ca>). Then upload those files.
Look at the code under the <ca> <cert> and <key> headings in the vpngate config file. Remove that code and save as separate files without the headers/footers (e.g. the <ca></ca>). Then upload those files.
Re: OpenVPN client connection problem
This is what I did if you look on my post above. I have split ovpn file into 4 and uploaded. The keys and certificates are identical. There is something wrong in ovpn file. Could you have a look at my post again?
In total. When I upload individual files service starts but no connection to server. When I try to change setting manually and hit apply. Service does not start at all.
In total. When I upload individual files service starts but no connection to server. When I try to change setting manually and hit apply. Service does not start at all.
Netgear WNDR3700v1 Gargoyle 1.6.0
Re: OpenVPN client connection problem
I will test further. I'm working on some improvements for OpenVPN right now anyway, so I'll see if I can fix this.