On Dec 15, 2005, at 5:05 pm, Matthias Langer wrote:
Well, i use azureus - and of course i know that upload-speed can be limited - which is maybe in fact the best solution to my problem. ... for p2p apps - give them as much bandwidth they can reasonably get but don't let them slow down firefox, ssh etc. Because i want this setup just for my homenetwork, it would perfectly suffice if packages get their priorities by examining port-numbers. And because i want to at least partially understand what i'm doing i would prefer a simple and clean setup.
I haven't used it yet, but my understanding of traffic-shaping is that it's exactly what you want. I believe that other quality-of-service mechanisms may require applications to be QoS aware (setting a QoS bit in the packet header).
You're absolutely right in that reducing the bandwidth of the p2p app isn't the ideal way to achieve what you want - I find latency in browsing & surfing with BitTorrent consuming only 60% - 70% of my upload - it doesn't help that other peers are continually making requests of you. If you lower the bandwidth consumption in Azureous then you have to remember to up it again when you go to bed - traffic shaping WILL allow you to permanently maximise your p2p bandwidth, with the ROUTER reducing it only when your priority services send packets.
I know that in principle the neccessairy steps to do what i wannt can be found in the 'Packet Shaping HOWTO'. .... By the way, there are many different packet shedulers in the kernel - and the HOWTO only explains the HTP-scheduler. What about the other schedulers - can they be usefull for my purposes too - and if yes, how can they be configured and used ?
No idea. I hope you'll give us feedback when you've discovered more. Stroller. -- gentoo-user@gentoo.org mailing list
