Re: Auto network reconfiguring causes DNS lookup to fail
- To: email@example.com
- Subject: Re: Auto network reconfiguring causes DNS lookup to fail
- From: Joel Roth <firstname.lastname@example.org>
- Date: Tue, 22 Nov 2011 04:52:05 -1000
- Message-id: <20111122145205.GB13857@sprite>
- Reply-to: Joel Roth <email@example.com>
- In-reply-to: <20111113152950.GA29781@sprite>
- References: <20111113152950.GA29781@sprite>
On Sun, Nov 13, 2011 at 05:29:50AM -1000, Joel Roth wrote:
> My laptop's wlan1 interface is connected to a wireless
> router, using wpa_supplicant (via wpa_gui).
> Every few minutes, DNS lookup fails. Output of ifconfig
> shows that eth1 and eth1:avahi interfaces have come up.
> Output of route shows that eth1 entries have been added to
> the routing table.
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use Iface
> 10.255.25.0 * 255.255.255.0 U 0 0 0 wlan1
> link-local * 255.255.0.0 U 0 0 0 eth1
> default 10.255.25.1 0.0.0.0 UG 0 0 0 wlan1
> default * 0.0.0.0 U 1002 0 0 eth1
> I can get connectivity by issuing
> ifconfig eth1 down
> dhclient wlan1
I just discovered that my issuing this command multiple
times causes multiple versions of dhclient to remain
running on my system.
Perhaps it is related to this problem. As of yesterday
(without avahi-daemon and without avahi-apd) I discovered
that I was losing ability to resolve addresses after
a short time. Killing the multiple dhclient processes
seemed to resolve the problem.
Is there any benefit to dhclient remaining running?
Why wouldn't I always want to use the -x flag, telling
dhclient to exit?