Hi Loye, Actually, where multiple routes are concerned, Trent is correct; because the 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. So if you have another device with a real Internet route, that route should always get precedence over the avahi route.
I do have another anecdote about why this behavior is a problem, though: the other week, my wife was complaining loudly to me on IRC that firefox wasn't working and I should come fix it. I prodded around, found that it wasn't just firefox that was failing, all DNS resolution was failing. But she had gotten connected to IRC, so what had changed to make DNS start failing? The answer: DHCP had failed when her lease came up for renewal, so she had lost her IP and default route! So why was she able to connect to IRC? Because she ran her IRC client on a server that was on the local link, and was therefore still able to reach this host even though she had no public IP, making it /seem/ that she was on the Internet. I can only imagine the frustration of a user trying to troubleshoot a problem like this without knowing about this bug! :) -- avahi-autoipd gives me an useless default route https://bugs.launchpad.net/bugs/99489 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
