Hi Lennart! Me again :-)
The libavahi-qt4 lib seems to be not provided in the OpenSuse standard repos. Is this right, or am I just looking at the wrong place? All other Avahi-libs are available. Thanx Daniel On Sun, 2009-06-07 at 01:52 +0200, Lennart Poettering wrote: > On Thu, 28.05.09 13:21, Florian Erfurth ([email protected]) wrote: > > > Ok, this means the host always(?) get 169.254.7.XXX-Address before > > getting IP from /etc/network/interfaces, right? Thank you for your tip, > > but I cannot use "ip addr" on client if I want to know the IP of the > > host. > > Uh? Not sure I understand what you mean. > > Avahi only announces one address per host name and interface. It tries > to be smart and picks the routable address over the IPv4LL address if > both are configured on the same interface. > > Other mDNS implementations my have implemented this differently, and > might even register both addresseson the network. When Avahi discovers > that it is not deterministc which one of those it picks. > > > > On a local network it shouldn't matter which adress is picked for > > > connection as long as it is a valid one. That's why it is not > > > deterministic which address is handed to applications when they try to > > > resolve a host name. > > > > > Sorry, you're saying "169.254.7.XXX"-Adress is a valid address? Here its > > not valid since the network-setting is given (static IP, netmask ...). > > If I try to ping from client, I get "Destination Net Unreachable". > > Yes, of course. 169.254.x.x addresses are valid ipv4ll adresses. Some > older OSes/distros/stacks don't know them. However everything recent > knows it. In fact Windows knows them since 95b, MacOS X since about > forever. And the better Linux distributions since quite some time too. > > Lennart > _______________________________________________ avahi mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/avahi
