[Bug 1046154] Re: Can't resolve OpenVPN DNS while using a 3G connection with resolvconf installed

Thomas Hood 1046154 at bugs.launchpad.net
Sat Sep 8 10:34:01 UTC 2012


*** This bug is a duplicate of bug 994575 ***
    https://bugs.launchpad.net/bugs/994575

@iox: Thanks.  It's possible that there are multiple problems on your
system but at least we have found one bug: /etc/ppp/ip-
up.d/000resolvconf was registering the nameserver addresses for your 3G
connection but when NetworkManager establishes the connection only it
should do the registering.  And I am happy to be able to say that the
bug has been fixed in resolvconf 1.67ubuntu2, released by Stéphane
Graber  yesterday.  Please upgrade to this new release of resolvconf and
test again. If resolving still doesn't work properly then we'll do some
more debugging.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1046154

Title:
  Can't resolve OpenVPN DNS while using a 3G connection with resolvconf
  installed

Status in “resolvconf” package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu version: fresh install of Ubuntu 12.04.1 LTS 64 bits (3.2.0-29-generic)
  Resolvconf package version: 1.63ubuntu15

  What I expected to happen: Connect through 3G (bluetooth DUN), connect
  to a OpenVPN and be able to resolve the internal domain names to
  access some servers.

  What happened instead: I can't resolve internal hostnames.

  Additional information: It only breaks when connecting through 3G.
  When connecting through Wifi/Cable it works perfectly.

  Workaround: Uninstalling the package resolvconf seems to solve the
  problem.

  Other users probably affected:
  http://mobilesociety.typepad.com/mobile_life/2012/07/ubuntu-1204-the-
  network-manager-3g-internet-and-vpn.html

  I've looked at other bug reports and tried other solutions:
  * #922578.  Removing "resolvconf" is a workaround that works, but I imagine this is resolvconf bug and there must be a more elegant solution.
  * #994575. This looks related, but I already have the patched version and it didn't help.
  * #924013. I have already checked that my OpenVPN servers are pushing the right information (DNS + DOMAIN) back to the client.

  With resolvconf installed: cat /etc/resolv.conf:
      nameserver 195.81.137.130
      nameserver 195.81.155.194
      nameserver 192.168.163.200
      search dummy.intranet

  With resolvconf uninstalled: cat /etc/resolv.conf
      domain dummy.intranet
      search dummy.intranet
      nameserver 127.0.0.1

  Please tell me if you need any additional information

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1046154/+subscriptions




More information about the foundations-bugs mailing list