From: Patrick McHardy <kaber@trash.net>
To: Dave Taht <dave.taht@gmail.com>
Cc: Jan Engelhardt <jengelh@medozas.de>,
Eric Dumazet <eric.dumazet@gmail.com>,
Netfilter Development Mailinglist
<netfilter-devel@vger.kernel.org>
Subject: Re: [RFC] ecn match ported to ipv6
Date: Thu, 09 Jun 2011 14:20:05 +0200 [thread overview]
Message-ID: <4DF0BA75.1070102@trash.net> (raw)
In-Reply-To: <BANLkTimMEBayFC2T+Y-0vTzUEyWHEsG6JQ@mail.gmail.com>
On 09.06.2011 14:15, Dave Taht wrote:
> On Thu, Jun 9, 2011 at 2:17 AM, Patrick McHardy <kaber@trash.net> wrote:
>> On 08.06.2011 22:50, Jan Engelhardt wrote:
>>> On Wednesday 2011-06-08 19:32, Patrick McHardy wrote:
>>>
>>>> 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.
>>>
>>> Moving it to xt_ecn first seems like producing a smaller patchset
>>> because you don't have to potentially duplicate the functions first. :)
>>
>> It actually already supports matching on IP header ECN bits:
>>
>> [!] --ecn-ip-ect [0..3] Match ECN codepoint in IPv4 header
>>
>
> Sorry, my bad. It's even documented as existing.
>
> So it's just a pair of convienence functions (
> --ecn-ip-ece --ecn-ip-cwr )
Yeah, that would make usage easier.
> and ipv6 iptables support for ECN that are MIA.
Sent out patches a few seconds ago.
> I'll argue that extending the blackhole-ing feature to also include ip
>
> --ecn-tcp-remove
>
> might be good... although in my testing I have not found a blackhole
> yet, they must still be out there.
That would be the ECN target, not the match.
prev parent reply other threads:[~2011-06-09 12:20 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
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 [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DF0BA75.1070102@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).