Send inn-workers mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.isc.org/mailman/listinfo/inn-workers
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of inn-workers digest..."


Today's Topics:

   1. Re: 2.6.x "cxnsleep transfer permission denied"? (Nix)


----------------------------------------------------------------------

Message: 1
Date: Thu, 25 Jan 2018 13:56:00 +0000
From: Nix <[email protected]>
To: Russ Allbery <[email protected]>
Cc: [email protected]
Subject: Re: 2.6.x "cxnsleep transfer permission denied"?
Message-ID: <[email protected]>
Content-Type: text/plain

On 25 Jan 2018, Russ Allbery uttered the following:

> Nix <[email protected]> writes:
>
>> Speculation: is this because I'm suddenly connecting to/from all my
>> peers via their IPv6 addresses, but they only know to grant me
>> permission to read/post over IPv4? If so, it's *really annoying* that I
>> can't turn IPv6 off temporarily until my peers have been informed of my
>> IPv6 address :(
>
> The log messages are from innfeed, so just set force-ipv4 in innfeed.conf?

I'll do that for a while to get a feed back :) The question of why
exactly when I search for 'ipv4', the clearly visible 'force-ipv4' in
the innfeed manpage is not found is between me and the less(1) author!
:/

(Though my incoming feed is fubared as well, probably for the same
reason :( it doesn't help that thanks to a DNS misconfiguration half my
IPv6 servers don't have visible AAAA addresses either!)

-- 
NULL && (void)


------------------------------

Subject: Digest Footer

_______________________________________________
inn-workers mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/inn-workers

------------------------------

End of inn-workers Digest, Vol 102, Issue 4
*******************************************

Reply via email to