configuration problem

Got a problem with Viscosity or need help? Ask here!

arbushell

Posts: 3
Joined: Mon Feb 22, 2010 8:50 pm

Post by arbushell » Mon Feb 22, 2010 9:18 pm
Hello
I'm trying Viscosity ( MAC 10.5.8) against an OpenVPN-server on a Dreambox Sat receiver (not the final server) and I'm having a lot of problems. First one is that ca, cert and key values (in config.conf, with required permissions) are not modified after the Save command (Preferences -> Connections -> Dream2 where Dream2 is the name of my connection).
I moved these files from the server to the ../Viscosity/openvpn/1 folder, they are seen and selected but no way to see their names in the config file.Only way was to directly edit manually

Done this here is the result (TCP is used because the server do not replies to UDP messages, server and client are in the same LAN, just for testing):

Mon Feb 22 11:08:07 2010: IMPORTANT: OpenVPN's default port number is now 1194, based on an official port number assignment by IANA. OpenVPN 2.0-beta16 and earlier used 5000 as the default port.
Mon Feb 22 11:08:07 2010: WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Mon Feb 22 11:08:07 2010: WARNING: file 'client1.key' is group or others accessible
Mon Feb 22 11:08:07 2010: Attempting to establish TCP connection with 192.168.2.9:1194
Mon Feb 22 11:08:07 2010: TCP connection established with 192.168.2.9:1194
Mon Feb 22 11:08:07 2010: TCPv4_CLIENT link local: [undef]
Mon Feb 22 11:08:07 2010: TCPv4_CLIENT link remote: 192.168.2.9:1194
Mon Feb 22 11:08:07 2010: TLS Error: reading acknowledgement record from packet
Mon Feb 22 11:08:07 2010: Fatal TLS error (check_tls_errors_co), restarting
Mon Feb 22 11:08:07 2010: SIGUSR1[soft,tls-error] received, process restarting

and here is the config file
#-- Config Auto Generated By Viscosity --#

#viscosity startonopen false
#viscosity dhcp true
#viscosity dnssupport true
#viscosity name Dream2
remote 192.168.2.9 1194
persist-key
tls-client
proto tcp-client
ca ca.crt
dev tun
persist-tun
cert client1.crt
nobind
key client1.key
pull


Thank you for any suggestion
Lucien A.

arbushell

Posts: 3
Joined: Mon Feb 22, 2010 8:50 pm

Post by arbushell » Mon Feb 22, 2010 9:35 pm
Sorry but I just discovered that the configuration file is not a problem because the utility makes copy ( cert.crt and key.key) of the selected files and use them.
Remains the activation problem
Thanks
Lucien A.

arbushell

Posts: 3
Joined: Mon Feb 22, 2010 8:50 pm

Post by arbushell » Wed Feb 24, 2010 3:27 am
Solved
was missing the tls_auth line

James

User avatar
Posts: 2313
Joined: Thu Sep 04, 2008 9:27 pm

Post by James » Thu Feb 25, 2010 12:43 am
Hi Lucien,

Thanks for posting your solution - hopefully it should prove handy for anyone else experiencing a similar issue.

Cheers,
James
Web: https://www.sparklabs.com
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
4 posts Page 1 of 1