[Bug 994227] Re: resolvconf breaks name resolution

Egor 994227 at bugs.launchpad.net
Fri May 4 07:04:35 UTC 2012


I use madwimax to connect that modem, I do not use ifup/ifdown at all.
Both ifup and ifdown respond smth like «ignoring unknown device wimax0».
When I'm done with my wimax network, I just unplug the modem from the
usb port without manual invocation of any command.

There is no dhclient for wimax in the process list.
However there are lots of dhclients for wlan0, I'm surprised:

# ps aux|grep dhcl
root       461  0.0  0.0   7256   672 ?        Ss   May03   0:00 /sbin/dhclient -v wlan0
root      1037  0.0  0.0   7256  1076 ?        Ss   00:25   0:00 dhclient wlan0
root      1917  0.0  0.0   7256  1080 ?        Ss   00:26   0:00 dhclient wlan0
root      2896  0.0  0.0   7256  1080 ?        Ss   00:28   0:00 dhclient wlan0
root      3125  0.0  0.0   7256   612 ?        Ss   09:14   0:00 /sbin/dhclient -v wlan0
root      5662  0.0  0.0   7256  1076 ?        Ss   00:31   0:00 /sbin/dhclient -v wlan0
root      5844  0.0  0.0   7256  1076 ?        Ss   00:31   0:00 dhclient wlan0
root      6000  0.0  0.0   7256  1076 ?        Ss   00:31   0:00 dhclient wlan0
root      8735  0.0  0.0   7256   672 ?        Ss   Apr29   0:02 /sbin/dhclient -v wlan0
root      9921  0.0  0.0   7256   672 ?        Ss   Apr29   0:02 /sbin/dhclient -v wlan0
root     10393  0.0  0.0   7256   660 ?        Ss   Apr29   0:02 /sbin/dhclient -v wlan0
root     12605  0.0  0.0   9344   928 pts/8    S+   11:02   0:00 grep --color=auto dhcl
root     13280  0.0  0.0   7256   616 ?        Ss   09:26   0:00 dhclient wlan0
root     14263  0.0  0.0   7256  1076 ?        Ss   00:43   0:00 dhclient wlan0
root     17101  0.0  0.0   7256  1076 ?        Ss   May03   0:00 /sbin/dhclient -v wlan0
root     17651  0.0  0.0   7256  1080 ?        Ss   May03   0:00 dhclient wlan0
root     23960  0.0  0.0   7256  1080 ?        Ss   00:13   0:00 /sbin/dhclient -v wlan0
root     24726  0.0  0.0   7256  1072 ?        Ss   00:58   0:00 /sbin/dhclient -v wlan0
root     25175  0.0  0.0   7256  1080 ?        Ss   00:58   0:00 dhclient wlan0
root     26028  0.0  0.0   7256  1080 ?        Ss   00:15   0:00 dhclient wlan0
root     27123  0.0  0.0   7256   276 ?        Ss   Apr30   0:02 /sbin/dhclient -v wlan0
root     30309  0.0  0.0   7256  1072 ?        Ss   07:37   0:00 /sbin/dhclient -v wlan0
root     32204  0.0  0.0   7256  1080 ?        Ss   00:24   0:00 dhclient wlan0

And again now wlan0.dhclient has disappeared, while wimax0.dhclient is
present…

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

Title:
  resolvconf breaks name resolution

Status in “resolvconf” package in Ubuntu:
  Incomplete

Bug description:
  While resolvconf daemon is running, I cannot use the network, because
  my resolv.conf file is filled with invalid nameservers soon after
  connection:

  ========================== bash session: ==========================
  # service resolvconf status
  resolvconf start/running
  # file /etc/resolv.conf
  /etc/resolv.conf: symbolic link to `../run/resolvconf/resolv.conf'
  # export LC_ALL=C;\
    date;\
    dhclient wlan0;\
    cat /etc/resolv.conf;\
    date;\
    inotifywait /etc/resolv.conf;\
    date;\
    cat /etc/resolv.conf
  Fri May  4 00:50:48 MSK 2012
  Rather than invoking init scripts through /etc/init.d, use the service(8)
  utility, e.g. service smbd reload

  Since the script you are attempting to invoke has been converted to an
  Upstart job, you may also use the reload(8) utility, e.g. reload smbd
  RTNETLINK answers: File exists
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  #     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  nameserver 192.168.129.129
  nameserver 8.8.8.8
  nameserver 94.25.128.74
  Fri May  4 00:50:50 MSK 2012
  Setting up watches.
  Watches established.
  /etc/resolv.conf OPEN
  Fri May  4 00:52:44 MSK 2012
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  #     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  nameserver 94.25.128.74
  nameserver 94.25.208.74

  =============================================================================

  To clarify servers:
  192.168.129.129 is my ISP DNS
  8.8.8.8 backup server configured in my router
  94.25.128.74… what's that?

  # egrep -nR '94.25.(12|20)8.74' /etc/*
  /etc/resolv.conf:3:nameserver 94.25.128.74
  /etc/resolv.conf:4:nameserver 94.25.208.74

  So these last two servers cannot be found in the configs, but somehow
  appear in resolv.conf. They are not delivered by dhclient either. I
  guess they may be root DNSes for my ISP (according to whois info), but
  I'm unable to surf the Internet with their help.

  The delay until resolv.conf gets corrupted is not constant at all, sometimes it's as small as 3 seconds. one time is was 13 seconds.
  If I reconnect and shut down resolvconf, I get a working network without any problems. This behavior seems to be a regression after apt-get upgrade from ubuntu 11.10 and seems to be a blocker to an ordinary user, since the network is effectively unusable.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: resolvconf 1.63ubuntu12
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic x86_64
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  Date: Thu May  3 23:57:11 2012
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: resolvconf
  UpgradeStatus: No upgrade log present (probably fresh install)

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




More information about the foundations-bugs mailing list