On Wed, Sep 9, 2015 at 18:17:44 +0200, Adnan Hodzic wrote: > Routing table and MTU remain the same between the reconnects. Only thing > that changes is DNS.
Ok, so NM is kicking in and overwriting the resolv.conf that vpnc-script created. But only the first time for some reason. […] > Having Juniper support with openconnect is the first proper solution on > Linux. Other options are to use a browser, or to use various (third party) > scripts to establish the connection. > > It would be nice to get it working using my current set-up. Which is APT > Pinning with base system on stable with network-manager/openconnect from > testing/unstable. > > Other option is to fully upgrade to unstable and then everything will work > as expected. But, I'm not sure a lot of people want this on their (possibly > production) environments on unstable. Yeah honestly I think this is all a little out of scope. With your set up, if you get it working, great, but if not you're pretty much on your own. > Third option is to backport openconnect 7.x to Jessie, but taking in > consideration all its dependencies, this might be a bit complicated task. No, this might be quite doable. I haven't packaged for backports before, but I think openconnect could work there. As long as installing 7.06 with its new library doesn't break NM and KDE plasma which use libopenconnect.so.3, it should be ok. Can you build git master on stable and use it? If so then a backport should be feasible. -- mike
