On Mon, Apr 28, 2025 at 12:40:54PM +0000, mailinglists.accustom...@aleeas.com wrote: > On Monday, April 28th, to...@tuxteam.de wrote: > > > > > > > While it is a good idea to have tshark, we already know that > > the OP's machine > > > > - is trying to resolve via mDNS > > - that part is failing. > > Yeah, Thanks for understanding. There are couple of connection like > 0.0.0.0:mdns and [::]:mdns that I can see. I posted in this mailing list to > know that whether are there some dependencies not satisfied or I have to > check some conf files.
OK. > I should have been more clear, I guess. About redacted IPs and mac address, I > am not sure I am comfortable posting my public IPs in a forum that is going > to be archived. Don't get me wrong I willing to help you guys to help me. But > I am not sure how knowing exact ips are helpful. If you guys can tell what > you guys are looking for, or share relevant links so that I can lookup. That was my guess. By now I think it is irrelevant, since we advanced to the mDNS issue. At some point, it'd been interesting whether yours were IPv4 zeroconf "link-local" addresses, i.e. in the 169.254.0.0/16 range: I'd bet they are :-) Note that posting such (local, non-routable) addresses is pretty harmless, since they won't be seen beyond your gateway, and many of us have some of those at home ;-) Now to the mDNS experts (I'm not one, mind you). Cheers -- t
signature.asc
Description: PGP signature