From: bert hubert <ahu@ds9a.nl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Ingress policing
Date: Wed, 06 Mar 2002 14:30:13 +0000 [thread overview]
Message-ID: <marc-lartc-101542510810612@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101498104311743@msgid-missing>
On Wed, Mar 06, 2002 at 03:19:02PM +0100, Rados?aw ?oboda wrote:
> Hi.
>
> I've been trying to use "The Ultimate traffic Conditioner" described in
> HOWTO and the two ingress rules at the end of the script didn't work. I've
> upgraded iproute and kernel, but it didn't help. I tried other ways to
> assume ingress policing, and i found that instead of this (not working):
So far everybody who upgraded to a newer iproute noted that the problem was
solved. Which version do you use? I've been specifically told that this
version works:
ftp://ftp.inr.ac.ru/ip-routing/iproute2-2.4.7-now-ss010824.tar.gz
> # tc qdisc add dev eth0 handle ffff: ingress
>
> i can issue:
>
> # tc qdisc add dev eth0 handle 2: parent 1: ingress
>
> which dos not produce any error. I don't know if this is all right. Please
> help me with this.
I don't think it will work either. Can you try again with the version
mentioned above?
Regards,
bert
--
http://www.PowerDNS.com Versatile DNS Software & Services
http://www.tk the dot in .tk
http://lartc.org Linux Advanced Routing & Traffic Control HOWTO
_______________________________________________
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-03-06 14:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-01 11:09 [LARTC] Ingress policing Jan Coppens
2002-03-06 14:19 ` Radosław Łoboda
2002-03-06 14:30 ` bert hubert [this message]
2002-03-07 11:17 ` Radosław Łoboda
2002-04-12 15:09 ` Jan Coppens
2002-04-14 10:19 ` bert hubert
2002-04-15 8:06 ` Jan Coppens
2002-12-28 11:32 ` [LARTC] ingress policing lartc
2002-12-28 12:02 ` Patrick McHardy
2004-01-13 22:26 ` Vinh Nguyen
2004-01-14 11:48 ` Andre Correa
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-101542510810612@msgid-missing \
--to=ahu@ds9a.nl \
--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.