Skip to contentSkip to conversation

ingress qdisc on kernel 2.2.21 with ds8 patch

LARTC Andrei Boros 3 participants 6 messages Jul 10, 2002 – Jul 12, 2002

lore
Share & tools
lore
#0 lore raw

Since some other constraints require me to still run 2.2 kernel.
(drivers for some hardware not working under 2.4)

I tried to control the ingress traffic with the ingress qdisc with no
success whatsoever.
I got 2.2.21 kernel and installed the ds8 patch to have the ingress
qdisc too.
Recompiled, installed kernel and modules.
Recompiled tc with diffserv=y.

I tried a setup very similar to the example Edge2:

ipchains -A input -p tcp -d 0/0 20 --mark 20
ipchains -A input -p tcp -d 0/0 21 --mark 20

tc qdisc add dev eth0 handle ffff: ingress

tc filter add dev eth0 parent ffff: protocol ip prio 50 handle 20 fw police rate 256kbit burst 25k mtu 1.5k drop flowid :1

I tried uploading with a ftp client and there was no traffic limit imposed on what my box received.

tc -s qdisc ls shows all counters as 0 (zero).

I looked around for this issue and managed to find exactly my problem described in a forum at
http://www.geocrawler.com/archives/3/11111/2001/5/0/5806401/ but the message was unaswered there.

If anyone has any suggestions, they are most welcome.

Signature · 7 lines
ing. Andrei Boros
mailto:[email protected] / +40-1-303-1870
Centrul pt. Tehnologia Informatiei
Societatea Romana de Radiodifuziune
_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
#1 lore raw

May be you use ftp in passive mode, where port 20 not used

Quoted 24 lines · Andrei Boros

Since some other constraints require me to still run 2.2 kernel. (drivers for some hardware not working under 2.4)

I tried to control the ingress traffic with the ingress qdisc with no success whatsoever.
I got 2.2.21 kernel and installed the ds8 patch to have the ingress qdisc too.
Recompiled, installed kernel and modules.
Recompiled tc with diffserv=y.

I tried a setup very similar to the example Edge2:

ipchains -A input -p tcp -d 0/0 20 --mark 20
ipchains -A input -p tcp -d 0/0 21 --mark 20

tc qdisc add dev eth0 handle ffff: ingress

tc filter add dev eth0 parent ffff: protocol ip prio 50 handle 20 fw police rate 256kbit burst 25k mtu 1.5k drop flowid :1

I tried uploading with a ftp client and there was no traffic limit imposed on what my box received.

Quoted 18 lines

tc -s qdisc ls shows all counters as 0 (zero).

I looked around for this issue and managed to find exactly my problem described in a forum at
http://www.geocrawler.com/archives/3/11111/2001/5/0/5806401/ but the message was unaswered there.

If anyone has any suggestions, they are most welcome.

Signature · 7 lines
ing. Andrei Boros
mailto:[email protected] / +40-1-303-1870
Centrul pt. Tehnologia Informatiei
Societatea Romana de Radiodifuziune
_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

-----------------------------------
mailto:[email protected]
BR
Alexey Talikov
FORTEK
-----------------------------------

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

#2 lore raw
In reply to Andrei Boros
Quoted 3 lines · Alexey Talikov

May be you use ftp in passive mode, where port 20 not used

No, I set the client not to use passive mode, and confirmed it with tcpdump. If it were a protocol/port specific thing I'd dig more in that direction.
And the statistic counters are on zero at all times.
If it were passive mode, why didn't the ingress capture the ftp session packets on port 21???

I even set firewall to mark everything and the filter directs it to ingress. Nothing happened.

Quoted 52 lines
Quoted 32 lines

Since some other constraints require me to still run 2.2 kernel. (drivers for some hardware not working under 2.4)

I tried to control the ingress traffic with the ingress qdisc with no success whatsoever.
I got 2.2.21 kernel and installed the ds8 patch to have the ingress qdisc too.
Recompiled, installed kernel and modules.
Recompiled tc with diffserv=y.

I tried a setup very similar to the example Edge2:

ipchains -A input -p tcp -d 0/0 20 --mark 20
ipchains -A input -p tcp -d 0/0 21 --mark 20

tc qdisc add dev eth0 handle ffff: ingress

tc filter add dev eth0 parent ffff: protocol ip prio 50 handle 20 fw police rate 256kbit burst 25k mtu 1.5k drop flowid :1

I tried uploading with a ftp client and there was no traffic limit imposed on what my box received.

tc -s qdisc ls shows all counters as 0 (zero).

I looked around for this issue and managed to find exactly my problem described in a forum at
http://www.geocrawler.com/archives/3/11111/2001/5/0/5806401/ but the message was unaswered there.

