From: Mihamina Rakotomandimby <mihamina@gulfsat.mg>
To: netdev@vger.kernel.org
Subject: Re: tc download always to "default" [solved]
Date: Tue, 23 Mar 2010 10:02:07 +0300 [thread overview]
Message-ID: <20100323100207.705ecef8@pbmiha.malagasy.com> (raw)
In-Reply-To: <20100322143113.GA23778@wolff.to>
> Bruno Wolff III <bruno@wolff.to> :
>> My problem is all the traffic is caught by "classid 1:10", the
>> default class.
>> Nothing is trapped by "classid 1:301" -> "classid 1:426"
>> At a first glance, would you see something wrong in these?
>I took a quick look and didn't see anything obvious. But I haven't
>played with this stuff for a while and my scripts were set up a bit
>differently.
>How are you checking that everything is ending up in the default class?
1°) As I wrote my rules, each IP address has one handler.
I use this script to display UP and DOWN traffic for the handler in $1:
#!/bin/sh
INIF=eth1
OUTIF=ifb0
RATEIN=$(tc -s -d class show dev $INIF \
| egrep -A 5 "class htb 1:$1 " \
| egrep "rate .+ backlog" \
| awk '{print $2}')
RATEOUT=$(tc -s -d class show dev $OUTIF \
| egrep -A 5 "class htb 1:$1 " \
| egrep "rate .+ backlog" \
| awk '{print $2}')
echo $RATEIN
echo $RATEOUT
I launch it like this:
# get-bw.sh $NNN
Where $NNN is the handler.
When I launch it, I see "0bit" for IN traffic, that means nothing is
trapped.
When I launch it with the handler of the default, I see much traffic.
2°) When varying the "default" allocated bandwidth, I see in my charts
it is the one seen.
>I remember there is a command that tells you how much stuff is ending
> up getting handled by the different qdiscs. Is that what you are doing
> or are you just assuming that's what's happening because traffic isn't
> being limited the way you expect?
Anyway, I solved my problem:
The LAN interface is "eth1" but there is a tunnel "tun0" coupled to it
(I use coova chilli access point).
Just to test, I switched to "tun0" and it suddenly worked.
In all the rules I gave, just replacing "eth1" with "tun0" made it!
(What a dumb I am...)
Thanks for everything.
--
Architecte Informatique chez Blueline/Gulfsat:
Administration Systeme, Recherche & Developpement
+261 34 29 155 34 / +261 33 11 207 36
parent reply other threads:[~2010-03-23 7:02 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20100322143113.GA23778@wolff.to>]
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=20100323100207.705ecef8@pbmiha.malagasy.com \
--to=mihamina@gulfsat.mg \
--cc=netdev@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