OK, I finally got the Connect client working on Debian Stretch. (64-bit, if it matters). CLI still broken (exits after I enter my password) but at least the GUI works. Install client version 5.3R4 Run the following script to launch the UI: LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/lib/x86_64-linux-gnu:/usr/local/pulse /usr/local/pulse/pulseUi Make the connection profile and start it up Bring the tun0 interface down and then up again: sudo ip link set tun0 down; sudo ip link set tun0 up Wait approximately 60 seconds And after all that, you should be able to route traffic through the VPN.   (ETA: I've only found the tun0 down/up trick necessary when using a split VPN configuration; when I use my employer's no-split configuration, it works right away. However, it also doesn't seem to clean up after itself as often.) ... View more

I've been using version 8.1r8.0 for a while now (since the next version up had a buggy installer) but when I upgraded Debian, it stopped working -- after connecting to the VPN, I couldn't even ping anything, let alone resolve DNS or browse the intranet.   Things I've tried:   - Modifying the 8.2r5.0 installer to pretend I'm using Ubuntu - Using the 5.2r9.1 installer (did the version number go down when I wasn't looking?), again hacked to accommodate Debian (bypass dependency checking) - Installed libwebkitgtk-1.0-0 and libwebkitgtk-1.0-0:i386 and messed around with LD_LIBRARY_PATH - Tried to enable logging (-L 5, but I can't actually find any logs) - Looked at `netstat -nr` output (yes, there's the tun0 device) - Looked at iptables to make sure there weren't any weird rules - Tried to download a newer version, but the packages aren't actually provided anywhere public   I'm pretty frustrated at this point. What can I even try next? ... View more