At IYCC, we've seen this problem over and over again, both on IYCC
computers and on Ubuntu computers of our customers . We've concluded
that avahi is a broken implementation of a bad idea, and the only
thing that seems to work reliably is to get it off the machine.
Here's the best solution:
# apt
>he avahi default route has a very high metric set, this route will only
>ever be used by the kernel when there are no other routes available.
That's not the behavior we're seeing on Hardy fresh installs. According to
RFC 1122, multiple default routes *must* be supported, but in practice
that's ho
On Sun, May 25, 2008 at 11:45:19PM -, Trent Lloyd wrote:
> Anything that is broken by this is inherently broken, not the Avahi
> setup - and -they- should be fixed.
Er, no, that's nonsense. Applications that generate network traffic have to
wait for network timeouts as a result of this avahi
