Linus Lüssing | 3 Feb 09:14
Picon

Re: Avahi Signalling that it is going offline??

On Mon, Jan 30, 2012 at 12:39:27PM -0700, Nathanael D. Noblet wrote:
> Hello
> 
>   I have a few devices that have a .service file in
> /etc/avahi/services. It works well I can see the service etc.
> However my administration app which is using avahi to detect
> machines coming online/offline in a link-local setup never knows
> when they disappear because they are always there. The devices
> offering the service are portable so go to sleep and move around on
> the network. So I'm wondering if there is a way the avahi-daemon can
> signal that the service/device is going offline so I get the
> notifications? When I first started and had an actual app listening
> it was just somewhat built in when you unregistered, however now it
> never does that.
> 
> I'm basically using the service to help detect when the devices are
> online since the service I want to use is always there when the
> devices are available. If that makes any sense.

Hi Nathanael,

For something similiar I'm just using avahi-browse and some ugly
bash-foo, don't know whether that's what you are looking for, too:

~~ snip ~~
#!/bin/sh
BROWSE_CMD="avahi-browse -p _snmp._tcp"

add_event() {
	echo "add_event for $1"
(Continue reading)

Gravatar

nss-mdns and multihoming

Hello, gents,

 

I would like to configure nss-mdns to prefer certain network interfaces for multicast DNS resolution, because I have a multihomed / always-on VPN system and sometimes nss-mdns returns address of the VPN when I am on the home network, causing all sorts of problems. What I would like is for nss-mdns to prefer resolving a host name X.local discovered on the local interface (wlan0) whenever a X.local machine is found on avahi's cache, and, if not, then return the IP address for the host name X.local on the VPN interface (tap0).

 

How to tell nss-mdns to do this?

Lennart Poettering | 14 Feb 22:51

[HEADS-UP] Dropping avahi-qt3, avahi-ui for gtk2, avahi-howl

Heya,

I am planning to drop Qt3 and Gtk2 support from avahi soon, leaving only
Qt4 and Gtk3 in. Anybody opposed to that? You need a very strong case if
you want to convince me not to do this.

Similar I want to drop the HOWl compat kludge. Would like to drop the
Bonjour compat kludge too, but I figure too many folks still use that.

Lennart

--

-- 
Lennart Poettering - Red Hat, Inc.
Lennart Poettering | 15 Feb 00:12

[ANNOUNCE] Avahi 0.6.31

Heya,

http://avahi.org/download/avahi-0.6.31.tar.gz

This mostly fixes one thing only: we can build Avahi again with current
autoconf.

Lennart Poettering (5):
      systemd: syslog.target is not longer useful
      build-sys: compatibility with newer automake
      build-sys: prepare release
      update NEWS
      build-sys: actually, we need to place the service type database in
      lib64, not unconditionally

Ludwig Nussel (1):
      database: add Mumble to service type database

Lennart

--

-- 
Lennart Poettering - Red Hat, Inc.
Peter Korsgaard | 15 Feb 08:34
Picon

Re: [HEADS-UP] Dropping avahi-qt3, avahi-ui for gtk2, avahi-howl

>>>>> "Lennart" == Lennart Poettering <lennart@...> writes:

Hi,

 Lennart> I am planning to drop Qt3 and Gtk2 support from avahi soon,
 Lennart> leaving only Qt4 and Gtk3 in. Anybody opposed to that? You
 Lennart> need a very strong case if you want to convince me not to do
 Lennart> this.

I haven't heard of anyone still using the Qt3 stuff (and Qt4 has been
out for quite some time), but we're atleast supporting the gtk2 stuff in
Buildroot. Not everyone has moved to GTK3/Gnome3 yet, my feeling is that
it's still a bit early to drop it.

 Lennart> Similar I want to drop the HOWl compat kludge. Would like to
 Lennart> drop the Bonjour compat kludge too, but I figure too many
 Lennart> folks still use that.

I'm not aware of anyone using the howl stuff, but we do have people
using the Bonjour API (for compat with Windows afaik).

--

-- 
Bye, Peter Korsgaard
Picon
Gravatar

Re: [HEADS-UP] Dropping avahi-qt3, avahi-ui for gtk2, avahi-howl

I suggest to keep the avahi-ui with Gtk2 as reference, I mean, Gtk2 is
still widely used, and would be nice to keep it until the Gtk3 migration
is complete. You could ship both Gtk2 and Gtk3 codes, but just compile
Gtk3 code.

By the way, the qt3 is really out of date.

Anyways, is just my opinion.
--

-- 
Atte. Félix Arreola Rodríguez,
Firmado con GPG, llave 1E249EE4
Guido Trentalancia | 18 Feb 04:45

[PATCH] avahi-0.6.31: fix avahi-python Makefile for install target without DESTDIR

Hello.

The following patch is intended to fix an installation error introduced
in version 0.6.31 and showing up when DESTDIR is not defined:

--- avahi-0.6.31-orig/avahi-python/avahi/Makefile.in	2012-02-14 23:36:37.346061317 +0100
+++ avahi-0.6.31/avahi-python/avahi/Makefile.in	2012-02-18 04:32:32.474681328 +0100
@@ -456,8 +456,12 @@ install-avahiPYTHON: $(avahi_PYTHON)
 	  $(INSTALL_DATA) $$files "$(DESTDIR)$(avahidir)" || exit $$?; \
 	done || exit $$?; \
 	if test -n "$$dlist"; then \
