Re: How to restrict torrent download ?
|[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]|
On Fri, 2012-02-17 at 14:31 -0600, Lloyd Standish wrote: > On Fri, 17 Feb 2012 12:20:16 -0600, Andrew Beverley <andy@xxxxxxxxxxx> wrote: > > > 2. Doing the prioritisation elsewhere to the rate limiting. This doesn't > > work, as you can only prioritise when you have too much traffic, > > otherwise all the packets just pass straight through. > I may be wrong, but I thing prioritization at the load-balancing router > will work, even though there is rate-limiting at the users' radios. [...] > So the central router establishes lots of simultaneous connections > balanced over its 5 uplinks. Each uplink is only 600 kbit, limited to > maximum 500 kbit by an HTB qdisc on each uplink, to avoid queuing at > the ISP. Even though each individual user is rate-limited, the > combined egress traffic can easily exceed the uplink bandwidth, and > would start getting queued in the central router. Yes, that will work, because you've got a queue at the user's radio and in the main router. My point was that prioritisation will only work if you're also doing some sort of shaping/policing. > As far as bittorrent download goes, I understand that bittorent will > not allow a user to download (much) more than he or she uploads. That's not something I've seen, but my use of bittorrents is pretty minimal so I wouldn't like to say for certain. > In fact I am using only a policing qdisc on ingress. > Does this plan > sound reasonable to you, or am I overlooking or misunderstanding > something? Sounds reasonable, yes. Personally I've always done both egress and ingress (as egress on the LAN), but that's not based on any experience that only doing egress does not work. Andy -- To unsubscribe from this list: send the line "unsubscribe netfilter" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html