search for: configuret

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

...IPv4 directly (but have it practically as IPv4-over-IPv6). That is not intrinsic to a system that does v4 and v6. It is about a misfeature which if turned on, when one binds to v6 also sets up a listener on v4 which connects as a mapped address. These days, I view it as a bug for a system to be configuret hat way. On NetBSD, from ip6(4): IPV6_V6ONLY int * Get or set whether only IPv6 connections can be made to this socket. For wildcard sockets, this can restrict connections to IPv6 only. which is 1 on my system. > Given that `LISTEN *` support is...

...IPv4 directly (but have it practically as IPv4-over-IPv6). That is not intrinsic to a system that does v4 and v6. It is about a misfeature which if turned on, when one binds to v6 also sets up a listener on v4 which connects as a mapped address. These days, I view it as a bug for a system to be configuret hat way. On NetBSD, from ip6(4): IPV6_V6ONLY int * Get or set whether only IPv6 connections can be made to this socket. For wildcard sockets, this can restrict connections to IPv6 only. which is 1 on my system. > Given that `LISTEN *` support is...

...with the same command using ads). My gues is that the "net" command uses a libary, that I have not placed in the right directory, can I check this somehow ?. Another solution would be to install a precompiled rpm of samba 3.0.8 on redhat 7.3, but I have not been able to find one that is configuret with ads and ldap support, does anyone know if such an rpm exists somewhere on the web ?. Regards. Lars Roland

...it practically as IPv4-over-IPv6). > > That is not intrinsic to a system that does v4 and v6. It is about a > misfeature which if turned on, when one binds to v6 also sets up a > listener on v4 which connects as a mapped address. These days, I view > it as a bug for a system to be configuret hat way. On NetBSD, from > ip6(4): > > IPV6_V6ONLY int * > Get or set whether only IPv6 connections can be made to this > socket. For wildcard sockets, this can restrict connections > to > IPv6 only. > > which is 1 on my syste...

...it practically as IPv4-over-IPv6). > > That is not intrinsic to a system that does v4 and v6. It is about a > misfeature which if turned on, when one binds to v6 also sets up a > listener on v4 which connects as a mapped address. These days, I view > it as a bug for a system to be configuret hat way. On NetBSD, from > ip6(4): > > IPV6_V6ONLY int * > Get or set whether only IPv6 connections can be made to this > socket. For wildcard sockets, this can restrict connections > to > IPv6 only. > > which is 1 on my syste...