Re "if you are using a VPN service for privacy purposes" - I have a contrary use case. I want to use my home router as much as possible, and the VPN (which may be my office network, or more critically a client's network) *only* for traffic required to go there. My understanding was that this was controlled by the checkebox "Use only for resources on this connection" - although, by the sounds of it, that only affects routing of traffic not DNS lookups (it *is* on the Routes.. subdialog)
traceroute to bugs.launchpad.net (91.189.89.225), 30 hops max, 60 byte packets 1 192.168.33.1 1.615 ms 2.487 ms 2.673 ms <== home router 2 .... traceroute to 192.168.68.44 (192.168.68.44), <== a resource on the remote LAN 1 192.168.70.1 7.561 ms 9.173 ms 10.266 ms <== VPN gateway 2 .... I can't check just now whether DNS queries are going where I intend or not - I'll have to reboot to get a working VPN link (Refer to Bug #1644098 <g>) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1644098 Title: Network Manager + OpenVPN does not respond to DNS server change on second connection attempt Status in network-manager package in Ubuntu: Confirmed Bug description: Scenario: Discovered on Kubuntu 16.10, upgraded from a fresh install of 16.04. While I only have the one computer to test with, the 16.10 is definitely relevant (I did not have this problem on 16.04) but I can't tell if the upgrade is part of it, (the upgrade may or may not be relevant). Have "full time" wired or wireless connection (does not matter which used) Part time OpenVPN connection set up via NetworkManager. Steps to reproduce 1. Fresh boot 2. ping a device on the VPN network (eg amachine.remotelan ) Result: "ping: amachine.remotelan: Name or service not known" 3. Connect to the VPN service via Network Manager. 4. ping amachine.remotelan - result: PING amachine.remotelan (192.168.68.44) 56(84) bytes of data. 64 bytes from amachine.remotelan (192.168.68.44): icmp_seq=1 ttl=127 time=7.75 ms 5. Disconnect from the VPN service again. ping result again "ping: amachine.remotelan: Name or service not known" 6. Reconnect to the VPN again, and ping again Observed: "ping: amachine.remotelan: Name or service not known" However "ping 192.168.68.44" responds successfully as expected Expected: PING ... 192.168.... 64 bytes from .. etc to the ping by name --------------- Further info I'm going to add in a subsequent comment. (just annotating syslog right now!) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1644098/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
