[Firewall] Bandwidth limitation for upload?

Roland Haeder r.haeder at gmx.de
Wed Mar 10 19:32:49 CET 2010


> Sure, removing t110 and t25 from SHAPER_BULKDATA_PORTS will give them the default queue with is a little higher priority.  SHAPER_STREAMINGMEDIA_PORTS is the highest priority, SHAPER_INTERACTIVE_PORTS is the next highest.
Thanks for the advice. I will try it out. :)

> You might try increasing UPLINK closer to your 64 limit.
Already done.

> PS: Arno recently included (1.9.2k-DEVEL) a traffic shaper update with two more queues and complete DSCP mapping, amount other things.
I think I better wait for a Debian package not to mix up thinks. :)

BTW: I have attached a logfile with tons of strange "scans" (which looks
like usual HTTP replies to me). I took some probes and found out that
these all probes matches to host names which YaCy has crawled.

So what could this mean? The connection was faster closed (by YaCy than
the package wants to reach the destination port? As I know, YaCy aborts
a transfer (right after the header lines analysis, as I recall) if the
downloaded document in question is larger than a specified size.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: port80.log
Type: text/x-log
Size: 147379 bytes
Desc: not available
URL: <http://rocky.eld.leidenuniv.nl/pipermail/firewall/attachments/20100310/37e3a4d2/attachment-0001.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
URL: <http://rocky.eld.leidenuniv.nl/pipermail/firewall/attachments/20100310/37e3a4d2/attachment-0001.pgp>

More information about the Firewall mailing list