mDNS discovery appears to be broken since 98e310d31404bf41475e49ba818b5aefced416e9 (#509).
The symptoms are that no discovered peer comes out the other end of the channel (it definitely goes in), and the madness stops querying after a while. Tweaks like using an unbounded channel and sprinkling println!s around the madness crate didn't yield any result nor hint.
A new attempt should:
ensure mDNS works under docker, so we can have coverage in CI
consider to add responder capabilities to the mdns crate directly
consider to use a system service (such as avahi) instead
mDNS discovery appears to be broken since 98e310d31404bf41475e49ba818b5aefced416e9 (#509).
The symptoms are that no discovered peer comes out the other end of the channel (it definitely goes in), and the
madnessstops querying after a while. Tweaks like using an unbounded channel and sprinklingprintln!s around themadnesscrate didn't yield any result nor hint.A new attempt should:
mdnscrate directly