All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Shannon C. Dealy" <dealy@deatech.com>
To: lartc@vger.kernel.org
Subject: [LARTC] police/ingress limiting problem
Date: Sat, 14 Sep 2002 06:14:58 +0000	[thread overview]
Message-ID: <marc-lartc-103198451300774@msgid-missing> (raw)


I setup the "Ultimate Traffic Conditioner" script on one of my 56k modem
lines, and every time it effectively kills the link.  The specific problem
is the ingress filter/rate limiter lines (which was what I really wanted)

   tc qdisc add dev $DEV handle ffff: ingress
   tc filter add dev $DEV parent ffff: protocol ip prio 50 u32 match ip src \
      0.0.0.0/0 police rate ${DOWNLINK}kbit burst 10k drop flowid :1

After quite a bit of searching, I finally found another person posted this
exact problem to the list a few months ago, but the answer they got was to
try another approach.  Before I spend time trying to figure out how to
use that approach, I thought I would check if anything more has been
discovered about this.  Like the person who originally reported this, I am
also running a 2.4.18 kernel, and as soon as I activate the filter
(regardless of settings), the link is effectively dead until I remove the
filter, presumably all incoming packets are being blocked.  I have tried
many variations, including setting the rate much higher than the link can
provide (so presumably the limit will never be reached), and even
switching from "drop" to "continue" or "pass", and even in these cases,
all the data gets blocked.  Unless I am misunderstanding something here,
there would appear to be a serious bug somewhere in the kernel or tc
command.  Anyone know anything more about this?  Has anyone gotten this to
work with a 2.4.18 kernel?  If not, what is the most recent kernel and tc
command combination that does work?

Thanks for any enlightenment you can provide.

Shannon C. Dealy      |               DeaTech Research Inc.
dealy@deatech.com     |          - Custom Software Development -
                      |    Embedded Systems, Real-time, Device Drivers
Phone: (800) 467-5820 | Networking, Scientific & Engineering Applications
   or: (541) 451-5177 |                  www.deatech.com

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

                 reply	other threads:[~2002-09-14  6:14 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-103198451300774@msgid-missing \
    --to=dealy@deatech.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.