← Back to team overview

desktop-packages team mailing list archive

[Bug 898224] Re: Wrong dnsmasq configuration when VPN is set as default gateway

 

No, this won't be backported or SRU'd to earlier releases. If you feel
daring, you may wish to try out Precise Pangolin early, and help with
the testing... see here: http://www.ubuntu.com/testing

Since Alpha 1 is the only milestone released so far, you'll need to make
sure to update to the latest packages too; which may prove to be
complicated for testing without installing on your system (but you can
still install on a virtual machine or so).

-- 
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/898224

Title:
  Wrong dnsmasq configuration when VPN is set as default gateway

Status in “network-manager” package in Ubuntu:
  Fix Released

Bug description:
  When using dnsmasq with Network Manager (DNS=dnsmasq in the config)
  and a VPN that's not configured as "Use VPN only for resources on its
  network" (default configuration), the dnsmasq configuration ends up
  being wrong.

  I'd have expected the default DNS server to be the one received from
  the VPN connection instead of the one from the current wired/wireless
  network as that one isn't reachable.

  So in a setup where VPN doesn't provide the default gateway, DNS should be: 
   - DNS queries for anything on the VPN network => DNS server from VPN
   - Everything elsse => DNS server from current wired/wireless network

  In a setup where the default gateway is the VPN
   - Everything => DNS server from VPN

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/898224/+subscriptions


References