Hi, Sorry for hijacking old thread but seems like indeed there is still indeed an unresolved bug in umDNS. I am using custom build OpenWRT 19.07. But without any modification to packages involved. I have followed the guide here: https://openwrt.org/docs/guide-developer/mdns
But my locally advertised printer is not on the list.
I have placed /etc/umdns/printer_service.json with the following content:
"ty=HP LaserJet P1005",
"product=(HP LaserJet P1005)",
"usb_MDL=HP LaserJet P1005",
I've checked the syntax with some online JSON syntax checked and I had a typo but I fixed it and its correct JSON now. Also I verified that printer is working besides network discovery. The printer works normally via network when added manually on Linux box and it prints. The firmware is loaded etc. I just want to make it discoverable on the br-lan.
I have two devices in network a router and ap both Turris Omnias and when I issue: root@router:~# ubus call umdns browse
The same on the AP the router's SSH service is discoverable: root@ap:~# ubus call umdns browse
So it seems like umDNS is working but ignoring services defined in /etc/umdns/*.json.
Could it be some permission/ownership issue? Any ideas?
EDIT: I forgot to mention that printer is connected to dumb AP's USB port.
EDIT2: I forgot to mention my local DNS uses domain .lan instead of .local.
I have this rule on both devices; the rule is the last one:
/etc/config/firewall config rule option src_port '5353' option name 'Allow-mDNS' option target 'ACCEPT' list dest_ip '188.8.131.52' option dest_port '5353' list proto 'udp' option src '*'
Also this is the scan from other device in the network:
root@wizard:~# nmap -sU -p 5353 ap.lan Starting Nmap 7.91 ( https://nmap.org ) at 2021-07-17 13:58 UTC Nmap scan report for ap.lan ($AP_IPv4) Host is up (0.00012s latency). PORT STATE SERVICE 5353/udp open|filtered zeroconf MAC Address: D8:58:D7:00:3D:9E (CZ.NIC, z.s.p.o.) Nmap done: 1 IP address (1 host up) scanned in 0.79 seconds
EDIT: I've runned wireshark with remote ssh session on br-lan of ap device and I could see mdns traffic with this filter udp && ip.dst == 184.108.40.206. The traffic was from $ROUTER_IPv4, from $AP_IPv4 and from some IP of Android device advertising PTR records for SSH and GoogleCast respectively. All to 220.127.116.11 protocol MDNS. So it seems like it's no firewall issue but more likely a bug in umdns package ignoring services in /etc/umdns/*.json.