From: Tadas <tadas@silvernet.homeip.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Why this stupid ingress tc does not work ?
Date: Thu, 13 Jun 2002 11:24:38 +0000 [thread overview]
Message-ID: <marc-lartc-102396777505992@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102392421009073@msgid-missing>
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ðë:
> ----- 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 ?
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-06-13 11:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-12 23:22 [LARTC] Why this stupid ingress tc does not work ? ludo
2002-06-13 7:49 ` Jan Coppens
2002-06-13 11:24 ` Tadas [this message]
2002-06-14 7:38 ` Ludovic Drolez
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-102396777505992@msgid-missing \
--to=tadas@silvernet.homeip.net \
--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.