All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jason A. Pattie" <pattieja@pcxperience.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Wonder Shaper problem?
Date: Wed, 02 Jan 2002 16:20:03 +0000	[thread overview]
Message-ID: <marc-lartc-100998859627061@msgid-missing> (raw)

I think I have an issue with the Wonder Shaper script.  I setup my 
firewall to use the Wonder Shaper script with HTB (instead of CBQ).  My 
firewall has Squid running in transparent proxy mode, but I setup my 
browser to point to port 3128 (default Squid port).  I ran a ping 
session to www.yahoo.com and did an SSH at the same time that I 
downloaded the Linux kernel (~20MB).  It appears that most (if not all) 
of the traffic is being placed into the high priority class (queue? 
don't really know the difference yet) 10:.  Isn't it supposed to go to 
20: if it's not SSH or ICMP or ACK packets?  Here are the ping times 
from Yahoo! while doing the kernel download:

sh-2.05# ping www.yahoo.com
PING www.yahoo.akadns.net (64.58.76.227): 56 data bytes
64 bytes from 64.58.76.227: icmp_seq=0 ttl$1 time\x1959.8 ms
64 bytes from 64.58.76.227: icmp_seq=1 ttl$1 time\x1993.4 ms
64 bytes from 64.58.76.227: icmp_seq=2 ttl$1 time 18.8 ms
64 bytes from 64.58.76.227: icmp_seq=3 ttl$1 time\x1872.8 ms
64 bytes from 64.58.76.227: icmp_seq=4 ttl$1 time\x1895.7 ms
64 bytes from 64.58.76.227: icmp_seq=5 ttl$1 time 03.9 ms
64 bytes from 64.58.76.227: icmp_seq=6 ttl$1 time 26.3 ms
64 bytes from 64.58.76.227: icmp_seq=7 ttl$1 time 49.0 ms
64 bytes from 64.58.76.227: icmp_seq=8 ttl$1 time 75.7 ms
 
--- www.yahoo.akadns.net ping statistics ---
11 packets transmitted, 9 packets received, 18% packet loss
round-trip min/avg/max = 1872.8/1988.3/2075.7 ms

As you can see, they are very high, on the order of 2 seconds!!!??

When I stopped the kernel download, the ping results dropped to:

sh-2.05# ping www.yahoo.com
PING www.yahoo.akadns.net (64.58.76.176): 56 data bytes
64 bytes from 64.58.76.176: icmp_seq=0 ttl$1 time\x178.1 ms
64 bytes from 64.58.76.176: icmp_seq=1 ttl$1 time\x179.1 ms
64 bytes from 64.58.76.176: icmp_seq=2 ttl$1 time\x179.1 ms
64 bytes from 64.58.76.176: icmp_seq=3 ttl$1 time\x179.3 ms
64 bytes from 64.58.76.176: icmp_seq=4 ttl$1 time\x179.6 ms
64 bytes from 64.58.76.176: icmp_seq=5 ttl$1 time\x179.2 ms
 
--- www.yahoo.akadns.net ping statistics ---
6 packets transmitted, 6 packets received, 0% packet loss
round-trip min/avg/max = 178.1/179.0/179.6 ms

Here is the output of 'tc -s qdisc list':

sh-2.05# tc -s qdisc list
qdisc ingress ffff: dev eth0
 Sent 0 bytes 0 pkts (dropped 0, overlimits 0)
 
 qdisc sfq 20: dev eth0 quantum 1514b perturb 10sec
 Sent 44775 bytes 401 pkts (dropped 0, overlimits 0)
 
 qdisc sfq 10: dev eth0 quantum 1514b perturb 10sec
 Sent 166751 bytes 2494 pkts (dropped 0, overlimits 0)
 
 qdisc htb 1: dev eth0 r2q 10 default 20 dcache 0
 deq_util 1/1000000 deq_rate 0 trials_per_deq 0
 dcache_hits 0 direct_packets 0
 Sent 211526 bytes 2895 pkts (dropped 0, overlimits 0)

During the download and the ping, the SSH session is extremely sluggish. 
 But once both are stopped, the SSH session is very usable.

I'm using the 2.4.16 kernel patched with the HTB patch.

-- 
Jason A. Pattie
pattieja@pcxperience.com



_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/

             reply	other threads:[~2002-01-02 16:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-02 16:20 Jason A. Pattie [this message]
2002-01-02 17:09 ` [LARTC] Wonder Shaper problem? bert hubert
2002-01-02 17:44 ` Jason A. Pattie
2002-01-02 18:04 ` Jason A. Pattie
2002-01-02 19:22 ` Michael T. Babcock
2002-01-02 20:39 ` Jason A. Pattie
2002-01-03 16:25 ` Jason A. Pattie
2002-01-03 16:59 ` Dhaval Patel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-lartc-100998859627061@msgid-missing \
    --to=pattieja@pcxperience.com \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.