Hello to list and Patrick !
scuse me first for my bad english:)
I'm using the new IMQ code since 2 days, and it's very efficient!
but i've experimented a bad problem, that i doesn't manage to resolve.
for example I load these simple rules:
tc qdisc add dev imq0 handle 1: root htb default 1
tc class add dev imq0 parent 1: classid 1:1 htb rate 500kbit burst 30k
tc qdisc add dev imq0 parent 1:1 handle 21:0 sfq
tc filter add dev imq0 protocol ip parent 1: handle 10 fw classid 1:1
iptables -t mangle -A PREROUTING -i ppp0 -j IMQ
iptables -t mangle -A PREROUTING -i ppp0 -j MARK --set-mark 10
ip link set imq0 up
the result in the syslog is (at the first network activity)
"kernel: nf_hook: Verdict = QUEUE."
and quickly become:
"kernel: last message repeated 6 times"
the real problem is that I've experimented a silent Crash this morning
but before using IMQ this machine was rock stable (months without crash)
the only usable log of it is:
Apr 8 10:03:55 way kernel: nf_hook: Verdict = QUEUE.
Apr 8 10:04:26 way last message repeated 1533 times
Apr 8 10:05:27 way last message repeated 2982 times
Apr 8 10:06:28 way last message repeated 2808 times
Apr 8 10:07:29 way last message repeated 2837 times
Apr 8 10:08:30 way last message repeated 2841 times
Apr 8 10:09:31 way last message repeated 3008 times
>> crash here, pc completely freezed <<
Apr 8 10:21:08 way syslogd 1.4.1: restart.
Configuration:
o kernel 2.4.18 with HTB patch,
o netfilter/iptables v1.2.6a from CVS, ppp0 is kernel mode pppoe,
o iproute2-ss020116 compiled with HTB patch
So, is it a bug, or a misconfiguration ?
tanks a lot!:)
curio / a QoS addicted french guy :)
