Skip to contentSkip to conversation

Ingress qdisc problems

LARTC Claudio Neves 2 participants 3 messages Dec 21, 2001 – Dec 22, 2001

lore
Share & tools
lore
#0 lore raw

Hello,

I tried ingress qdisc with kernel 2.4.16, and it works very well.
But when I tried it with kernel 2.2.20, with diffserv-8 patches applied (and latest HTB too), it doesn't work. It seems that the filter don't classify the packets to the ingress queue.

Here follows the simplest setup I tried:

#!/bin/bash

tc qdisc del dev eth0 root 2> /dev/null > /dev/null tc qdisc del dev eth0 ingress 2> /dev/null > /dev/null

tc qdisc add dev eth0 handle ffff: ingress

tc filter add dev eth0 parent ffff: protocol ip prio 0 u32 match ip src \
0.0.0.0/0 police rate 1000kbit burst 90k mtu 1500 drop
flowid :1

This doesn't seems to limit any traffic, nor the traffic goes to the ingress qdisc.

root@gw ~# tc -s qdisc
qdisc ingress ffff: dev eth0 ----------------
Sent 0 bytes 0 pkts (dropped 0, overlimits 0)

Do you have any clues on what I am doing wrong ?! I'm using iproute2 001007.

Thanks for your attention,

Claudio Neves

_______________________________________________________________________________________________
Yahoo! GeoCities
Tenha seu lugar na Web. Construa hoje mesmo sua home page no Yahoo! GeoCities. É fácil e grátis!
http://br.geocities.yahoo.com/

_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/

#1 lore raw
Quoted 8 lines · Claudio Neves

Hello,

I tried ingress qdisc with kernel 2.4.16, and it works very well.
But when I tried it with kernel 2.2.20, with diffserv-8 patches applied (and latest HTB too), it doesn't work. It seems that the filter don't classify the packets to the ingress queue.

It may be that the diffserv patches don't work too well.. you might want to mail their author, Werner I think.

Quoted 1 line

This doesn't seems to limit any traffic, nor the traffic

In 2.4 the ingress qdisc also doesn't match any packets according to the stats- it's a bug that Jamal has fixed, should go in somewhere soon.

Regards,

bert

Signature · 8 lines
http://www.PowerDNS.com          Versatile DNS Software & Services
http://www.tk                              the dot in .tk
Netherlabs BV / Rent-a-Nerd.nl           - Nerd Available -
Linux Advanced Routing & Traffic Control: http://ds9a.nl/lartc

_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
#2 lore raw
In reply to Claudio Neves

--- bert hubert <[email protected]> escreveu: > On Fri, Dec 21,

Quoted 11 lines

It may be that the diffserv patches don't work too well.. you might want to
mail their author, Werner I think.

Quoted 1 line

This doesn't seems to limit any traffic, nor the

traffic

In 2.4 the ingress qdisc also doesn't match any packets according to the
stats- it's a bug that Jamal has fixed, should go in somewhere soon.

You are right, even in 2.4 the ingress qdisc doesn't show any packets on the stats. But filter stats are correct, the counter increments.
On 2.2, nothing works.

I'll try posting on the diffserv mailing list. Thanks for your attention, and for your great work writing the HOWTO!

Claudio Neves.

_______________________________________________________________________________________________
Yahoo! GeoCities
Tenha seu lugar na Web. Construa hoje mesmo sua home page no Yahoo! GeoCities. É fácil e grátis!
http://br.geocities.yahoo.com/

_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/