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
Yann:
Sorry for the delay.. I would have responded quicker
but we have company for this long weekend in the US :-D
This is definetly a pilot error on my part.. but I can't
figure out how... it appears (in the patch) that all the
files are there...
But.. I am wondering..
in your source
netinet
On Sun, 02 Jul 2006, at 07:37, Randall Stewart wrote:
> Yann:
>
> Sorry for the delay.. I would have responded quicker
> but we have company for this long weekend in the US :-D
no problem really
> This is definetly a pilot error on my part..
ok never mind: it was a pilot error on my sid
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
Hello,
here is a reply from one of the XORP developers, Pavlin Radoslavov. What is
your
opinion to this problem ?
Thanks,
Bohus
- Forwarded message from Pavlin Radoslavov <[EMAIL PROTECTED]> -
> To: [EMAIL PROTECTED]
> cc: Pavlin Radoslavov <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
> Sub
Hi,
Well, I'm quite new to the *nix/BSD arena, and have
been giving it a try lately for a server I'm
attempting to host for a University project; so far
I've been impressed. I'm trying to setup/install the
drivers for a PCI wireless card, but am having little
success. The manufacturer of the ca
