From: Michal Soltys <soltys@ziu•info>
To: "Michal Kubeček" <mkubecek@suse•cz>
Cc: netdev@vger•kernel.org,
"John A. Sullivan III" <jsullivan@opensourcedevel•com>
Subject: Re: tc filter mask for ACK packets off?
Date: Wed, 04 Jan 2012 01:01:21 +0100 [thread overview]
Message-ID: <4F0396D1.9030303@ziu.info> (raw)
In-Reply-To: <21734335.uCtjXOcSpA@alaris>
On 12-01-03 08:31, Michal Kubeček wrote:
> On Saturday 31 of December 2011 21:30EN, John A. Sullivan III wrote:
>> <cut>
>
> However, by a "ACK only" packet (worth prioritizing), I would rather
> understand a packet with ACK flag without any payload, not a packet with
> ACK as the only flag. For many TCP connections, all packets except
> initial SYN and SYN-ACK and two FIN packets have ACK as the only flag.
> So my guess is you should rather prioritize all TCP packets with no
> application layer data.
>
> Michal Kubecek
In context of the above - xtables-addons provide length2 match which
(possibly paired with other iptables matches) gives excellent control
for such tasks.
next prev parent reply other threads:[~2012-01-04 0:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-01 2:30 tc filter mask for ACK packets off? John A. Sullivan III
2012-01-03 7:31 ` Michal Kubeček
2012-01-03 9:36 ` Dave Taht
2012-01-03 10:40 ` [RFC] SFQ planned changes Eric Dumazet
2012-01-03 12:07 ` Dave Taht
2012-01-03 12:50 ` Eric Dumazet
2012-01-03 16:08 ` Eric Dumazet
2012-01-03 23:57 ` Dave Taht
2012-01-04 0:14 ` Eric Dumazet
2012-01-04 7:56 ` Dave Taht
2012-01-04 8:17 ` Eric Dumazet
2012-01-03 12:18 ` tc filter mask for ACK packets off? John A. Sullivan III
2012-01-03 12:32 ` Eric Dumazet
2012-01-03 12:45 ` John A. Sullivan III
2012-01-03 13:00 ` Dave Taht
2012-01-03 17:57 ` John A. Sullivan III
2012-01-04 0:01 ` Michal Soltys [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-01-01 2:30 John A. Sullivan III
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=4F0396D1.9030303@ziu.info \
--to=soltys@ziu$(echo .)info \
--cc=jsullivan@opensourcedevel$(echo .)com \
--cc=mkubecek@suse$(echo .)cz \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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