search for: v6on

...6). 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 in fact not documented explicitly (I > think),...

...6). 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 in fact not documented explicitly (I > think),...

...he end neither socket works, declare a fatal error (could not fulfill the config requirement). If we could get IPv4 initially, and could not after getting IPv6, do not bother - assume a dual-stack system (and log it so). Also as part of this change, NUT would ask (although not insist) for the IPV6_V6ONLY socket option when preparing IPv6 connections, except when handling `LISTEN *`. Finally, I noticed that if some configuration hostname resolves to more than one address, the first one bound wins and others are ignored. This behavior was here before, the PR change just logs that this happens. Jim...

...he end neither socket works, declare a fatal error (could not fulfill the config requirement). If we could get IPv4 initially, and could not after getting IPv6, do not bother - assume a dual-stack system (and log it so). Also as part of this change, NUT would ask (although not insist) for the IPV6_V6ONLY socket option when preparing IPv6 connections, except when handling `LISTEN *`. Finally, I noticed that if some configuration hostname resolves to more than one address, the first one bound wins and others are ignored. This behavior was here before, the PR change just logs that this happens. Jim...

Am 26.08.2018 um 18:12 schrieb TE Dukes: > Thanks. I did open the port but made no difference. > > I found this in the roundcube mail error file: > > [26-Aug-2018 11:48:41 -0400]: <a763f95e> IMAP Error: Login failed for tdukes > from 192.168.1.102. Could not connect to localhost:143: > php_network_getaddresses: getaddrinfo failed: System error in >

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

...cp LISTEN 0 100 *:143 *:* > users:(("dovecot",pid=1576,fd=37)) ino:32014 sk:ffff913e953e2e80 <-> > tcp LISTEN 0 100 :::143 :::* > users:(("dovecot",pid=1576,fd=38)) ino:32015 sk:ffff913b2e90a100 v6only:1 > <-> So port 143 is listening. Are we back to the point that your DNS or NSS is broken so that even telnet localhost 143 fails while telnet 127.0.0.1 143 is successful? > Thanks!! Alexander

...| grep 143 : tcp LISTEN 0 100 *:143 *:* users:(("dovecot",pid=1576,fd=37)) ino:32014 sk:ffff913e953e2e80 <-> tcp LISTEN 0 100 :::143 :::* users:(("dovecot",pid=1576,fd=38)) ino:32015 sk:ffff913b2e90a100 v6only:1 <-> Thanks!! > Alexander > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos

...0 100 *:143 *:* > > users:(("dovecot",pid=1576,fd=37)) ino:32014 sk:ffff913e953e2e80 <-> > > tcp LISTEN 0 100 :::143 :::* > > users:(("dovecot",pid=1576,fd=38)) ino:32015 sk:ffff913b2e90a100 v6only:1 > > <-> > > So port 143 is listening. Are we back to the point that your DNS or NSS > is broken so that even I think so. Everything else work, I don't get it. > > telnet localhost 143 > > fails while > > telnet 127.0.0.1 143 > > is successf...

...p6.keepfaith: 0 net.inet6.ip6.log_interval: 5 net.inet6.ip6.hdrnestlimit: 50 net.inet6.ip6.dad_count: 1 net.inet6.ip6.auto_flowlabel: 1 net.inet6.ip6.defmcasthlim: 1 net.inet6.ip6.gifhlim: 30 net.inet6.ip6.kame_version: FreeBSD net.inet6.ip6.use_deprecated: 1 net.inet6.ip6.rr_prune: 5 net.inet6.ip6.v6only: 1 net.inet6.ip6.rtexpire: 3600 net.inet6.ip6.rtminexpire: 10 net.inet6.ip6.rtmaxcache: 128 net.inet6.ip6.use_tempaddr: 0 net.inet6.ip6.temppltime: 86400 net.inet6.ip6.tempvltime: 604800 net.inet6.ip6.auto_linklocal: 1 net.inet6.ip6.prefer_tempaddr: 0 net.inet6.ip6.use_defaultzone: 0 net.inet6.ip...