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
avahi-autoipd gives me an IP address which overrides the settings in
Network manager. This mean that after each reboot I have no valid
network connection. I have to restart the network or re-configure
Network manager each time.
syslog fragment:
[code]
Nov 15 17:23:25 vlad-studio avahi-autoipd(ath0
I have a box with two network interfaces: DHCP to WAN and a statically
configured local interface. Avahi-autpid constantly resets default route
to local network so Internet traffic doesn't go anywhere.
Removing avahi fixes this problem for me.
--
avahi-autoipd gives me an useless default route
h
>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
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 shou
Steve is right. Setting up a default route on a link-local interface is
inherently flawed.
The default route is the the "gateway of last resort", i.e., the router
address used when no other known route exists for a given IP packet's
destination address. However, the basic architectural assumption
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
Hi Steve,
Anything that is broken by this is inherently broken, not the Avahi
setup - and -they- should be fixed.
The link local default is installed at the lowest preference, and should
not be used if a better one exists.
The original bug report was about openswan, what specific problems have
y
I'm confirming this as a bug. I have never seen a situation where a
local-link default route has been useful to me, but I have frequently
been bitten by the network timeouts that result from this wrong route.
I believe that /etc/avahi/avahi-autoipd.action should be fixed to not
set a default route
That route tells it to just send packets for any IP directly out the
interface, this is usefull because in a LAN using zeroconf LL IPs (as
avahi-autoipd), only hosts without another non-LL ip should have an LL
ip.
So without a default (last resort) route out the interface, if you only
had an LL ip
When i start openswan, i get this error message :
ipsec_setup: multiple default routes, %defaultroute cannot cope!!!
It is because openswan is looking for the interface that manage the
defaultroute, since there is several default route, it fails to start.
And i can't just specify to it an interfa
It is not 'useless' it is installed as a last resort thus should not
cause any problems
It what way does it confuse openswan?
--
avahi-autoipd gives me an useless default route
https://launchpad.net/bugs/99489
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/ma
12 matches
Mail list logo
