You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am experiencing an issue where devices within the Thread network cannot be discovered by external networks using mDNS. Below are the details regarding my OTBR build command and the outputs from the relevant commands.
The ping command supports ipv6, because pinging the ipv6 address directly is normal. Even when I use avahi-browse on the OTBR host, I can't find any Thread related services.
In addition to OTBR_DNSSD_DISCOVERY_PROXY and OTBR_SRP_ADVERTISING_PROXY, what other macros control the mDNS and SRP behavior of OTBR?
There is also a strange phenomenon: using a Linux host, you can directly ping the Thread device's ipv6 address, but the Windows host cannot ping. They are all in the same LAN (no subnet).
Refer to Ping the hostname or IPv6 address, add mdns6_minimal to /etc/nsswitch.conf and restart the machine. Now the ping command can find the appropriate IPv6 address through the mDNS domain name.
But the windows machine still cannot ping the Thread device.
I am experiencing an issue where devices within the Thread network cannot be discovered by external networks using mDNS. Below are the details regarding my OTBR build command and the outputs from the relevant commands.
OTBR Build Command:
Output from
ot-ctl srp server service
:Despite the above configurations, when I try to ping the device using the command
ping MGM240_3425B4FFFE0E86D9.local
, I receive the following error:Thanks
The text was updated successfully, but these errors were encountered: