Disabling the Nagle algorithm (i.e., enabling TCP_NODELAY) or typing a lot of garbage just to fill the buffer with enough data can help, also.
And IIRC, netcat has a UDP mode as well. I see no reason for this to happen, but is there any chance it's using UDP by default, and you're only redirecting TCP? Good luck! -- "The user-friendly computer is a red herring. The user-friendliness of a book just makes it easier to turn pages. There's nothing user-friendly about learning to read." -Alan Kay On 11/21/05, John R. Hogerhuis <[EMAIL PROTECTED]> wrote: > On Sun, 2005-11-20 at 22:45 +0000, Richard Neill wrote: > > This connection is accepted (Netcat doesn't say connection refused), > > but then no data is ever transferred. [8<] > Without more data, I'd vote for (a). It sounds like netcat is behaving > normally to me. Since you are typing this at the prompt, netcat is > dutifully waiting for you to type something to send over the link. > > Perhaps if you type something on the client side and hit <ENTER>? Then > see if it shows up on the server side. > > If you don't get any output on the server side, a network sniffer > (tcpdump) on both sides of the connection should be illuminating. > _______________________________________________ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
