Hi All, Is there any bug in Ingress for IMQ? I get Oops with following setup /sbin/modprobe imq iptables -I POSTROUTING -t mangle -j IMQ iptables -I PREROUTING -t mangle -j IMQ #Making imq0 enable /sbin/ip link set imq0 up #Adding root /sbin/tc qdisc del dev imq0 root #Diverting unclassified traffic to default class. /sbin/tc qdisc add dev imq0 root handle 1: htb default 1 #Default traffic class /sbin/tc class add dev imq0 parent 1:0 classid 1:1 htb rate 100mbps tc class add dev imq0 parent 1:2 classid 1:10 htb rate 50kbps ceil 50kbps tc class add dev imq0 parent 1:2 classid 1:11 htb rate 50kbps ceil 50kbps tc filter add dev imq0 protocol ip parent 1:0 prio 1 handle 800::1 u32 match ip dst 192.9.203.70 match ip sport 80 0xffff flowid 1:10 tc filter add dev imq0 protocol ip parent 1:0 prio 1 handle 800::3 u32 match ip src 192.9.203.139 match ip dport 80 0xffff flowid 1:10 Now when I do http download my system crashes when download reaches somewhere between 100K and 200K. Most surprising observation in this is system crash happens only when I do download from simultanious connection tool DAP (Download Accelarator Plus). I know in above setup one problem is there that a packet will get pass 2 from IMQ. I'm useing kernel-2.4.18 from redhat rpm and patched with imq-2.4.18.diff-10.txt, and htb3.6_2.4.17.diff Now let me clear my question why I asked Ingress... In above setup if i remove "iptables -I PREROUTING -t mangle -j IMQ" then no kernel oops. Attechment is Oops on serial-console. -- Sumit
Attachment:
2.4bug.log
Description: Binary data
