All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Schiffbauer <marc.schiffbauer@links2linux.de>
To: LKML <linux-kernel@vger.kernel.org>
Cc: bert hubert <ahu@ds9a.nl>
Subject: Re: ingress policing still not working in 2.4?
Date: Sun, 10 Feb 2002 09:55:22 +0100	[thread overview]
Message-ID: <20020210085521.GA2153@links2linux.de> (raw)
In-Reply-To: <20020209114529.GA6753@links2linux.de> <20020210005636.A21350@outpost.ds9a.nl>
In-Reply-To: <20020210005636.A21350@outpost.ds9a.nl>

* bert hubert schrieb am 10.02.02 um 00:56 Uhr:
> On Sat, Feb 09, 2002 at 11:48:50AM +0000, Marc Schiffbauer wrote:
> > RTNETLINK answers: No such file or directory
> 
> Get a newer tc, it appears to fix this problem.
> 

Yes, the debian unstable package did it, thanks.


> > Before that I successfully did this:
> > # install root CBQ
> > DEV=ppp0
> > UPLINK=100
> > DOWNLINK=750
> > tc qdisc add dev $DEV root handle 1: cbq avpkt 1000 bandwidth 100mbit
> 
> The WonderShaper! 
> 
What?

Ok, I changed the 10mbit to 100mbit because this is my LAN speed
here. I first didn't see, that the root handle is per device.

But
tc qdisc add dev $DEV root handle 1: cbq avpkt 1000 bandwidth 10mbit

is exactly the line from your HOWTO. So what will be proper values
for my DSL Line with 128kbit up and 768kbit downstream?

Regards
-Marc

-- 
BUGS My programs  never  have  bugs.  They  just  develop  random
     features.  If you discover such a feature and you want it to
     be removed: please send an email to bug@links2linux.de 

  reply	other threads:[~2002-02-10  8:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-09 11:45 ingress policing still not working in 2.4? Marc Schiffbauer
2002-02-09 23:56 ` bert hubert
2002-02-10  8:55   ` Marc Schiffbauer [this message]
2002-02-10 11:11     ` bert hubert

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=20020210085521.GA2153@links2linux.de \
    --to=marc.schiffbauer@links2linux.de \
    --cc=ahu@ds9a.nl \
    --cc=linux-kernel@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.