From: James Linder <jam@ti...> - 2012-06-02 08:30:43
On 01/06/2012, at 9:41 PM, gumstix-users-request@... wrote:
> The GNU netcat utility which you can call with the command nc or
> netcat appears to be broken in client mode.
> It functions correctly in server mode on an overo COM with a IP
> address of 192.168.1.100 when started with this syntax:
> nc -l -p 1234
> Which sets up a server listening for connections on port 1234.
> On another overo COM, issuing
> nc 192.168.1.100 1234
> Should bring up a connection between the two overo COM modules, but
> the client nc command immediately returns to the command prompt.
> The busybox netcat utility does function as a client, but lacks some
> of the functionality that the GNU netcat utility should provide.
> The command I used to start the busybox netcat client is:
> busybox nc 192.168.1.100:1234
> It may be that this is a issue with the utility itself and not a build
> issue related to the particular hardware environment, but I thought I
> would post this here first to see if anyone had any suggestions or had
> run into this before.
This message is noise :-) but it confirms that I've had many issues using nc on linux using CentOS 5 and ubuntu 10.04
I can't recall details but I built nc twice, one as a server on CentOS and one as client on Ubuntu and particularly server would accept one connection then exit despite -l
If you get desperate mail me and I'll dig out old code to see what I did (1 year old)