All of lore.kernel.org
 help / color / mirror / Atom feed
* [LARTC] RE: Oops with IMQ Ingress
@ 2002-07-29 14:39 Sumit Pandya
  0 siblings, 0 replies; only message in thread
From: Sumit Pandya @ 2002-07-29 14:39 UTC (permalink / raw)
  To: lartc

[-- Attachment #1: Type: text/plain, Size: 4081 bytes --]

Hi All,
	One more result with my setup. Here is my all command lines with more
details
my client IP is 192.9.203.70
IP on linux router	192.9.203.139 and xxx.xxx.xxx.xxx

# iptables -n -t nat -L -v
Chain PREROUTING (policy ACCEPT 245 packets, 42668 bytes)
 pkts bytes target     prot opt in     out     source
destination

Chain POSTROUTING (policy ACCEPT 14 packets, 1279 bytes)
 pkts bytes target     prot opt in     out     source
destination
   10   488 MASQUERADE  all  --  *      eth1    192.9.203.0/24
0.0.0.0/0

Chain OUTPUT (policy ACCEPT 19 packets, 1963 bytes)
 pkts bytes target     prot opt in     out     source
destination


# iptables -n -t mangle -L -v
Chain PREROUTING (policy ACCEPT 6917 packets, 4711K bytes)
 pkts bytes target     prot opt in     out     source
destination
   12   569 IMQ        all  --  *      *       0.0.0.0/0
0.0.0.0/0          IMQ: todev 0

Chain INPUT (policy ACCEPT 1419 packets, 118K bytes)
 pkts bytes target     prot opt in     out     source
destination

Chain FORWARD (policy ACCEPT 5356 packets, 4575K bytes)
 pkts bytes target     prot opt in     out     source
destination

Chain OUTPUT (policy ACCEPT 824 packets, 67098 bytes)
 pkts bytes target     prot opt in     out     source
destination

Chain POSTROUTING (policy ACCEPT 6191 packets, 4644K bytes)
 pkts bytes target     prot opt in     out     source
destination
 5779 4600K IMQ        all  --  *      *       0.0.0.0/0
0.0.0.0/0          IMQ: todev 0

# sh /root/show_tc.sh
############################################################################
########################
                                                        Qdisciplines
############################################################################
########################
qdisc htb 1: r2q 10 default 1 direct_packets_stat 0
 Sent 2185158 bytes 2835 pkts (dropped 1, overlimits 3168)


############################################################################
########################
                                                        Classes
############################################################################
########################
class htb 1:11 root prio 0 quantum 5120 rate 400Kbit ceil 400Kbit burst
2111b/8 mpu 0b cburst 2111b/8 mpu 0b level 0 buffer [000119fb] cbuffer
[000119fb]
 Sent 0 bytes 0 pkts (dropped 0, overlimits 0)
 lended: 0 borrowed: 0 giants: 0
 tokens: 72187 ctokens: 72187

class htb 1:1 root prio 0 quantum 200000 rate 800Mbit ceil 800Mbit burst
1050044b/8 mpu 0b cburst 1050044b/8 mpu 0b level 0 buffer [00004476] cbuffer
[00004476]
 Sent 40014 bytes 482 pkts (dropped 0, overlimits 0)
 rate 100bps 1pps
 lended: 482 borrowed: 0 giants: 0
 tokens: 17526 ctokens: 17526

class htb 1:10 root prio 0 quantum 5120 rate 400Kbit ceil 400Kbit burst
2111b/8 mpu 0b cburst 2111b/8 mpu 0b level 0 buffer [000119fb] cbuffer
[000119fb]
 Sent 2145144 bytes 2353 pkts (dropped 1, overlimits 0)
 lended: 2353 borrowed: 0 giants: 0
 tokens: 70548 ctokens: 70548

############################################################################
########################
                                                        Filters
############################################################################
########################
filter parent 1: protocol ip pref 1 u32
filter parent 1: protocol ip pref 1 u32 fh 800:[80000000]  ht divisor 1
filter parent 1: protocol ip pref 1 u32 fh 800::1[80000001]  order 1 key ht
800 bkt 0 flowid 1:10
  match c009cb46/ffffffff at 16
  match 00500000/ffff0000 at 20
filter parent 1: protocol ip pref 1 u32 fh 800::3[80000003]  order 3 key ht
800 bkt 0 flowid 1:10
  match c009cb46/ffffffff at 12
  match 00000050/0000ffff at 20


	This time Oops trace is different then previous. But similarity is that it
can be simulated by placing simply one entry into iptables i.e iptables -t
mangle -I PREROUTING -j IMQ and avoided by not having above entry.
	I know again filter 800::3 is not proper and it does not satisfy my
purpose. Insteed of specifying Public-IP, I made mistake of placing
client-ip and found some bug.

-- Sumit

[-- Attachment #2: 2.4bug.log --]
[-- Type: application/octet-stream, Size: 24597 bytes --]

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2002-07-29 14:39 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-07-29 14:39 [LARTC] RE: Oops with IMQ Ingress Sumit Pandya

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.