From: Gavin Hamill <gdh@acentral.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: Guaranteeing bandwidth through netfilter-based router?
Date: Fri, 7 Jan 2005 08:48:09 +0000 [thread overview]
Message-ID: <200501070848.09790.gdh@acentral.co.uk> (raw)
In-Reply-To: <1105064717.7100.78.camel@localhost>
On Friday 07 January 2005 02:25, John A. Sullivan III wrote:
> Not really, there are pertinent elements of netfilter. Linux will to
> some rudimentary traffic shaping based upon the TOS bits. One can
> change those in the mangle table. Set the VoIP packets as best as you
> can identify them with TOS of minimize-delay - John
Interesting stuff - I didn't know the kernel itself would prioritise packets
simply by having these bits set, I thought they only existed so that some
upstream router / ISP could manage them.
Cheers,
Gavin.
next prev parent reply other threads:[~2005-01-07 8:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-06 20:39 Guaranteeing bandwidth through netfilter-based router? Rick Mann
2005-01-06 22:26 ` Gavin Hamill
2005-01-07 2:25 ` John A. Sullivan III
2005-01-07 8:48 ` Gavin Hamill [this message]
2005-01-07 16:26 ` Michael P. Soulier
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=200501070848.09790.gdh@acentral.co.uk \
--to=gdh@acentral.co.uk \
--cc=netfilter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox