search for: inaddr6_ani

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 I either lose IPv6 or lose IPv4 directly (but have it practically as IPv4-over-IPv6).

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 I either lose IPv6 or lose IPv4 directly (but have it practically as IPv4-over-IPv6).

Jim Klimov via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> 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 LAN on v4/v6. On another, I have an empty

Jim Klimov via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> 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 LAN on v4/v6. On another, I have an empty

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). Ultimately the chosen logic is that if there was a `LISTEN * <port>` in `upsd.conf`, the depending on

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). Ultimately the chosen logic is that if there was a `LISTEN * <port>` in `upsd.conf`, the depending on