> Will your script help the performance on heavily loaded external links? > Your script constructs a queue for the internal interface, which > prioritizes traffic for that interface, but I have an easily saturated > dial-up connection, and my problems are (I suspect) with the very large > queues that build up at my upstream provider. I don't see how your > script will help me with this problem, though it is likely the problem > is with my understanding, rather than with your script!
Bandwidth filtering *anywhere* in the end-to-end chain can help control traffic levels, leaving room for other (presumably higher priority) packets, provided the traffic you're trying to limit is TCP based, and both ends of the TCP connection "play by the rules". Why? Perhaps a bit of a digression, but: TCP is a connection based protocol, and includes mechanisims that allow each end of a connection to acknowledge reciept of a packet, and/or request duplicates of a packet. If you start dropping packets anywhere in a TCP link, the sending and recieving end will notice the missing packets, causing the sender to "back-off", and start pushing data out at a slower rate. There are, of course, many low-level networking parameters that control this behavior, which can be tweaked if you really understand what you're doing (if you don't, fiddling with these controlls is amost guaranteed to provide less performance than the defaults). So...if you're background traffic consists mainly of long-term (ie long enough for rate adaptation to occur) or slow-start TCP connections, you *CAN* successfully limit their bandwidth anywhere in the end-to-end network chain. Charles Steinkuehler http://lrp.steinkuehler.net http://c0wz.steinkuehler.net (lrp.c0wz.com mirror) _______________________________________________ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
