From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Jan Coppens" <Jan.Coppens@intec.rug.ac.be>
Date: Thu, 13 Jun 2002 07:49:46 +0000
Subject: Re: [LARTC] Why this stupid ingress tc does not work ?
Message-Id: <marc-lartc-102395469128326@msgid-missing>
List-Id: <lartc.vger.kernel.org>
References: <marc-lartc-102392421009073@msgid-missing>
In-Reply-To: <marc-lartc-102392421009073@msgid-missing>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: lartc@vger.kernel.org

----- Original Message -----
From: "ludo" <ludovic.drolez@freealter.com>
To: <lartc@mailman.ds9a.nl>
Sent: Thursday, June 13, 2002 1:22 AM
Subject: [LARTC] Why this stupid ingress tc does not work ?


> Hi !
>
> I wanted to shape my analog modem connection so I took these two lines
> from the 'wondershaper' script:
>
> 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} burst 10k drop flowid :1
>
>
> with DEV=ppp0 and DOWNLINK$kbit.
> But, when I activate it, nothing comes back from the web, no ping.
>
> 'tc -s qdisc' gives:
>
> qdisc ingress ffff: dev ppp0 ----------------
>  Sent 0 bytes 0 pkts (dropped 0, overlimits 0)

In fact, the qdisc does work, only the output of the byte and packet count
is not implemented I guess.

Cheers,
Jan

>
> I can see the packets or ping replies with a tcpdump -i ppp0
> but the packets do not seem to reach applications !
>
> I run kernel 2.4.18... what's the problem ?
>
>
> Cheers,
>
>   Ludovic Drolez.
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>
>

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