[Bug 994575] Re: /etc/ppp/ip-up.d/000resolvconf should "exit 0" if pppd was run by NM, since NM will register the nameserver addresses itself

Ubuntu Foundation's Bug Bot 994575 at bugs.launchpad.net
Sun Jun 17 20:20:36 UTC 2012


The attachment "Patch to fix resolvconf's pppd hook scripts such that
they don't call resolvconf if pppd was called by nm-pptp-service" of
this bug report has been identified as being a patch.  The ubuntu-
reviewers team has been subscribed to the bug report so that they can
review the patch.  In the event that this is in fact not a patch you can
resolve this situation by removing the tag 'patch' from the bug report
and editing the attachment so that it is not flagged as a patch.
Additionally, if you are member of the ubuntu-reviewers team please also
unsubscribe the team from this bug report.

[This is an automated message performed by a Launchpad user owned by
Brian Murray.  Please contact him regarding any issues with the action
taken in this bug report.]

** Tags added: patch

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

Title:
  /etc/ppp/ip-up.d/000resolvconf should "exit 0" if pppd was run by NM,
  since NM will register the nameserver addresses itself

Status in “resolvconf” package in Ubuntu:
  In Progress

Bug description:
  I have a VPN set up in Network Manager, which worked well when my
  system was running 11.10.

  After upgrading to 12.04, I've noticed that DNS changes needed by the
  VPN aren't happening.  Hosts that only resolve within the VPN won't
  resolve, and hosts that are supposed to resolve with different IP
  addresses inside the VPN don't.

  I can see the new, proper nameserver configuration in /var/run/nm-dns-
  dnsmasq.conf.  I can resolve properly if I query the name server
  directly, i.e. "host <name-to-resolve> <vpn-dns-server-ip>".  And, if
  I use that IP address instead of the name, I can successfully do
  things like ssh.  But simple resolution appears to still be using the
  old name server.

  At one point, I killed off dnsmasq and wrote a new /etc/resolv.conf
  with the VPN name servers.  That worked, but caused all manner of
  problems later.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: network-manager 0.9.4.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic x86_64
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  Date: Fri May  4 09:04:23 2012
  EcryptfsInUse: Yes
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  IpRoute:
   default via 192.168.50.2 dev eth0  proto static 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.50.0/24 dev eth0  proto kernel  scope link  src 192.168.50.222  metric 1 
   192.168.50.0/24 dev wlan0  proto kernel  scope link  src 192.168.50.106  metric 2
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RfKill:
   0: phy0: Wireless LAN
   	Soft blocked: no
   	Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to precise on 2012-05-02 (1 days ago)
  nmcli-dev:
   DEVICE     TYPE              STATE         DBUS-PATH                                  
   eth0       802-3-ethernet    connected     /org/freedesktop/NetworkManager/Devices/1  
   wlan0      802-11-wireless   connected     /org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING         VERSION    STATE           NET-ENABLED   WIFI-HARDWARE   WIFI       WWAN-HARDWARE   WWAN      
   running         0.9.4.0    connected       enabled       enabled         enabled    enabled         disabled

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




More information about the foundations-bugs mailing list