I'm having a problem where using openconnect via the command line works fine, and connecting using networkmanager-openconnect doesn't. This is a tunnel-in-tunnel scenario, so there's that weirdness, too. Attached are the `ip route` and `ip addr` output in the working and broken scenario- you'll note the major difference is that the network-manager case (the broken case) is missing two routes which correspond to the two addresses given in X-CSTP-DNS during the connection (adding them manually doesn't fix it) and one of the routes from the other vpn (the 173.36.119.148 route) appears to have been changed. (For these files, tun0 is the first tunnel, created by networkmanager-vpnc, and then tun1 (working case / openconnect command line) and vpn0 (broken case / networkmanager-openconnect) are the tunnel-in-tunnel). Have I done something obviously wrong, here? Thanks! -------------- next part -------------- A non-text attachment was scrubbed... Name: route.after-css-working Type: application/octet-stream Size: 1615 bytes Desc: not available URL: <http://lists.infradead.org/pipermail/openconnect-devel/attachments/20160805/0e7f649d/attachment.obj> -------------- next part -------------- A non-text attachment was scrubbed... Name: route.after-css-broken Type: application/octet-stream Size: 2348 bytes Desc: not available URL: <http://lists.infradead.org/pipermail/openconnect-devel/attachments/20160805/0e7f649d/attachment-0001.obj>
