From: Andrew Beverley <andy@andybev.com>
To: "Nikolay S. Rybaloff" <nowhere@hakkenden.ath.cx>
Cc: netfilter@vger.kernel.org
Subject: Re: Creating an equivalent to ESFQ using flow classifier
Date: Mon, 16 Mar 2009 23:35:38 +0000 [thread overview]
Message-ID: <8e76d4ceb304242debfb0a0c500976e3@localhost> (raw)
In-Reply-To: <1237140472.28333.10.camel@hakkenden>
> That's right, you have configured hashing based on src/dst address +
> src/dst port + protocol, which is almost classical SFQ hash. In your
> case you should try only nfct-src, which will create queues per source
> IP and service these queues fairly within htb class.
Thanks, that makes perfect sense now. I have to admit I didn't really
understand the rules I was writing!
I have tried it with just nfct-src for the ppp0 device going from the
server to the internet, and nfct-dst for the eth0 device going to the
individual machines. This seems to work a lot more as I would expect.
Thanks,
Andy Beverley
prev parent reply other threads:[~2009-03-16 23:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-15 16:29 Creating an equivalent to ESFQ using flow classifier Andrew Beverley
2009-03-15 18:07 ` Nikolay S. Rybaloff
2009-03-15 18:53 ` Tom Eastep
2009-03-16 23:35 ` Andrew Beverley [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=8e76d4ceb304242debfb0a0c500976e3@localhost \
--to=andy@andybev.com \
--cc=netfilter@vger.kernel.org \
--cc=nowhere@hakkenden.ath.cx \
/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