Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: "Radosław Łoboda" <p0wer@tl.krakow.pl>
To: lartc@vger.kernel.org
Subject: [LARTC] Ingress policing
Date: Wed, 06 Mar 2002 14:19:02 +0000	[thread overview]
Message-ID: <marc-lartc-101542431607990@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101498104311743@msgid-missing>

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):

# 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.

Greetz.

-- 

##########################################
#           |       p0wer        |       #
#   __      |    GG#1877248      |       #
#  (oo)     | p0wer@bojko.eu.org |       #
# / \/ \ Go away or I will replace you   #
# `V__V' with a very small shell script. #
##########################################



_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  reply	other threads:[~2002-03-06 14:19 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 [this message]
2002-03-06 14:30 ` bert hubert
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-101542431607990@msgid-missing \
    --to=p0wer@tl.krakow.pl \
    --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