From: Patrick McHardy <kaber@trash.net>
To: Dave Taht <dave.taht@gmail.com>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
Jan Engelhardt <jengelh@medozas.de>,
Netfilter Development Mailinglist
<netfilter-devel@vger.kernel.org>
Subject: Re: [RFC] ecn match ported to ipv6
Date: Wed, 08 Jun 2011 19:32:03 +0200 [thread overview]
Message-ID: <4DEFB213.5030802@trash.net> (raw)
In-Reply-To: <BANLkTi=ORBH0q_arGbFUdjk=WMjbBz1KZg@mail.gmail.com>
On 08.06.2011 17:47, Dave Taht wrote:
> On Wed, Jun 8, 2011 at 9:01 AM, Eric Dumazet <eric.dumazet@gmail.com> wrote:
>
>> Dave Taht mentioned in bloat list that netfilter ecn match was ipv4
>> only.
>>
>> Is there any plan to make the switch from net/ipv4/netfilter/ipt_ecn.c
>> to net/netfilter/xt_ecn.c ?
>>
>> I can probably do it but not before ~ten days, so if someone is
>> interested, this will please Dave ;)
That should be a relatively quick job, I'll give it a shot while
my dinner is cooking :)
> The larger question I had was this
>
> "iptables seems to think ecn can only be looked at in TCP streams, where (for
> example), ecn bits can be copied to the outer header of a udp vpn
> stream, and marked
>
> when needed."
>
> ECN is an ip level standard, not just a tcp one.
That probably needs a new revision and is slightly more work, lets
begin by porting it to IPv6, then we can add this on top.
> http://www.ietf.org/rfc/rfc3168.txt
>
> Example of ECN on ipsec:
>
> http://huchra.bufferbloat.net/~d/veryhappynetwork.png
>
> Also ECN marking in various qdiscs like HTB as presently being discussed on
> the bloat list
>
> https://lists.bufferbloat.net/pipermail/bloat/2011-June/000555.html
I'd suggest to make this generic so other qdiscs can use it as well.
> and a truly crazy idea regarding combining DSCP with firewalling is here:
>
> https://lists.bufferbloat.net/pipermail/bloat/2011-June/000558.html
>
> To give some context as to what we've been up to regarding bufferbloat, I
> have a test lab setup with a bunch of wndr3700v2 routers at georgia tech,
> and have pushed every ecn and bloat related patch in linux head into the
> openwrt distro, and am playing with all sorts of techniques now, with
> increasingly good results.
>
> The 'uberwrt' project is in addition to the debloat-testing work
> and has various subprojects...
>
> http://www.bufferbloat.net/projects/uberwrt/wiki
>
next prev parent reply other threads:[~2011-06-08 17:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-08 15:01 [RFC] ecn match ported to ipv6 Eric Dumazet
[not found] ` <BANLkTi=ORBH0q_arGbFUdjk=WMjbBz1KZg@mail.gmail.com>
2011-06-08 15:49 ` Fwd: " Dave Taht
2011-06-08 17:32 ` Patrick McHardy [this message]
2011-06-08 20:50 ` Jan Engelhardt
2011-06-09 8:17 ` Patrick McHardy
2011-06-09 12:15 ` Dave Taht
2011-06-09 12:20 ` Patrick McHardy
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DEFB213.5030802@trash.net \
--to=kaber@trash.net \
--cc=dave.taht@gmail.com \
--cc=eric.dumazet@gmail.com \
--cc=jengelh@medozas.de \
--cc=netfilter-devel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.