From: Jose Luis Domingo Lopez <lartc@24x7linux.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] incoming traffic??
Date: Sat, 10 May 2003 18:05:56 +0000 [thread overview]
Message-ID: <marc-lartc-105259000802864@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105258341931128@msgid-missing>
On Saturday, 10 May 2003, at 16:15:00 +0000,
sun reflex4 wrote:
> I want to classify incoming traffic and then put them in HTB queues, is
> that possible with tc (and/or iptables)? and when yes, which chain should I
> use: PREROUTING, or INPUT?
>
You should patch your kernel to support IMQ device and configure it, as
has been said several times on this list. Check the archives.
If you are configuring Linux traffic shaping in a router for a whole net
behind it, you can avoid IMQ and shapa incoming traffic in the inner
network card, shaping outgoing traffic to your internal network.
IP packets travel through the operating system stack following a well
defined path, that you can check at:
http://www.docum.org/stef.coene/qos/kptd/
Regards.
--
Jose Luis Domingo Lopez
Linux Registered User #189436 Debian Linux Sid (Linux 2.5.69)
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-05-10 18:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-10 16:15 [LARTC] incoming traffic?? sun reflex4
2003-05-10 18:05 ` Jose Luis Domingo Lopez [this message]
2003-05-11 4:49 ` hare ram
2003-05-11 10:13 ` sun reflex4
2003-05-11 12:37 ` Graste
-- strict thread matches above, loose matches on Subject: below --
2005-10-04 9:33 [LARTC] Incoming traffic? Dominik Werder
2005-10-04 10:00 ` Andreas Klauer
2005-10-04 13:08 ` Edward Smith
2005-10-04 17:53 ` Carl-Daniel Hailfinger
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=marc-lartc-105259000802864@msgid-missing \
--to=lartc@24x7linux.com \
--cc=lartc@vger.kernel.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.