>Seems solved to me in hardy anyone can comment? >I have tried again, and there where "eth0:avahi", "eth0" and "eth1" already up, but no "eth1:avahi".
This is because avahi can only configures one interface. To do otherwise would require separate resolver caches for each network interface, in accordance with RFC4795 (http://www.ietf.org/rfc/rfc4795.txt) at Sections 4.3 and 5.4. Implementing such behavior would increase vulnerabilities to denial of service (id. at Section 5.1) and spoofing (id. at Section 5.3) man-in-the-middle attacks and would reduce resolver performance (see manpage of resolv.conf). The security vulnerabilities can be mitigated by following the guidelines suggested in RFC4795 at 5.2, but will not be entirely eliminated, especially in the context of internet cafes and public wifi zones. >there is no reason avahi-daemon should affect Network managers access There is an indirect connection between the two. The problem centers around the way avahi-autoipd interacts with dhcdbd, which both ignore or interfere with the configuration found in /etc/network/interfaces. More generally and fundamentally, networking is unstable in the default installation because IP addresses are allocated using three parallel systems that don't work together very well: dhclient/ifupdown, dhclient/dhcdbd, and avahi-daemon/avahi-autoipd. Happy Trails, Loye Young Isaac & Young Computer Company Laredo, Texas http://www.iycc.biz -- [feisty] avahi daemon interacts badly with network-manager https://bugs.launchpad.net/bugs/82287 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
