On Mon, Aug 03, 2015 at 10:42:25 +0300, Matti Koskimies wrote: > Versions: > network-manager 1.0.4-1 > openconnect: 7.06-2 > > I did a little research and found out that the routing table was > different with different NM versions installed after starting > openconnect. So I found a workaround: > > ip route add default dev tun0 scope link > > After that command all connections work as expected. > > What might be the reason for this?
Ok well if the routing configuration is the problem, then this should likely be reassigned to network-manager. To be sure, can you connect with openconnect on the command-line alone and get a successful connection, and routes set up the way you expect? Does fiddling with the NM VPN configuration dialog options change anything? E.g. any options in the IPv4 routing dialog? Is your VPN configured for split tunneling? -- mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
