On Sun, 2 Jul 2006, Stefan Bethke wrote:
Essentially, dummynet delays processing of that "two" line just long enough
to break the code's assumption that TCP over the loopback interface is
instantaneous. If my fading memory of TCP/IP Illustrated Vol 2 serves me
right, that was actually the case
Am 28.06.2006 um 00:13 schrieb Mikhail Teterin:
fconfigure $sock -blocking 0
lappend result c:[gets $sock]
was always returning empty string, instead of the string "two",
that was
written into the socket and flushed.
Is the test wrong, and such result is possible, or is dummynet
t
After I added the following rules to my ipfw configuration:
ipfw pipe 1 config bw 20Mbit/s
ipfw add 200 pipe 1 tcp from any to any
The following test from Tcl's regression-test suite started to fail:
set s [socket -server accept 0]
set sock ""
set s2 [socket 1
