[EMAIL PROTECTED] wrote: > What sort of capabilities are you looking for in shaping packets? > > - introducing random packet loss? > - introducing fixed/random delays? > - imposing queue restrictions (n slots, n kB, n MB) > - imposing a bandwidth limit (n kb/s, n Mb/s) > - changing the TCP MSS (can only be changed when the connection *starts) > - changing the TCP window size > - others? > > Darren >
Obviously, you can impose bandwidth limits, queue restrictions (I'm a little fuzzy on this one but it appears to be like netfilter in Linux) and drop packets currently if at a broad level. What I'd really like is to be able to change all the above (except packet loss or fixed/random delays ... that's easy enough to just do in server code) on a per connection basis. Having a way to granularly set a bandwidth limit for a specific connection would be very useful as a wrapper to changes in the TCP window size and MSS. As I understand the way that limits are imposed in Crossbow, on a per interface/port basis, it's implemented using squeues and ends up introducing packet loss and queue restrictions instead of the smoother options that you can use with TCP header manipulation. (Someone please correct me if I'm lacking some understanding on how this happens under the hood.) About the MSS, albeit my TCP is a little fuzzy, but would it be possible to do a connection reestablishment to get the MSS changed? _______________________________________________ networking-discuss mailing list [email protected]
