Currently ifup-eth adds a single zeroconf route to each interface. To be fully compatible it should add two: ip route add 169.254.0.0/16 dev ${REALDEVICE} metric 1000 scope link ip route add default dev ${REALDEVICE} metric 1000 scope link For an explanation what these routes do, please consult: http://avahi.org/wiki/AvahiAutoipd#Routes
Is there any specific rationale of '1000' as a metric, other than 'very very high'?
No. It should just be "very, very high". Apple uses 99 for those routes. And we're better than Apple. Hence 1000. ;-)
How does this work in the case of multiple active devices, and therefore having multiple default routes with metric 1000?
Linux is fine with multiple routes to the same network. The route that was created last wins. Of course, that means you cannot reach any link-local hosts on the network that was attached first, but I guess that is OK.
Based on the date this bug was created, it appears to have been reported against rawhide during the development of a Fedora release that is no longer maintained. In order to refocus our efforts as a project we are flagging all of the open bugs for releases which are no longer maintained. If this bug remains in NEEDINFO thirty (30) days from now, we will automatically close it. If you can reproduce this bug in a maintained Fedora version (7, 8, or rawhide), please change this bug to the respective version and change the status to ASSIGNED. (If you're unable to change the bug's version or status, add a comment to the bug and someone will change it for you.) Thanks for your help, and we apologize again that we haven't handled these issues to this point. The process we're following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again.
Changing version to '9' as part of upcoming Fedora 9 GA. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
(In reply to comment #4) > Linux is fine with multiple routes to the same network. The route that was > created last wins. Of course, that means you cannot reach any link-local hosts > on the network that was attached first, but I guess that is OK. I need to correct myself here. Linux doesn't allow multiple routes to the same destination with the same metric. An elegant way to work around this is by adding the ifindex to the 1000. i.e. Something like this: ip route add 169.254.0.0/16 dev eth0 metric $((1000 + `cat /sys/class/net/eth0/ifindex`)) scope link The second route (i.e. the default one) only needs to be there if we have an IPv4ll address assigned. I can thus create it in the avahi-autoipd package, it doesn't need to be set globally. Thus I only ask you to replace this line in the network scripts: ip route replace 169.254.0.0/16 dev ${REALDEVICE} by this one: ip route add 169.254.0.0/16 dev ${REALDEVICE} metric $((1000 + `cat /sys/class/net/${REALDEVICE}/ifindex`)) scope link
http://git.fedorahosted.org/git/?p=initscripts.git;a=commitdiff;h=641149c88429ad66fe233a02fc48d5eb13a4c4b5
The commit looks borked. You open three ((( but close only two )).
Fixed.