search for: internet6

...357 em0 127.0.0.1 127.0.0.1 UH 0 3934 lo0 192.168.16.0/24 link#1 UC 0 0 em0 192.168.16.1 00:07:e9:80:33:bc UHLW 1 16 em0 951 192.168.16.254 00:07:e9:80:33:bc UHLW 2 0 em0 1002 Internet6: Destination Gateway Flags Netif Expire ::1 ::1 UHL lo0 fe80::%lo0/64 fe80::1%lo0 U lo0 fe80::1%lo0 link#5...

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).

...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 upsd.conf and it is listening: nut upsd 1047 4* internet stream tcp 127.0.0.1:3493 nut upsd 1047 5* internet6 stream tcp [::1]:3493 > 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). That is not intrinsic to a system that does v4 and v...

...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 upsd.conf and it is listening: nut upsd 1047 4* internet stream tcp 127.0.0.1:3493 nut upsd 1047 5* internet6 stream tcp [::1]:3493 > 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). That is not intrinsic to a system that does v4 and v...

...> 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 > upsd.conf and it is listening: > > nut upsd 1047 4* internet stream tcp 127.0.0.1:3493 > nut upsd 1047 5* internet6 stream tcp [::1]:3493 > > > 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). > > That is not intrinsic to...

...> 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 > upsd.conf and it is listening: > > nut upsd 1047 4* internet stream tcp 127.0.0.1:3493 > nut upsd 1047 5* internet6 stream tcp [::1]:3493 > > > 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). > > That is not intrinsic to...