From: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] tc -s qdisc questions
Date: Mon, 18 May 2015 09:09:03 +0100 [thread overview]
Message-ID: <55599E1F.1070105@darbyshire-bryant.me.uk> (raw)
In-Reply-To: <alpine.DEB.2.02.1505180743070.9487@uplift.swm.pp.se>
[-- Attachment #1: Type: text/plain, Size: 1497 bytes --]
On 18/05/15 06:46, Mikael Abrahamsson wrote:
> On Sun, 17 May 2015, Kevin Darbyshire-Bryant wrote:
>
>> Thanks Mikael - some ECN tweakage in progress. I'll see which bits
>> of the Internet I use break :-)
>
> I have been running this on my macbook for almost 2 years (since I got
> it):
>
> $ cat /etc/sysctl.conf
> net.inet.tcp.ecn_initiate_out=1
> net.inet.tcp.ecn_negotiate_in=1
>
> and this on my linux server for 5+ years:
>
> $ cat /etc/sysctl.conf | grep -i ecn
> net.ipv4.tcp_ecn = 1
>
> I used the same on my previous Ubuntu based laptop for 5+ years.
>
> I have yet to encounter any ECN related breakage. I have had
> significant problems with IPv6 PMTUD blackholing, but no ECN related
> problems. I had ECN related problems back in 2001 (or whenever it
> was) when Linux first introduced it due to a lot of firewalls being
> very paranoid about it, but then I turned it back on again 5-7 years
> ago and by then all problems were gone.
>
That's good to know :-)
And for those struggling (ok just me then) to get ecn to survive a
reboot on OpenWrt despite playing with sysctl.conf, instead add "option
tcp_ecn '1'" in /etc/config/firewall something like:
config defaults
option syn_flood '1'
option input 'ACCEPT'
option output 'ACCEPT'
option forward 'REJECT'
option drop_invalid '1'
option tcp_ecn '1'
Kevin (being that 'better built idiot' since 1971) :-)
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4791 bytes --]
prev parent reply other threads:[~2015-05-18 8:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-14 22:22 Kevin Darbyshire-Bryant
2015-05-14 23:37 ` Jonathan Morton
2015-05-14 23:41 ` Dave Taht
2015-05-15 8:16 ` Kevin Darbyshire-Bryant
2015-05-15 8:55 ` Mikael Abrahamsson
2015-05-15 16:45 ` Dave Taht
2015-05-17 20:23 ` Kevin Darbyshire-Bryant
2015-05-18 5:46 ` Mikael Abrahamsson
2015-05-18 8:09 ` Kevin Darbyshire-Bryant [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55599E1F.1070105@darbyshire-bryant.me.uk \
--to=kevin@darbyshire-bryant.me.uk \
--cc=bloat@lists.bufferbloat.net \
--cc=swmike@swm.pp.se \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox