On 11/05/15 at 06:58P, Midori Kato wrote:
> Hi Macy and Don,
>
> I am Midori. Too late to catch up this topic but this topic is interesting
> to me.
> Linux separates inbound and outbound ecn operation while RFC 3168 says that
> making hosts fail during the negotiation without ecn configuration.
>
Hi Macy and Don,
I am Midori. Too late to catch up this topic but this topic is interesting
to me.
Linux separates inbound and outbound ecn operation while RFC 3168 says that
making hosts fail during the negotiation without ecn configuration.
I think FreeBSD is probably able to distinguish inboun
On Fri, Sep 4, 2015 at 5:53 PM, Don Lewis wrote:
> On 4 Sep, K. Macy wrote:
>> By default ECN is completely disabled on FreeBSD. On Linux the default
>> is to disable it outbound (not request it) but enable it inbound
>> (accept new connections asking for it). Is there a good reason to only
>> se
On 4 Sep, K. Macy wrote:
> By default ECN is completely disabled on FreeBSD. On Linux the default
> is to disable it outbound (not request it) but enable it inbound
> (accept new connections asking for it). Is there a good reason to only
> set ECN_PERMIT on inbound connections if the system is doi
By default ECN is completely disabled on FreeBSD. On Linux the default
is to disable it outbound (not request it) but enable it inbound
(accept new connections asking for it). Is there a good reason to only
set ECN_PERMIT on inbound connections if the system is doing ECN on
outbound connections?
__
