On Sat, 2015-08-01 at 11:52 -0400, Mike Miller wrote: > Control: tags -1 + moreinfo > > On Fri, Jul 31, 2015 at 16:59:00 +0300, Matti Koskimies wrote: > > Debian sid updated network-manager from 1.0.2 to 1.0.4 and after > > that > > openconnect didn't work. I downgraded network-manager to 1.0.2 and > > openconnect > > works again. > > Works for me. Can you define "didn't work"? Doesn't show up in NM? > Shows up but doesn't connect? What versions of all OpenConnect and NM > packages do you have?
"Didn't work" means I couldn't connect to the addresses I expect to connect to using VPN. And almost no network connections worked. 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? -- Matti K -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
