mDNS/avahi not resolving as expecting

Installing and Using OpenWrt
1

Trying to use avahi to cast to my TCL Roku using the YouTube app across VLANs. It currently can't be discovered.

This is the the avahi conf:

[server]
use-ipv4=yes
check-response-ttl=no
use-iff-running=no
allow-interfaces=br-guest,br-iot,eth1
[publish]
publish-addresses=yes
publish-hinfo=yes
publish-workstation=no
publish-domain=yes

[reflector]
enable-reflector=yes
reflect-ipv=no

[rlimits]
rlimit-core=0
rlimit-data=4194304
rlimit-fsize=0
rlimit-nofile=30

These are the firewall rules:

config rule
	option name 'allow mDNS'
	list proto 'udp'
	option src_port '5353'
	option dest_port '5353'
	option target 'ACCEPT'
	option src '*'
	list dest_ip '224.0.0.251'

config rule
	option name 'allow casting'
	list proto 'udp'
	option src_port '1900'
	list dest_ip '239.255.255.250'
	option dest_port '1900'
	option target 'ACCEPT'
	option src '*'

When I do an nslookup for the avahi IP it doesn't resolve for one of the devices:

nslookup -port=5353 10.200.0.185 224.0.0.251
;; communications error to 224.0.0.251#5353: timed out
;; communications error to 224.0.0.251#5353: timed out
;; communications error to 224.0.0.251#5353: timed out
;; no servers could be reached

However, it does for the openwrt router IP:

nslookup -port=5353 10.200.0.185 10.0.0.1
185.0.200.10.in-addr.arpa	name = YL00FP519033.local.

These are the log lines for avahi starting up:

Wed Aug 21 14:39:35 2024 daemon.info avahi-daemon[6519]: avahi-daemon 0.8 starting up.
Wed Aug 21 14:39:35 2024 daemon.warn avahi-daemon[6519]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Wed Aug 21 14:39:35 2024 daemon.info avahi-daemon[6519]: No service file found in /etc/avahi/services.
Wed Aug 21 14:39:35 2024 daemon.info avahi-daemon[6519]: Joining mDNS multicast group on interface br-guest.IPv4 with address 172.16.1.1.
Wed Aug 21 14:39:35 2024 daemon.info avahi-daemon[6519]: New relevant interface br-guest.IPv4 for mDNS.
Wed Aug 21 14:39:35 2024 daemon.info avahi-daemon[6519]: Joining mDNS multicast group on interface br-iot.IPv4 with address 10.200.0.1.
Wed Aug 21 14:39:35 2024 daemon.info avahi-daemon[6519]: New relevant interface br-iot.IPv4 for mDNS.
Wed Aug 21 14:39:35 2024 daemon.info avahi-daemon[6519]: Joining mDNS multicast group on interface eth1.IPv6 with address fe80::80c0:1eff:fea6:8d4e.
Wed Aug 21 14:39:35 2024 daemon.info avahi-daemon[6519]: New relevant interface eth1.IPv6 for mDNS.
Wed Aug 21 14:39:35 2024 daemon.info avahi-daemon[6519]: Joining mDNS multicast group on interface eth1.IPv4 with address 10.0.0.1.
Wed Aug 21 14:39:35 2024 daemon.info avahi-daemon[6519]: New relevant interface eth1.IPv4 for mDNS.
Wed Aug 21 14:39:35 2024 daemon.info avahi-daemon[6519]: Network interface enumeration completed.
Wed Aug 21 14:39:35 2024 daemon.info avahi-daemon[6519]: Registering new address record for 172.16.1.1 on br-guest.IPv4.
Wed Aug 21 14:39:35 2024 daemon.info avahi-daemon[6519]: Registering new address record for 10.200.0.1 on br-iot.IPv4.
Wed Aug 21 14:39:35 2024 daemon.info avahi-daemon[6519]: Registering new address record for fe80::80c0:1eff:fea6:8d4e on eth1.*.
Wed Aug 21 14:39:35 2024 daemon.info avahi-daemon[6519]: Registering new address record for 10.0.0.1 on eth1.IPv4.
Wed Aug 21 14:39:35 2024 daemon.info avahi-daemon[6519]: Registering HINFO record with values 'AARCH64'/'LINUX'.
2

So, it looks like mDNS is working, it's just that the casting is not

ping YL00FP519033.local
PING YL00FP519033.local (10.200.0.185) 56(84) bytes of data.
64 bytes from RokuStreambar (10.200.0.185): icmp_seq=1 ttl=63 time=1.70 ms
64 bytes from RokuStreambar (10.200.0.185): icmp_seq=2 ttl=63 time=1.86 ms
64 bytes from RokuStreambar (10.200.0.185): icmp_seq=3 ttl=63 time=1.33 ms
3

Solved by combining with this:

4

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.