Good clarification Tom. I've a few things to add:
- It could be argued that (2) is part of (1) - because it is NM that spawns the DHCP daemon, and so it could be said that it's NM's responsibility to make sure that DHCP doesn't upset the VPN plugin functionality, which incidentally, is also part of NM. - I would like to just point out an oversight in (1B) - what if you were connecting to a LAN with private hostnames resolved by a private DNS server? What you would want there is for the DNS servers to be appended to those that already exist. I currently suffer from scenario (1A) - and as someone has already stated before me, the workaround I am using is to add a "append domain- name-servers 123.456.789.ABC;" line into /etc/dhcp/dhclient.conf - so that whenever the DNS lease is renewed, the IP address 123.456.789.ABC is appended onto the end of whatever it was going to write into /etc/resolv.conf - and so my connection won't break. Ideally, the solution would be for NM to be the sole manager of /etc/resolv.conf - and so it can arbitrate between VPN/PPP and DHCP. I read somewhere that NM 0.7 does away with using the current DHCP daemon.. which may or may not alleviate the problem. Anyone know? Eddie -- VPN connection should alter /etc/resolv.conf https://bugs.launchpad.net/bugs/37239 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
