Control: tags -1 - newcomer + moreinfo On Sun, Sep 06, 2015 at 14:35:43 +0200, Adnan Hodzic wrote: > I connect to Juniper VPN with "sudo openconnect --juniper vpn-url/linux" > > After link is established, I will not be able to reach any address within the > tunnel. Meaning, established connection will not work. > > Workaround: > > However, if I disconnect from VPN and connect to it again, link will be > successfuly established. After this, I will be able to communicate to > addresses > within the tunnel just fine. […] > -- System Information: > Debian Release: 8.2 > APT prefers stable > APT policy: (600, 'stable'), (500, 'stable-updates'), (300, 'testing'), > (200, 'unstable'), (100, 'experimental') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 4.1.0-1-amd64 (SMP w/4 CPU cores) > Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages openconnect depends on: > ii libc6 2.19-18+deb8u1 > ii libgnutls-deb0-28 3.3.17-1 > ii libopenconnect5 7.06-2+b1 > ii libproxy1v5 0.4.11-4.2 > ii libxml2 2.9.1+dfsg1-5 > ii vpnc-scripts 0.1~git20140806-1
You are running OpenConnect from the unstable release on a stable system. And you are also running the stable version of NetworkManager (0.9.10.0). Can you reproduce when NetworkManager is *not* running at all? Can you try with NetworkManager 1.0.6 in unstable? -- mike
