Russian localization quality.

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

Fraga

Posts: 3
Joined: Fri Aug 12, 2016 5:55 pm

Post by Fraga » Fri Aug 12, 2016 6:51 pm
Hello.
Right now I am considering buying Viscosity client and the only thing that stops me is Russian localization quality. It is not like I really need it, in fact I prefer English menus, but since Viscosity chooses its interface language based on system preferences, I am forced to use it with Russian localization. And frankly speaking I can't call its quality satisfying to say the least. If you wish I can edit it for you(mistakes correction and selection of more appropriate words or phrases) for free.

Eric

User avatar
Posts: 1146
Joined: Sun Jan 03, 2010 3:27 am

Post by Eric » Mon Aug 15, 2016 11:17 am
Hi Fraga,

Thanks for the offer! If you'd like to help improve the localization please send us an email to https://www.sparklabs.com/support/#contact

If you would like to force the client to English:
Exit Viscosity
Run the following command from Start -> Run or a command prompt - Viscosity.exe SetPref DisplayLanguage en
Then restart Viscosity.

Regards,
Eric
Eric Thorpe
Viscosity Developer

Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs

Fraga

Posts: 3
Joined: Fri Aug 12, 2016 5:55 pm

Post by Fraga » Mon Aug 15, 2016 11:22 pm
Thank you, Eric. I've never knew that it is possible to change interface language in Viscosity with a simple command.

