>> # ttcp -s -t -b 1677721 -l 16384 backup.netbsd.org
>> ttcp-t: buflen=16384, nbuf=2048, align=16384/0, port=5001, sockbufsize=1677721

> 1677721 is 0x199999.  Did something go wrong with interpreting a
> decimal number as hex, or is that just a coincidence?

1677721 is 16777216 or 16777215, ie, 2^24 or 2^24-1, with the last
digit dropped.  Divide 0x1000000 or 0xffffff by 0xa and you get
0x199999 (with a remainder of 0x6 or 0x5).

Whether this is actually where it came from, of course, I cannot tell.
But I do note that it was provided on the ttcp command line and thus I
see no particular reason to think it's a magic boundary value.

/~\ The ASCII				der Mouse
\ / Ribbon Campaign
 X  Against HTML	       mouse@rodents.montreal.qc.ca
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B