Skip to content
No traffic through tunnel after 1.7 upgrade
Got a problem with Viscosity or need help? Ask here!
I've used Viscosity for years and this upgrade has been the first major set of problems. I've got two servers, one is openVPN 2.4.1 and that works fine. The other is a Sophos UTM firewall (not sure what it runs under the hood).
The tunnel comes up (after forcing me to reset the password without explanation as to why it lost the old one) but I cannot ping anything at the other end or even the VPN endpoint internal address. In fact I can't even ping the local address allocated by the VPN tunnel to my machine.
OSX 10.12.5 with the local machine firewall disabled.
I need this for work, so I can't do much more testing now... I need to downgrade to Viscosity 1.6 so I can work again. Hopefully some other people can help beta test this new release more thoroughly.
The tunnel comes up (after forcing me to reset the password without explanation as to why it lost the old one) but I cannot ping anything at the other end or even the VPN endpoint internal address. In fact I can't even ping the local address allocated by the VPN tunnel to my machine.
OSX 10.12.5 with the local machine firewall disabled.
Code: Select all
It is odd that utun1 has the same IP on the left and right isn't it? Also, when I take the tunnel down, utun0 never goes away.utun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 2000
inet6 fe80::6b8b:748:9052:dbc7%utun0 prefixlen 64 scopeid 0xb
nd6 options=201<PERFORMNUD,DAD>
utun1: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1500
inet 10.242.2.2 --> 10.242.2.2 netmask 0xffffff00
I need this for work, so I can't do much more testing now... I need to downgrade to Viscosity 1.6 so I can work again. Hopefully some other people can help beta test this new release more thoroughly.
Web: https://www.sparklabs.com
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
Hi ari,
I recommend checking your OpenVPN log when connecting or attempting to connect with both OpenVPN 2.4 and 2.3:
http://www.sparklabs.com/support/kb/art ... envpn-log/
The symptoms you describe do point to a mismatch of compression settings between an older version of OpenVPN on the server and your OpenVPN 2.4 settings. The administrator of the VPN server/device may be able to offer more information regarding the server-side compression settings.
Please be aware that macOS may create its own utun adapters for a variety of reasons (typically iCloud and FaceTime related), and these aren't associated with Viscosity.
Cheers,
James
I recommend checking your OpenVPN log when connecting or attempting to connect with both OpenVPN 2.4 and 2.3:
http://www.sparklabs.com/support/kb/art ... envpn-log/
The symptoms you describe do point to a mismatch of compression settings between an older version of OpenVPN on the server and your OpenVPN 2.4 settings. The administrator of the VPN server/device may be able to offer more information regarding the server-side compression settings.
Please be aware that macOS may create its own utun adapters for a variety of reasons (typically iCloud and FaceTime related), and these aren't associated with Viscosity.
Cheers,
James
Web: https://www.sparklabs.com
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
4 posts
Page 1 of 1