HTB on IMQ
Hello,
could somebody check my IMQ+HTB config? Is it OK?/usr/local/sbin/tc qdisc add dev imq0 root handle 1: htb default 10 /usr/local/sbin/tc class add dev imq0 parent 1: classid 1:1 htb rate 1920kbit quantum 500/usr/local/sbin/tc class add dev imq0 parent 1:1 classid 1:60 htb rate 1024kbit ceil 1024kbit/usr/local/sbin/tc qdisc add dev imq0 parent 1:60 handle 60: pfifo limit 2 /usr/local/sbin/tc class add dev imq0 parent 1:1 classid 1:40 htb rate 128kbit ceil 128kbit/usr/local/sbin/tc qdisc add dev imq0 parent 1:40 handle 40: pfifo limit 2 /usr/local/sbin/tc class add dev imq0 parent 1:1 classid 1:10 htb rate 704kbit ceil 1920kbit/usr/local/sbin/tc qdisc add dev imq0 parent 1:10 handle 10: pfifo limit 2 /usr/local/sbin/tc class add dev imq0 parent 1:1 classid 1:30 htb rate 128kbit ceil 128kbit/usr/local/sbin/tc qdisc add dev imq0 parent 1:30 handle 30: pfifo limit 2 /usr/local/sbin/tc class add dev imq0 parent 1:1 classid 1:20 htb rate 64kbit ceil 64kbit/usr/local/sbin/tc qdisc add dev imq0 parent 1:20 handle 20: pfifo limit 2 /usr/local/sbin/tc class add dev imq0 parent 1:1 classid 1:50 htb rate 128kbit ceil 128kbit/usr/local/sbin/tc qdisc add dev imq0 parent 1:50 handle 50: pfifo limit 2 /usr/local/sbin/tc filter add dev imq0 protocol ip parent 1:0 u32 match ip dst 192.168.102.128/25 flowid 1:60/usr/local/sbin/tc filter add dev imq0 protocol ip parent 1:0 u32 match ip dst 192.168.101.42 flowid 1:40/usr/local/sbin/tc filter add dev imq0 protocol ip parent 1:0 u32 match ip dst 192.168.100.0/27 flowid 1:10/usr/local/sbin/tc filter add dev imq0 protocol ip parent 1:0 u32 match ip dst 192.168.1.170 flowid 1:10/usr/local/sbin/tc filter add dev imq0 protocol ip parent 1:0 u32 match ip dst 192.168.101.38 flowid 1:30/usr/local/sbin/tc filter add dev imq0 protocol ip parent 1:0 u32 match ip dst 192.168.101.34 flowid 1:20/usr/local/sbin/tc filter add dev imq0 protocol ip parent 1:0 u32 match ip dst 192.168.101.46 flowid 1:50/usr/local/sbin/iptables -t mangle -A PREROUTING -i eth2 -j IMQ --todev 0 /usr/local/sbin/iptables -t mangle -A POSTROUTING -o eth2 -j IMQ --todev 0
(I;m running on linux-2.4.20 with IMQ patch + iptables-1.2.7a with IMQ and patched tc).
Why am I asking for this?
I got kernel panic and I don't know what is wrong in my config/system.
Thanks in advance,
Thomas
_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
Quoted 4 lines · Thomas Jalsovsky
could somebody check my IMQ+HTB config? Is it OK?
Why am I asking for this?
I got kernel panic and I don't know what is wrong in my config/system.
Kernel panics are not the consequence of bad configuration on the user
or administrator part (except attempts to overflow some kernel buffer to do Very Bad Things (tm)).
If the kernel crashes, process the resulting panic() through ksymoops to decode the functions and symbols, and post it to the appropiate mailing list. It will be a bug from some developer, not you :-)
Hope it helps.
Signature · 5 lines
Jose Luis Domingo Lopez Linux Registered User #189436 Debian Linux Woody (Linux 2.4.20-xfs) _______________________________________________ LARTC mailing list / [email protected] http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
Quoted 7 lines · Jose Luis Domingo Lopez
Quoted 4 lines · Thomas Jalsovsky
could somebody check my IMQ+HTB config? Is it OK?
Why am I asking for this?
I got kernel panic and I don't know what is wrong in my config/system.
Quoted 7 lines
Kernel panics are not the consequence of bad configuration on the useror administrator part (except attempts to overflow some kernel buffer to do Very Bad Things (tm)).
If the kernel crashes, process the resulting
panic()through ksymoops to decode the functions and symbols, and post it to the appropiate mailing list. It will be a bug from some developer, not you :-)
The problem source has been found:/usr/local/sbin/iptables -t mangle -A PREROUTING -i eth2 -j IMQ --todev 0 /usr/local/sbin/iptables -t mangle -A POSTROUTING -o eth2 -j IMQ --todev 0
this doesn't work and causes kernel panic. Unfortunately I'm not a kernel hacker but I think this problem is easily reproducable.
My goal is to have one queue to achive a global traffic shaping e.g. to have a bandwidth for ingress and egress traffic in one. 2 IMQ's don't solve the problem while it is not possible to connect them into one...
Is the shaper configuration (one IMQ for ingress and eggress traffic from the same physical interface) WRONG or simple it is a kernel bug?
Thanks in advance,
Thomas
_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
Quoted 2 lines · Thomas Jalsovsky
Is the shaper configuration (one IMQ for ingress and eggress traffic from the same physical interface) WRONG or simple it is a kernel bug?
It is wrong. You must have separate imq devices for ingress and egress.
i.e.
modprobe imq numdevs=2
iptables -t mangle -A PREROUTING -i eth1 -j IMQ --todev 0 iptables -t mangle -A POSTROUTING -o eth1 -j IMQ --todev 1
Zdravim/Regards
Vladimir Smelhaus
_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
Quoted 6 lines · Vladimir Smelhaus
Quoted 2 lines
Is the shaper configuration (one IMQ for ingress and eggress traffic from the same physical interface) WRONG or simple it is a kernel bug?
It is wrong. You must have separate imq devices for ingress and egress.
Maybe the syntax is wrong, but in no case an error like this should give you a very worrying panic(). It seems a IMQ bug triggered by an incorrect use, and as such it should be reported to the IMQ maintainer.
Hope it helps.
Signature · 5 lines
Jose Luis Domingo Lopez Linux Registered User #189436 Debian Linux Woody (Linux 2.4.20-xfs) _______________________________________________ LARTC mailing list / [email protected] http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/