(SOLVED!) Re: Auto network reconfiguring causes DNS lookup to fail
Summary: purging avahi-daemon appears to have resolved
the issue.
On Sun, Nov 13, 2011 at 11:28:28PM +0000, Brian wrote:
> On Sun 13 Nov 2011 at 12:07:47 -1000, Joel Roth wrote:
>
> > On Sun, Nov 13, 2011 at 05:13:54PM +0000, Brian wrote:
> > > May we see the output of ifconfig and your interfaces file in
> > > /etc/network?
> >
> > auto lo
> > iface lo inet loopback
>
> This isn't the sum total of /etc/network/interfaces, is it? Where is
> wlan0?
Since that advent of udev, I notice that not all network
devices start at 0. For instance, I have only one ethernet
interface, eth1. And only one wireless interface, wlan1.
> > > Do you use avahi for anything?
> >
> > Not that I know of. I never deliberately installed it;
> > it got pulled in during an upgrade.
>
> You could stick with the situation you have now and solve the problem in
> that context, or revert to what was, presumably, a working situation. It
> is highly unlikely you will miss the benefits of avahi. So
>
> apt-get purge avahi-daemon
>
> Does anything complain?
I see it is used for LAN printer discovery. I stopped the
avahi-daemon just now, but I still see that eth1 and
eth1:avahi have popped back into the ifconfig listing.
(I'm not sure if that has anything to do with my connectivity
problem, but I have also noticed that DNS lookups take *much*
longer if the routing table has entries for unconnected
network interfaces.)
Funny, I thought
/etc/init.d/avahi-daemon stop
should be enough to shutdown whatever avahi was doing,
but, ps ax | grep avahi:
28687 ? S 0:00 avahi-autoipd: [eth1] bound 169.254.11.90
28688 ? S 0:00 avahi-autoipd: [eth1] callout dispatcher
28745 ? S 0:00 avahi-autoipd: [wlan1] sleeping
28746 ? S 0:00 avahi-autoipd: [wlan1] callout dispatcher
That goes against the grain of what "stopping" a service
means to me. Perhaps that deserves a bug report.
And having killed these processes. I see they have started
up again.
Having purged avahi, these processes are still starting up. I
guess a reboot is in order.
Having rebooted, my networking is working normally again.
Yay! What a relief. Thanks, Brian!!
--
Joel Roth
Reply to: