On Fri, Feb 23, 2024 at 4:37 PM anthony_ful...@trendmicro.com
wrote:
>
> I tried this on a fresh installation of Fedora Workstation 39. I installed
> wireshark and set the filter to `tcp.port == 5355` then ran the python script
> again with an ip of `123.123.123.123` and I see an outbound
From: Anthony Fuller (TR-NA)
Date: Friday, February 23, 2024 at 10:22 AM
To: Cristian Rodríguez
Cc: systemd-devel@lists.freedesktop.org
Subject: Re: [systemd-devel] Systems-resolved: Calling gethostbyaddr on
non-local/non-private causes connection attempt
Hi Cristian,
Below is my complete /etc
db files
rpc:db files
netgroup: nis
```
From: Cristian Rodríguez
Date: Friday, February 23, 2024 at 10:07 AM
To: Anthony Fuller (TR-NA)
Cc: systemd-devel@lists.freedesktop.org
Subject: Re: [systemd-devel] Systems-resolved: Calling gethostbyaddr on
non-local/non-priv
On Thu, Feb 22, 2024 at 8:13 PM anthony_ful...@trendmicro.com
wrote:
I tried again now with packet capture software and no such behaviour
was found. ..what you have in the hosts line of nsswitch.conf ?
.
Let me know what else I can investigate, this is new territory for me.
Thanks,
Anthony
From: Cristian Rodríguez
Date: Thursday, February 22, 2024 at 4:48 PM
To: Anthony Fuller (TR-NA)
Cc: systemd-devel@lists.freedesktop.org
Subject: Re: [systemd-devel] Systems-resolved: Calling gethostbyaddr
On Thu, Feb 22, 2024 at 2:09 PM anthony_ful...@trendmicro.com
wrote:
>
> Port 5355 is used for LLMNR and RFC-4795 [4], states in the abstract that
> “LLMNR only operates on the local link” so I think the current behavior of
> contacting hosts on port 5355 is incorrect, especially if that host