-	  $(am__py_compile) --destdir "$(DESTDIR)" \
-	                    --basedir "$(avahidir)" $$dlist; \
+	  if test -z "$(DESTDIR)"; then \
+	    $(am__py_compile) --destdir "$(DESTDIR)" \
+			      --basedir "$(avahidir)" $$dlist; \
+	  else
+	    $(am__py_compile) --basedir "$(avahidir)" $$dlist; \
+	  fi; \
 	else :; fi

 uninstall-avahiPYTHON:

Guido Trentalancia | 18 Feb 05:15

[PATCH] avahi-0.6.31: fix avahi-python Makefile for install target without DESTDIR (v2)

Intended to fix installation error for avahi version 0.6.31 when DESTDIR
is not defined.

Version2: fix a typo in previously submitted patch (missing "\" at the
end of line after the else statement) and fix the order of commands in
the if statement. Add a similar modification for avahi-discover.

Intended to fix installation error for avahi version 0.6.31 when DESTDIR is not defined.

Version2: fix a typo in previously submitted patch (missing "\").

--- avahi-0.6.31-orig/avahi-python/avahi/Makefile.in	2012-02-14 23:36:37.346061317 +0100
+++ avahi-0.6.31/avahi-python/avahi/Makefile.in	2012-02-18 04:32:32.474681328 +0100
@@ -456,8 +456,12 @@ install-avahiPYTHON: $(avahi_PYTHON)
 	  $(INSTALL_DATA) $$files "$(DESTDIR)$(avahidir)" || exit $$?; \
 	done || exit $$?; \
 	if test -n "$$dlist"; then \
-	  $(am__py_compile) --destdir "$(DESTDIR)" \
-	                    --basedir "$(avahidir)" $$dlist; \
+	  if test -z "$(DESTDIR)"; then \
+	    $(am__py_compile) --basedir "$(avahidir)" $$dlist; \
+	  else \
+	    $(am__py_compile) --destdir "$(DESTDIR)" \
+			      --basedir "$(avahidir)" $$dlist; \
+	  fi; \
 	else :; fi

 uninstall-avahiPYTHON:
--- avahi-0.6.31-orig/avahi-python/avahi-discover/Makefile.in	2012-02-14 23:36:37.265061040 +0100
+++ avahi-0.6.31/avahi-python/avahi-discover/Makefile.in	2012-02-18 05:10:00.632755343 +0100
@@ -477,8 +477,12 @@ install-avahi_discoverPYTHON: $(avahi_di
 	  $(INSTALL_DATA) $$files "$(DESTDIR)$(avahi_discoverdir)" || exit $$?; \
 	done || exit $$?; \
 	if test -n "$$dlist"; then \
-	  $(am__py_compile) --destdir "$(DESTDIR)" \
-	                    --basedir "$(avahi_discoverdir)" $$dlist; \
+	  if test -z "$(DESTDIR)"; then \
+	    $(am__py_compile) --basedir "$(avahi_discoverdir)" $$dlist; \
+	  else \
+	    $(am__py_compile) --destdir "$(DESTDIR)" \
+			      --basedir "$(avahi_discoverdir)" $$dlist; \
+	  fi; \
 	else :; fi

 uninstall-avahi_discoverPYTHON:

Kirk Reistroffer | 21 Feb 01:31
Favicon

Bonjour emulation by Avahi on Ubuntu

I have a Bonjour-aware service in development and running on OSX and Windows.  I'm currently moving it onto Linux flavors and am looking for advice on how best to proceed with that.

It appears that Avahi is a preferred Linux native zeroconf implementation and I see that there's been some collaboration between Apple and the Avahi project in the past, leading to an Avahi supplied replacement dns_sd.h and an avahi-compat-libdns_sd library.  I'm looking for information on how to initially make use of the compatibility library.  I'm expecting that I'll eventually need to re-implement the zeroconf parts of the app to the Avahi API on Linux but hope to more immediately get a Linux build that plays well/ok with its peers for POC.

I haven't yet found a spot on www.avahi.org that describes how to build the first step.  I've substituted the Avahi dns_sd.h (which appears to be a subset of Apple's dns_sd.h) and link with libavahi-common.so.  I've tried:
> sudo apt-get install libavahi-compat-libdnssd1
That appears to be a source download and I'm trying to get all of its dependencies via ./configure in its avahi-0.6.31 directory. I'm guessing that will eventually get me a libavahi-compat-libdnssd1.so to add to my app link.
It seems that the standard Avahi .so's are pre-installed in Ubuntu 11 but the compatibility libraries aren't so I think I have to build it locally and add it to /usr/lib with the other libavahi-*.so files.  Am I on the right track?


aymeric demay | 23 Feb 17:21
Picon
Favicon

Publish services in local

Hi,

I actually work for a project where we decide to use avahi to discover services in all our sytem...
We want to publish global services and also local services.
We use avahi_entry_group_add_service and avahi_entry_group_commit methods. This works well for global services: all machines of our network receive notifications of service publication. But we do not know how to publish only on local... We tried by modifying AvahiIfIndex parameter (value 1 for lo interface): this did not work (no notification received on local machine). We tried by modifying AvahiPublishFlags parameter (value AVAHI_PUBLISH_NO_ANNOUNCE): we had an error with avahi_entry_group_add_service "Failed to add _service1._tcp service: Invalid flags"
Can we do this with avahi?

Thanks for your answer,
regards

Gmane