All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonas Berlin <xkr47@outerspace.dyndns.org>
To: Patrick McHardy <kaber@trash.net>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: [PATCH] new 'tcpack' match
Date: Mon, 11 Apr 2005 12:11:59 +0000	[thread overview]
Message-ID: <425A698F.6080703@outerspace.dyndns.org> (raw)
In-Reply-To: <425032D5.2010302@trash.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Quoting Patrick McHardy on 2005-04-03 18:15 UTC:

|> ~  iptables -A INPUT -p tcp -m tcpack --tcpack -j CLASSIFY 1:10
|
| I can see that it would be useful, given all the half-working ACK
| matching rules for shaping floating around, but we already a tcp
| match, so it should be done in there, and, if possible, kept a little
| bit more generic. Perhaps a data-len match option.

Should I make a new revision of the tcp match in order not to break
binary compatibility?

- --
- - xkr47
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFCWmmNxyF48ZTvn+4RAps7AKC2Bii7ZaWYecGwYgPQ8xJxmgLWqgCfRucE
PajDstxPkhhzN3q17+hXzfA=
=Gsrz
-----END PGP SIGNATURE-----

  parent reply	other threads:[~2005-04-11 12:11 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
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 [this message]
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=425A698F.6080703@outerspace.dyndns.org \
    --to=xkr47@outerspace.dyndns.org \
    --cc=kaber@trash.net \
    --cc=netfilter-devel@lists.netfilter.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.