On Wed, 2015-08-05 at 16:19 +0300, Matti Koskimies wrote: > Connecting using the GUI still doesn't work, although I get a lot > further now. Connecting and authentication works, and everything looks > OK in NM. The routing table looks similar to the one I get using my > workaround. But there's no networking unless I set the setting "Use > this connection only for resources on its network" under "Routes" in > "IPv4 Settings", but then I can connect only to the same networks as > without the VPN.
OK, so connecting *does* work but your routes are still not right. The oddly named 'Use this connection only for resources on its network' option basically means "Do not set the default route". But you *want* the default route, so you shouldn't be setting that. Let's take a look at what's happening without that option set. You say that the routing table looks similar to the one you get using your workaround — which is promising. But you have "no networking". Which is ambiguous. Can you reach hosts on the VPN if you ping them by their IP address? Is it only DNS that isn't working? Can you show the full output of connecting manually with openconnect with '-v' added to the command line so we can see the routes and DNS it's supposed to be setting up? What do you have in /etc/resolv.conf when you've connected with NetworkManager? -- dwmw2
smime.p7s
Description: S/MIME cryptographic signature
