Can anyone confirm that umdns service (Multicast DNS Daemon on UDP port 5353) does anything on Turris OS 6 ?
root@turris:~# ss -tulnp | grep umdns
udp UNCONN 0 0 224.0.0.251:5353 0.0.0.0:* users:(("umdns",pid=3150,fd=8))
udp UNCONN 0 0 192.168.1.254:5353 0.0.0.0:* users:(("umdns",pid=3150,fd=7))
udp UNCONN 0 0 [ff02::fb]:5353 *:* users:(("umdns",pid=3150,fd=10))
udp UNCONN 0 0 [fe80::da58:d7ff:fe00:2868]:5353 *:* users:(("umdns",pid=3150,fd=9))
root@turris:~# ubus call umdns update # triggers a scan && sleep 30
root@turris:~# ubus call umdns browse # look at the currently cached records
{
}
root@turris:~# ubus call umdns hosts # look at the currently cached hosts
{
}
UMDNS daemon doesn’t listen on assigned IPv6 LAN prefix anymore (same result on IPv6 ULA), just multicast and local IPv4 LAN as you can see. It worked “out of box” on previous version 5. I tested it on upgraded TOS 5.4.4 -->6.0 Omnia devices and on one device tried to do medkit recovery to 6.0.3 with no result. My configuration is simple:
root@turris:~# uci show umdns
umdns.@umdns[0]=umdns
umdns.@umdns[0].jail='1'
umdns.@umdns[0].network='lan'
root@turris:~# uci show firewall.lan_mDNS_rule
firewall.lan_mDNS_rule=rule
firewall.lan_mDNS_rule.name='Allow-mDNS'
firewall.lan_mDNS_rule.src='*'
firewall.lan_mDNS_rule.proto='udp'
firewall.lan_mDNS_rule.src_port='5353'
firewall.lan_mDNS_rule.dest_ip='224.0.0.251'
firewall.lan_mDNS_rule.target='ACCEPT'
firewall.lan_mDNS_rule.enabled='1'
root@turrish:~# uci show network.lan
network.lan=interface
network.lan.device='br-lan'
network.lan.proto='static'
network.lan.ip6assign='60'
network.lan._turris_mode='managed'
network.lan.ipaddr='192.168.1.254/24'