Hi bubi54,

Sorry for not replying, yes we have and they have been included in 1.8.5.1.

Regards,
Eric

Hi Altern 8, As of version 1.8.5, Viscosity no longer uses 127.0.0.1. As a first step, please have all connections disconnected and ensure this IP is not set on any adapters anymore. We'd recommend resetting your network settings, to do this, right click Start, select Network Connections and the Net...

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 d...

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 cl...

Hi bubi54,

I'm afraid we can't include them in the update just gone but we can certainly include them in future updates.

Regards,
Eric

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 legiti...

Hi nsumner,

We have a solution for this in 1.8.5, and the solution is already in the beta branch if you would like to give it a try. We don't have a firm release date for 1.8.5 at this stage.

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

Regards,
Eric

Hi MikeSK,

Could you please open a Command Prompt and send us the output of the following two commands? Type each one in then press Enter:

ipconfig -all
route print

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

Regards,
Eric

Hi MikeSK,

Thanks for sending that. I think we've found the problem and implemented a fix. Could you please try updating to 1.8.5 Beta 8 and let us know if the problem is still present?

Regards,
Eric

Hi Andrew,

If a dropout/modem reboot lasts for that long, you are probably better off letting Viscosity handle the dropout in this case.

Regards,
Eric