The "use this connection" change really shouldn't be affecting much.
I can confirm this on n-m-vpnc as well; though it's unclear there yet whether the extra domains (in split-domain config on my Cisco ASA) are actually supported by vpnc. I'm adding a task to get this fixed. Fixing this in openvpn should be feasible and probably simpler, since it probably just relies on the fact that the server misuses the domain field to pass more than one search domain. I don't know how the openconnect plugin deals with it. Please, if you're getting this bug, we need to know more about what's going on and whether the extra domains are seen at all by the underlying application that deals with the vpn connection. That means we'll need debugging logs from the vpn service in use: See http://live.gnome.org/NetworkManager/Debugging, scroll towards the end to the VPN plugin you use and attach the logs for it, after making sure they don't include sensitive data (be extra careful about passwords and such) ** Also affects: network-manager-vpnc (Ubuntu) Importance: Undecided Status: New ** Changed in: network-manager-vpnc (Ubuntu) Status: New => Confirmed ** Changed in: network-manager-openvpn (Ubuntu) Importance: Undecided => Low ** Changed in: network-manager-vpnc (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/924013 Title: VPN DNS only works for IP, not names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openconnect/+bug/924013/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
