From: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2005@gmx.net>
To: Maciej Soltysiak <solt@dns.toxicfilms.tv>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: [PATCH] new 'tcpack' match
Date: Mon, 04 Apr 2005 16:15:43 +0200 [thread overview]
Message-ID: <42514C0F.4000605@gmx.net> (raw)
In-Reply-To: <5810131003.20050404153025@dns.toxicfilms.tv>
Maciej Soltysiak schrieb:
>>I aim to fix this all with one simple netfilter match which can give an
>>answer with simple arithmetics in one go instead of matching against a
>>preconfigured list of possible values one by one.
>
> Right.
>
> I agree the best way to go would be to extend the tcp match with
> the proposed semantics:
> --datalen [!] A[,B:C[,D]]
>
>
> It also might be useful to match the sole header length.
> --headerlen [!] A[,B:C[,D]]
>
> And the lenght of tcp+data
>
> --len
>
> Possibly the similar for udp:
> --datalen, --headerlen, --len
>
> And ICMP:
> --datalen, --len (icmp headers have fixed size)
Could we do this in a generic way? I'm currently rewriting the iptables
ACCOUNT target and it could benefit from that as well.
I'd need:
- length of whole IP packet
- length of layer 2 frame
Perhaps a generic prefix for all "length" options is appropriate?
--len-header-ip
--len-data-ip
--len-full-ip
--len-header-tcp
--len-data-tcp
--len-full-tcp
--len-header-ether
--len-data-ether
--len-full-ether
etc.
I realize that some of the options above don't make that much sense,
but you get the idea.
Regards,
Carl-Daniel
--
http://www.hailfinger.org/
next prev parent reply other threads:[~2005-04-04 14:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-27 5:33 [PATCH] new 'tcpack' match Jonas Berlin
2005-03-28 14:06 ` Jonas Berlin
2005-04-03 18:15 ` Patrick McHardy
2005-04-03 21:30 ` Re[2]: " Maciej Soltysiak
2005-04-04 0:04 ` Jonas Berlin
2005-04-04 13:30 ` Re[2]: " Maciej Soltysiak
2005-04-04 14:15 ` Carl-Daniel Hailfinger [this message]
2005-04-11 11:26 ` Jonas Berlin
2005-04-11 13:09 ` Jonas Berlin
2005-04-19 13:13 ` Carl-Daniel Hailfinger
2005-04-03 23:36 ` Jonas Berlin
2005-04-03 23:51 ` Phil Oester
2005-04-04 0:07 ` Jonas Berlin
2005-04-04 0:52 ` Phil Oester
2005-04-04 3:42 ` Patrick McHardy
2005-04-11 12:11 ` Jonas Berlin
2005-04-17 14:36 ` 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=42514C0F.4000605@gmx.net \
--to=c-d.hailfinger.devel.2005@gmx.net \
--cc=netfilter-devel@lists.netfilter.org \
--cc=solt@dns.toxicfilms.tv \
/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.