From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] ingress and egress
Date: Tue, 21 May 2002 05:27:34 +0000 [thread overview]
Message-ID: <marc-lartc-102195891016672@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102194476409224@msgid-missing>
On Tuesday 21 May 2002 03:31, hanhbnetfilter wrote:
> ingress can be used to control the incoming packet,
> such as:
> tc qdisc add dev eth0 handle ffff: ingress
> tc filter add dev eth0 parent ffff: protocol ip prio 5
> u32 match ip src 172.16.1.11 police rate 10kbit burst
> 10k drop flowid :1
> tc filter add dev eth0 parent ffff: protocol ip prio 5
>
> u32 match ip src 172.16.1.22 police rate 10kbit burst
> 10k drop flowid :2
> first ,I do not sure these method can use class(could
> it do? I tested it can not do). if it can do it
> ,please give me a example.
Ingress qdisc is classless.
> second, rate can not be shared, if i want to control
> the incoming packet rate not throug egress qdisc, and
> the rate can be shared, please tell me how can i do.
You can use use the imq device. You can redirect packets (incoming and
outgoing) to this device. And you can attach CBQ or HTB to this device. A
link can be found on www.docum.org under faq.
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.openprojects.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-05-21 5:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-21 1:31 [LARTC] ingress and egress hanhbnetfilter
2002-05-21 5:27 ` Stef Coene [this message]
2002-05-21 5:44 ` Alexey Talikov
2002-05-22 2:29 ` hanhbnetfilter
2002-05-22 3:22 ` Patrick McHardy
2002-05-22 6:15 ` Alexey Talikov
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-102195891016672@msgid-missing \
--to=stef.coene@docum.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox