Your message dated Mon, 28 Feb 2011 23:36:31 -0800
with message-id <[email protected]>
and subject line RE: wondershaper: Does not work correctly with intesive uploads
has caused the Debian Bug report #264133,
regarding wondershaper: Does not work correctly with intesive uploads
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
264133: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=264133
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: wondershaper
Version: 1.1a-4
Severity: important
I have a 256Kbps/128Kbps ADSL line with an effective bandwidth of
225Kbps/115Kbps. My web server has a WebDAV folder and I use it to
update the website.
At this moment I'm uploading photos so my upload link is really busy but
there is not difference with wondershaper, I get the same ping with it or
without it.
I'm executing it this way:
wondershaper eth0 225 115
My eth0 is the network card connected to the ADSL router and my private
network is connected to the eth1 card.
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.7-1-686
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (ignored: LC_ALL set to
es_ES.UTF-8)
Versions of packages wondershaper depends on:
ii iproute 20010824-13.1 Professional tools to control the
-- no debconf information
--- End Message ---
--- Begin Message ---
I think the results the submitter of #264133 got with various tests is
pretty standard, DSL lines lines never do what is advertised AND in order
for OQS to work properly it has to be set below the max the line is capable
of in order to force the bottleneck to be the QOS. wondershaper certainly
helped the situation, but there's only so much it can overcome.
I'm closing this bug.
--
Matt Taggart
[email protected]
--- End Message ---
