Avahi: "Failed to create client object: Daemon not running"

alteredstate · May 6, 2019, 5:16 PM

@Gertjan said in Avahi: "Failed to create client object: Daemon not running":

This part :
@alteredstate said in Avahi: "Failed to create client object: Daemon not running":

[2.4.4-RELEASE][admin@pfsense.jam.lan]/root: avahi-browse -a
Failed to create client object: Daemon not running

is known : https://forum.netgate.com/topic/134339/new-avahi-package/30

Thanks for the reply! So that seems related to "dbus" but it appears to be disabled intentionally. I suppose the: "nss-mdns" is not needed as well? I see this on the pfSense Packet Capture:

22:48:23.451723 44:91:60:db:60:aa (oui Unknown) > 01:00:5e:00:00:fb (oui Unknown), ethertype IPv4 (0x0800), length 135: (tos 0x0, ttl 255, id 49097, offset 0, flags [DF], proto UDP (17), length 121)
    Galaxy-S9.jam.lan.mdns > 224.0.0.251.mdns: [udp sum ok] 4 [4q] PTR (QM)? _674A0243._sub._googlecast._tcp.local. PTR (QM)? _233637DE._sub._googlecast._tcp.local. PTR (QM)? _8E6C866D._sub._googlecast._tcp.local. PTR (QM)? _googlecast._tcp.local. (93)

pfSense is definitely seeing the mdns query and I would have expected to see some sort of response from Avahi but nothing.

alteredstate · May 17, 2019, 7:52 PM

Has anyone been able to successfully get this type of setup to work and by that I mean using Avahi to route an mDNS "Cast" from a phone app to a smart TV across VLANs? If so, would you please provide some insight on how you were able to achieve this?

jagradang · Aug 19, 2019, 4:53 PM

I'm trying to get this working at the moment too but no luck.

Same messages in the logs as above

I can cast to firestick, smart tv and chrome cast if i connect wifi to the vlan containing all these devices. Changing to a different vlan i can only cast to chromecast. I can see the smart tv but it won't connect, and firestick won't even show up.

Did anyone ever get this working?

alteredstate · Aug 19, 2019, 5:06 PM

@jagradang said in Avahi: "Failed to create client object: Daemon not running":

I'm trying to get this working at the moment too but no luck.

Same messages in the logs as above

I can cast to firestick, smart tv and chrome cast if i connect wifi to the vlan containing all these devices. Changing to a different vlan i can only cast to chromecast. I can see the smart tv but it won't connect, and firestick won't even show up.

Did anyone ever get this working?

Were you able to resolve this? This just started happening recently, but if I switch my Samsung Galaxy S9+ to the same WiFi network as my Samsung TV (VLAN20) and cast Youtube from my phone then I can switch my phone back to the other WiFi network (VLAN35) and still continue to cast Youtube. This was not the case before and I would lose all casting ability when switching back to VLAN35. The only catch is I must make the initial cast from VLAN20. Not sure what caused this to start happening but I'll take it! Just wish I could figure out how to initially cast from VLAN35 so I could avoid switching WiFi networks all the time.

jagradang · Aug 20, 2019, 7:39 PM

@alteredstate still trying to work out what's happening. I can cast YouTube just fine using avahi. But I can't cast to Samsung tv or my firestick. Only if I connect to that vlan. My printer can be found either. I have to connect using its ip only.

There is definately an underlying issue or rule that's blocking all this broadcast readdix or something.

If I find it I'll shout back.

rajid · Nov 7, 2021, 1:08 AM

Any updates after all of this time? I'm seeing this and don't know what could be causing it.

alteredstate · Nov 7, 2021, 1:08 AM

@rajid said in Avahi: "Failed to create client object: Daemon not running":

Any updates after all of this time? I'm seeing this and don't know what could be causing it.

Unfortunately no (at least for me). I gave up and just connect to the same vlan as my SmartTV. I wish it would have worked as I would like to keep my devices on a separate vlan.

rajid · Nov 7, 2021, 1:11 AM

I'm getting closer. Editing /usr/local/etc/avahi/avahi-daemon.conf to enable "dbus", and then adding:
dbus_enable=YES
to /etc/rc.conf
at least gets the daemon running and avahi-browse no longer gives a "no daemon" error.

I'm thinking I have some filtering which could be interferring now.

alteredstate · Nov 7, 2021, 2:06 AM

@rajid said in Avahi: "Failed to create client object: Daemon not running":

I'm getting closer. Editing /usr/local/etc/avahi/avahi-daemon.conf to enable "dbus", and then adding:
dbus_enable=YES
to /etc/rc.conf
at least gets the daemon running and avahi-browse no longer gives a "no daemon" error.

I'm thinking I have some filtering which could be interferring now.

Nice! Any luck getting "Cast" (mDNS) to work from phone to a SmartTV across vlans?

rajid · Nov 11, 2021, 7:05 AM

@rajid Followup:
I've also found that I need to add a filter to allow mdns packets to "pass", otherwise they end up blocked. I'm still not seeing any mdns responses using the avahi programs (such as "avahi-browse -a"), but "tcpdump" shows the packets are there on the wire.