If anyone has any suggestions, they are most welcome.

Quoted 9 lines

--
ing. Andrei Boros
mailto:[email protected] / +40-1-303-1870
Centrul pt. Tehnologia Informatiei
Societatea Romana de Radiodifuziune
_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

-----------------------------------
mailto:[email protected]
BR
Alexey Talikov
FORTEK
-----------------------------------

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

Signature · 7 lines
ing. Andrei Boros
mailto:[email protected] / +40-1-303-1870
Centrul pt. Tehnologia Informatiei
Societatea Romana de Radiodifuziune
_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
#3 lore raw
In reply to Andrei Boros

Hello,

Quoted 4 lines · Andrei Boros

I tried to control the ingress traffic with the ingress qdisc with no
success whatsoever.
I got 2.2.21 kernel and installed the ds8 patch to have the ingress
qdisc too.

You probably have to apply more fixes to be sure something
will not break. I just uploaded some fixes for the 2.2 code as it appears nobody have the time to deal with it:

http://www.linuxvirtualserver.org/~julian/#qos-2.2

To all: if there is a good place for such fixes please let
me know.

Quoted 4 lines

Recompiled, installed kernel and modules.
Recompiled tc with diffserv=y.

I tried a setup very similar to the example Edge2:

Not "very similar" :) The bug is exactly in the
differences :)

	mark here is in decimal (may be can be hex with 0x20):
Quoted 4 lines

ipchains -A input -p tcp -d 0/0 20 --mark 20
ipchains -A input -p tcp -d 0/0 21 --mark 20

tc qdisc add dev eth0 handle ffff: ingress

"handle 20" here is in hex:

Quoted 2 lines

tc filter add dev eth0 parent ffff: protocol ip prio 50 handle 20 fw police rate 256kbit burst 25k mtu 1.5k drop flowid :1

if you somewhere use fwmark in ip rules, the fwmark
there is again in hex. Make sure all values match according to their representation, i.e. 20 in dec is different from 20 in hex.

Quoted 1 line

If anyone has any suggestions, they are most welcome.

Regards

--
Julian Anastasov <[email protected]>

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

#4 lore raw
In reply to Andrei Boros
Quoted 6 lines · Julian Anastasov

You probably have to apply more fixes to be sure something
will not break. I just uploaded some fixes for the 2.2 code as it appears nobody have the time to deal with it:

http://www.linuxvirtualserver.org/~julian/#qos-2.2

I'll try them asap.

Quoted 11 lines

To all: if there is a good place for such fixes please let
me know.

Quoted 4 lines

Recompiled, installed kernel and modules.
Recompiled tc with diffserv=y.

I tried a setup very similar to the example Edge2:

Not "very similar" :) The bug is exactly in the
differences :)

I also tried filtering using the u32 match ip dport ... same result. I even tried u32 match ip (anything ip), same result.

Quoted 9 lines
        mark here is in decimal (may be can be hex with 0x20):
Quoted 4 lines

ipchains -A input -p tcp -d 0/0 20 --mark 20
ipchains -A input -p tcp -d 0/0 21 --mark 20

tc qdisc add dev eth0 handle ffff: ingress

"handle 20" here is in hex:

Quoted 7 lines
Quoted 2 lines

tc filter add dev eth0 parent ffff: protocol ip prio 50 handle 20 fw police rate 256kbit burst 25k mtu 1.5k drop flowid :1

if you somewhere use fwmark in ip rules, the fwmark
there is again in hex. Make sure all values match according to their representation, i.e. 20 in dec is different from 20 in hex.

Sorry. However, I don't know of any place where these differences are explained clearly.

Signature · 7 lines
ing. Andrei Boros
mailto:[email protected] / +40-1-303-1870
Centrul pt. Tehnologia Informatiei
Societatea Romana de Radiodifuziune
_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
#5 lore raw
In reply to Andrei Boros

Hello,

Quoted 2 lines · Andrei Boros

I also tried filtering using the u32 match ip dport ... same result. I even tried u32 match ip (anything ip), same result.

This is another issue, may be for howto:12.1.2. Bert promised
to clarify them in the Howto:

http://mailman.ds9a.nl/pipermail/lartc/2001q4/thread.html

Search for "tc: u32 match in nexthdr not working?"

In short, dport and sport do not always match, eg.
for packets with IP Options. Try different examples. May be your settings are incorrect.

Quoted 2 lines

Sorry. However, I don't know of any place where these differences are explained clearly.

Huh. I don't want to start new howto :)

Regards

--
Julian Anastasov <[email protected]>

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