Jim Klimov writes:
> Thanks to everyone for a fruitful discussion, links and ideas.
>
> The result is nearing a merge at
> https://github.com/networkupstools/nut/pull/2013 and seems to not upset CI
> on any platform, including Windows (which behaves funny WRT binding to the
> same host:port as
Thanks to everyone for a fruitful discussion, links and ideas.
The result is nearing a merge at
https://github.com/networkupstools/nut/pull/2013 and seems to not upset CI
on any platform, including Windows (which behaves funny WRT binding to the
same host:port as many times as you ask).
Jim Klimov via Nut-upsuser writes:
> I've recently found that at least on my test box the `LISTEN *` line had
> only set up an IPv4 `0.0.0.0` listener but not an IPv6 `::0` listener for
> `upsd`.
Interesting. On one system I checked, I have 4 explicit directives for
127.0.0.1, ::1, and the
Cheers all,
TL;DR version:
I've recently found that at least on my test box the `LISTEN *` line had
only set up an IPv4 `0.0.0.0` listener but not an IPv6 `::0` listener for
`upsd`. In fact, at least on a "dual-stack" system, it seems impossible to
bind to both - so depending on binding order
