Bandwidth limitation doesn't impact buffering directly .. it works by delaying the send of packet N+1 by the transfer time computed for packet N. It appears to us from a black box perspective that there is no provision for dropping packets when the queue length exceeds some length ... say 3 seconds worth.
One of these days I may get around to addressing those issues, but in the mean time, that is how it is. Dave Morris On Thu, 8 Nov 2007, Xiaochuan Shen wrote: > Hello group, > > > > I am just wondering if anyone got any idea how much buffer NistNet uses (or > in what way it determines how much buffer should be used) when bandwidth > limitation is applied. > > > > > > This is what I implemented: > > > > > > server ----------------(100mb link) ---------------- NistNet box > ------------------(100mb link) --------------------- Client > > > > > > I am transferring bulk TCP traffic from server to client (a huge file using > FTP transfer). > > > > If I apply: > > Cnistnet server client -bandwidth 187500 > > > > Then I observed the "queue length" is around 50 packets. > > > > If all of these packets are full packet of size 1500Byte, a queue length of > 50 packets will introduce 50 * 1500 / 187500 = 400 milli-seconds delay in my > configuration. Is this value realistic in a real network? If not, why > nistnet use such a length of buffer? > > I can understand nistnet has to buffer a number of packets before it can > process the coming traffic but is this queue length configurable in nistnet? > > > > Thanks for anyone looking and answering! > > > > Regards, > > Xiaochuan > > _______________________________________________ nistnet mailing list nistnet@antd.nist.gov http://www-x.antd.nist.gov/mailman/listinfo/nistnet
