Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: dpreed@reed.com
To: "Dane Medic" <dm70dm@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Torrents are too fast
Date: Mon, 3 Nov 2014 08:33:37 -0500 (EST)	[thread overview]
Message-ID: <1415021617.1354967@apps.rackspace.com> (raw)
In-Reply-To: <CABsdH_HKRvXeHzPtOfGqQqRcBnSz7emU7WUNukoKZ=65ndWSuw@mail.gmail.com>

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


In other words, rather than share the capacity of the link "fairly" among flows (as TCP would if you eliminated excess buffer-bloat), you want to impose control on an endpoint from the middle?
 
This seems counterproductive... what happens when the IP address changes, new services arise, and more ports are involved?
 
TCP and other protocols generally are responsive when packets are dropped at a congested point, and they generally end up sharing the available capacity relatively fairly.  If you want even more fairness, use fq_codel. It should do pretty much what you want without even having to identify the source addresses.


On Monday, November 3, 2014 2:53am, "Dane Medic" <dm70dm@gmail.com> said:





Hi,

what lines do I have to add to simple.qos script on cerowrt to slow down bulk traffic from a specific IP address (172.30.42.6) and from a specific port (18224)?


Thank you guys

[-- Attachment #2: Type: text/html, Size: 1728 bytes --]

  reply	other threads:[~2014-11-03 13:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-03  7:53 Dane Medic
2014-11-03 13:33 ` dpreed [this message]
2014-11-20 14:13 Dane Medic
2014-11-20 14:40 ` Dave Taht
2014-11-20 16:25   ` Dane Medic
2014-11-21 11:51     ` Sebastian Moeller
2014-11-21 12:04       ` Dane Medic
2014-11-21 12:17         ` Sebastian Moeller
2014-11-21 11:16 ` Sebastian Moeller
2014-11-21 11:51   ` Dane Medic
2014-11-21 12:14     ` Sebastian Moeller

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

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to=1415021617.1354967@apps.rackspace.com \
    --to=dpreed@reed.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dm70dm@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox