From mboxrd@z Thu Jan  1 00:00:00 1970
From: Tadas <tadas@silvernet.homeip.net>
Date: Thu, 13 Jun 2002 11:24:38 +0000
Subject: Re: [LARTC] Why this stupid ingress tc does not work ?
Message-Id: <marc-lartc-102396777505992@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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
To: lartc@vger.kernel.org

Hi,

I suggest you to use IMQ device. This makes possible to shape & queue
incomiong trafic.

Bye,
Tadas

Thu, Jun 13, 2002 at 09:49:46AM +0200, Jan Coppens ra=F0=EB:
> ----- 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 ?
>=20
>=20
> > 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=3Dppp0 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)
>=20
> In fact, the qdisc does work, only the output of the byte and packet count
> is not implemented I guess.
>=20
> Cheers,
> Jan
>=20
> >
> > 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 ?

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