Anyways, now I have encountered a bug that makes further usage of Viscosity impossible for me. ( I've got Jetico firewall installed on my working PC, and if I try to initialize a connection to my VPN server while the firewall is set to "Block all" policy or if it blocks Viscosity in learning mode, VPN client connection hangs . And even worse restarting Viscosity and its service doesn't seem to help, the connection keeps being stuck in the hang state, so I have to reboot Windows in order to fix everything. Below there is a log of how this happens.
Code: Select all
aug 15 15:56:58: State changed to Connecting
aug 15 15:56:58: Viscosity Windows 1.6.4 (1448)
aug 15 15:56:59: Running on Microsoft Windows 7 Professional 
aug 15 15:56:59: Bringing up interface...
aug 15 15:57:00: Checking reachability status of connection...
aug 15 15:57:00: Connection is reachable. Starting connection attempt.
aug 15 15:57:01: - System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Net.Sockets.SocketException: Сделана попытка доступа к сокету методом, запрещенным правами доступа
aug 15 15:57:01:   at System.Net.Sockets.Socket.Listen(Int32 backlog)
aug 15 15:57:01:   at System.Net.Sockets.TcpListener.Start(Int32 backlog)
aug 15 15:57:01:   at 36YCxObcym7pgcjlAekrywubaBD.adRVkd2roZRUGVbc0EWKKdN8kNL()
aug 15 15:57:01:   at ViscosityService.ViscosityDaemon.startOpenVPN(String uniqueID, String openVPNVer, iXN6yK3ztflfD0zdz6MveBXP61U config, StreamReader sr, StreamWriter sw, NamedPipeServerStream pipeServer)
aug 15 15:57:01:   --- End of inner exception stack trace ---
aug 15 15:57:01:   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
aug 15 15:57:01:   at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
aug 15 15:57:01:   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
aug 15 15:57:01:   at TGDJKb39amCPNVurV6jPZ2KHpYd.fcnswsDuakWEqYbZa3rqv0osRUg(Object )

The OpenVPN subsystem could not be started. Please check the following:
- Check for any error messages above this notification.
- Ensure ViscosityService is running.
- Make sure the configuration is valid

aug 15 15:57:06: State changed to Disconnected
aug 15 15:57:10: State changed to Connecting
aug 15 15:57:10: Viscosity Windows 1.6.4 (1448)
aug 15 15:57:10: Running on Microsoft Windows 7 Professional 
aug 15 15:57:10: Bringing up interface...
aug 15 15:57:16: State changed to Disconnecting
Steps to reproduce:
  1. Open Viscosity, set Jetico policy to "Block all"
  2. Click "Connect" in Viscosity connection menu. Wait until the connection state changes to disconnected.
  3. Click "Connect" in Viscosity connection menu again. That's it, now the connection is in the hang state.
Also this sometimes happens if firewall blocks Viscosity during connection process or when it is already connected. I tried legacy driver as well, and it is pretty much the same except that I got weird dhcp errors several times when proper IP address, gateway etc were not assigned to Viscosity virtual adapter. Original OpenVPN client works fine in these conditions, though it is not so ergonomic as Viscosity.

Eric

User avatar
Posts: 1146
Joined: Sun Jan 03, 2010 3:27 am

Post by Eric » Tue Aug 16, 2016 8:15 am
Hi Fraga,

The crash is making out there is no free ports available on the PC. We will look into fixing the crash but please note if you are blocking all ports on the PC, no connection will ever be able to take place.

Regards,
Eric
Eric Thorpe
Viscosity Developer

Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs

Eric

User avatar
Posts: 1146
Joined: Sun Jan 03, 2010 3:27 am

Post by Eric » Tue Aug 16, 2016 8:34 am
Hi Fraga,

We've uploaded a new beta that should resolve this crash and prevent Viscosity hanging, please give it a go and let us know if it resolve the issue - http://sparklabs.com/support/kb/article ... -versions/

Regards,
Eric
Eric Thorpe
Viscosity Developer

Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs

Fraga

Posts: 3
Joined: Fri Aug 12, 2016 5:55 pm

Post by Fraga » Tue Aug 16, 2016 2:27 pm
Eric wrote:
Hi Fraga,

The crash is making out there is no free ports available on the PC. We will look into fixing the crash but please note if you are blocking all ports on the PC, no connection will ever be able to take place.
I understand that I am blocking everything when firewall policy is set to "Block all". I usually use this feature in case of emergency when I need to block all traffic on all interfaces promptly. And when I enable it back I am unable to use VPN anymore, at least until OS reboot, which is why the way Vicosity handles connection in combination with firewall is quite problematic for me.

Eric wrote:
We've uploaded a new beta that should resolve this crash and prevent Viscosity hanging, please give it a go and let us know if it resolve the issue - http://sparklabs.com/support/kb/article ... -versions/
Thank you, I really appreciate the amount of attention you dedicate to this issue. But sadly it is not resolved with the latest update you provided.
Firewall policy is set to "Allow all". I click connect in Viscosity client and it connects as expected.
Code: Select all
aug 16 6:26:14: State changed to Connecting
aug 16 6:26:15: Viscosity Windows 1.6.5 (1453) Beta5
aug 16 6:26:15: Running on Microsoft Windows 7 Professional
aug 16 6:26:15: Bringing up interface...
aug 16 6:26:16: Checking reachability status of connection...
aug 16 6:26:17: Connection is reachable. Starting connection attempt.
aug 16 6:26:17: OpenVPN 2.3.11 Windows-MSVC [SSL (OpenSSL)] [LZO] [PKCS11] [IPv6] built on May 11 2016
aug 16 6:26:17: library versions: OpenSSL 1.0.2h  3 May 2016, LZO 2.09
aug 16 6:26:18: Control Channel Authentication: using 'C:\Program Files\Common Files\Viscosity\OpenVPNConfig\User\1\ta.key' as a OpenVPN static key file
aug 16 6:26:18: UDPv4 link local: [undef]
aug 16 6:26:18: UDPv4 link remote: [AF_INET]*.*.*.*:1194
aug 16 6:26:19: WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1602', remote='link-mtu 1572'
aug 16 6:26:19: WARNING: 'tun-mtu' is used inconsistently, local='tun-mtu 1500', remote='tun-mtu 1470'
aug 16 6:26:19: [server] Peer Connection Initiated with [AF_INET]*.*.*.*:1194
aug 16 6:26:22: do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
aug 16 6:26:22: open_tun, tt->ipv6=0
aug 16 6:26:22: TAP-WIN32 device [Amsterdam3] opened: \\.\Global\{DE3549F7-30AB-4688-9E1A-C2D17ABECEA9}.tap
aug 16 6:26:22: Notified TAP-Windows driver to set a DHCP IP/netmask of 10.8.0.6/255.255.255.252 on interface {DE3549F7-30AB-4688-9E1A-C2D17ABECEA9} [DHCP-serv: 10.8.0.5, lease-time: 31536000]
aug 16 6:26:22: Successful ARP Flush on interface [18] {DE3549F7-30AB-4688-9E1A-C2D17ABECEA9}
aug 16 6:26:27: Initialization Sequence Completed
aug 16 6:26:28: DNS set to Full.
aug 16 6:26:28: State changed to Connected
I click disconnect and the client disconnects.
Code: Select all
aug 16 6:26:46: State changed to Disconnecting
aug 16 6:26:46: State changed to Disconnected
Firewall policy is changed to "Block all" and I click connect in Viscosity. Everything seems fine for now as Viscosity checks connection availability and aborts it immediately.
Code: Select all
aug 16 6:26:58: State changed to Connecting
aug 16 6:26:58: Viscosity Windows 1.6.5 (1453) Beta5
aug 16 6:26:58: Running on Microsoft Windows 7 Professional
aug 16 6:26:58: Bringing up interface...
aug 16 6:26:58: Checking reachability status of connection...
aug 16 6:26:58: Connection is reachable. Starting connection attempt.
aug 16 6:26:59: No free ports available, Aborting.

The OpenVPN subsystem could not be started. Please check the following:
- Check for any error messages above this notification.
- Ensure ViscosityService is running.
- Make sure the configuration is valid

aug 16 6:26:59: State changed to Disconnected
I click connect again and now the connection hangs like I mentioned in my previous post.
Code: Select all
aug 16 6:27:01: State changed to Connecting
aug 16 6:27:01: Viscosity Windows 1.6.5 (1453) Beta5
aug 16 6:27:01: Running on Microsoft Windows 7 Professional
aug 16 6:27:01: Bringing up interface...
Firewall policy is changed to "Allow all" I restarted both Viscosity and its service, I click connect again and connection is still in the hang state.
Code: Select all
aug 16 6:30:01: State changed to Connecting
aug 16 6:30:01: Viscosity Windows 1.6.5 (1453) Beta5
aug 16 6:30:01: Running on Microsoft Windows 7 Professional
aug 16 6:30:01: Bringing up interface...
Update. I also found an interesting detail that can be important to you, after about 5-6 minutes after I restart Viscosity and corresponding service, it turns back to normal and I can connect to VPN again, though DNS resolve doesn't seem to work unless I reset(disable -> enable) my main network interface(not the virtual one). By the way if you need Jetico firewall for debugging purposes you can download it on the official site for free.

Eric

User avatar
Posts: 1146
Joined: Sun Jan 03, 2010 3:27 am

Post by Eric » Tue Aug 16, 2016 3:15 pm
Hi Fraga,

Thanks for the detailed information! I think we've located the reason the hang is occurring, there should be a new beta available in a few hours with a fix.

As for DNS not resolving, this is most likely an issue with the firewall (one we have seen with multiple different firewall and leak protection products). When many security applications like this restore after blocking, they generally leave it up to Windows to restore traffic and services in it's own refresh cycle rather than forcing the restore (i.e., the just unblock and don't inform Windows that traffic is now free to flow). Depending on multiple factors, this can take anywhere between 5 minutes and an hour, which is most likely why you are seeing a delay. Disabling and re-enabling the adapter will force Windows to do this refresh on DHCP/DNS etc which is why it resolves the issue.

Regards,
Eric
Eric Thorpe
Viscosity Developer

Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs
7 posts Page 1 of 1