Please provide a link to download 1.8.4

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

sjgibbs65

Posts: 5
Joined: Sat Jan 04, 2020 12:02 pm

Post by sjgibbs65 » Fri Apr 03, 2020 6:40 am
Please provide a link to download 1.8.4, as my update to 1.8.5 has resulted in a DNS setting of 127.56.49.53 being overwritten into my wifi adapter setting and completely breaking all my connectivity.

sdg233

Posts: 1
Joined: Fri Apr 03, 2020 7:32 am

Post by sdg233 » Fri Apr 03, 2020 7:35 am
I am in the same boat. When I connect to my OpenVPN server it breaks split tunneling, but if i reinstall 1.8.4 it works again.

Eric

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

Post by Eric » Fri Apr 03, 2020 12:55 pm
Hi sdg233 and sjgibbs65,

We have intentionally used this different loopback address from this update forwards to allow us to better control teardown of DNS, as some users were having 127.0.0.1 get stuck, and unfortunately we couldn't forcefully remove it as that address is used for some other legitimate applications other than Viscosity.

We would highly appreciate you working with us to see if we can find out what is going on and fix the issue you're facing with 1.8.5. Are you able to please post a copy of your log after connecting - https://sparklabs.com/support/kb/articl ... envpn-log/

Could you also please open a command prompt and post a copy of the output from the following commands:
ipconfig -all
route print
nslookup sparklabs.com.

You may wish to email this to us instead as this is a public forum - https://www.sparklabs.com/support/#contact

Regards,
Eric
Eric Thorpe
Viscosity Developer

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

sjgibbs65

Posts: 5
Joined: Sat Jan 04, 2020 12:02 pm

Post by sjgibbs65 » Sat Apr 04, 2020 2:14 am
I made a simple request for SparkLabs to provide me with a download link for the prior v1.8.4, since I could not find a way to download it off of your website. I made this request because your update broke my connectivity and prevented me from working at home yesterday.
Yet, no download link was provided to me. How is that supportive?
While I can understand your desire to figure out what is happening with your software, your first imperative should always be to keep your paying customers connected. I made a simple request to that end and was not supported.
I am very unhappy.
My peers at work are pressuring me to switch to OpenVPN. If I cannot run Viscosity today, I will have no choice but to abandon it.

rcqa

Posts: 2
Joined: Sat Apr 04, 2020 4:50 am

Post by rcqa » Sat Apr 04, 2020 4:55 am
I am seeing the same issue as well. Viscosity is updating my WiFi IPV4 DNS routing to 127.56.49.53 and killing my internet capabilities.

I cannot do my job without my VPN connections, and I cannot do my job without DNS routing set to "Obtain DNS server address automatically". I need to be able to revert Viscosity today.

tfugie

Posts: 1
Joined: Sat Apr 04, 2020 5:42 am

Post by tfugie » Sat Apr 04, 2020 5:53 am
Hello I am also in the same situation. We have Cisco umbrella service which uses the 127.0.0.1 and it will reset both the vpn adapter and real NIC's DNS to that so after the users connect they loose basic DNS function. We are going to need a fix for this or a link to the older version so our users can operate. We have it deployed across a couple customer organizations and this was a major issue yesterday.

Eric

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

Post by Eric » Sat Apr 04, 2020 7:11 pm
Hi Everyone,

Thank you to those who posted here as well as those that emailed us and pointed us in the direction of the Cisco/OpenDNS Umbrella client. We've done some testing and identified there is a compatibility problem running both Viscosity and Umbrella as well as some other DNS-Crypt or DoH clients on the same machine.

Up to Viscosity 1.8.4, as Umbrella and Viscosity were both using the same loopback IP Address (127.0.0.1 and ::1) for their resolvers, this meant to users there didn't appear to be any problems. Unfortunately, what was happening is while Viscosity was connected to a VPN, some of your DNS requests were being handled by Viscosity, and some of your DNS requests were being handled by Umbrella. There was no guarantee that all your requests would go through one resolver or the other while connected to a VPN.

In 1.8.5, we switched our local DNS addresses to 127.56.49.53 and fd53:7061:726b:4c61:6273:5669:7344:4e53 to address several issues, namely that we were implementing work-arounds on most releases for new issues from drivers or other applications that were causing loopback IP addresses to remain after disconnecting from a VPN connection or the PC recovering after a crash/bluescreen. It looks like from some testing Umbrella or other dns-crypt clients may have been causing some of these as well.

Unfortunately, changing to these new IP addresses meant that once Viscosity connects, Umbrella and some other dns-crypt clients start fighting for control over DNS and IP settings, effectively making it appear as if the user has no connectivity on the machine anymore once connected as DNS no longer works.

We're currently implementing a work around to have Viscosity and Umbrella co-exist on the same machine. In the mean time, a work around would be to use Umbrella for all DNS queries while connected to a VPN, this may be what some users preferred anyway but wasn't happening all the time with previous versions.

To do this on the client, edit the connection, go to Networking, and set the DNS Mode to Full DNS. Save the connection, go to Preferences -> Advanced, and tick Use Windows DNS System for Full DNS.

Alternatively, you can push this to clients from the server by adding the following to your VPN Server configuration. The following should not cause other OpenVPN clients issues other than displaying an unknown option warning in the log:

push "dhcp-option DNSMODE simultaneous"

It's also worth noting that your DNS may be in a bit of a stuck state if you have tried to connect and disconnect, restarting your PC should clear this up.

We will let everyone know once we have a work around implemented and uploaded to our beta stream, as well as release an update to as soon as we can.

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: 973
Joined: Sun Jan 03, 2010 3:27 am

Post by Eric » Sun Apr 05, 2020 12:29 am
Hi Everyone,

We have uploaded Viscosity 1.8.5.1 Beta1 to the beta stream. We have implemented a work around where the Umbrella Roaming Client will be disabled when Viscosity connects and requires it's own DNS Proxy for normal operation, and will re-enable the Umbrella Roaming Client when Viscosity disconnects. The Umbrella client will not be disabled if it is not required, for example if DNS is set to Simultaneous or Off.

We've made this configurable as well if you would like to implement your own management of the Umbrella Roaming Client, with an option in Preferences -> Advanced to disable this behaviour.

Please give this beta a try and let us know if you have any feedback at all.

https://sparklabs.com/support/kb/articl ... -versions/

Regards,
Eric
Eric Thorpe
Viscosity Developer

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

rcqa

Posts: 2
Joined: Sat Apr 04, 2020 4:50 am

Post by rcqa » Tue Apr 07, 2020 2:22 am
FYI - the 1.8.5.1 update did not resolve my issue, but the workaround, using full DNS settings, did.

sjgibbs65

Posts: 5
Joined: Sat Jan 04, 2020 12:02 pm

Post by sjgibbs65 » Sun Apr 12, 2020 3:17 am
So I have yet to be provided with the download link to 1.8.4 that I requested. Until I receive that, I will not try any other solution, for fear of breaking my connectivity. I found a 1.8 version on one of my personal PCs, so I am now using that on my work PC. I keep getting the nag to update to 1.8.5 and I don't want to turn off that check for the risk of missing when 1.8.6 gets released.

Why is SparkLabs so stingy and anal about providing a download page that includes prior releases? I routinely see this option from other software companies. The forums here are scattered with these types of prior release requests and I have yet to see the subject properly addressed. Why?
10 posts Page 1 of 1