From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Wed, 5 Apr 2006 01:45:33 +0300 From: Harri Haataja Subject: Re: [9fans] netcat, the only stdin/stdout redirector to tcp/udp conns? In-reply-to: <4432C4EA.10204@gmail.com> To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> Message-id: <20060404224533.GK17716@XTL.antioffline.net> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-disposition: inline References: <4432C4EA.10204@gmail.com> User-Agent: Mutt/1.5.11+cvs20060126 Content-Transfer-Encoding: quoted-printable Topicbox-Message-UUID: 2eafa322-ead1-11e9-9d60-3106f5b1d025 On Tue, Apr 04, 2006 at 09:11:38PM +0200, Llu=EDs Batlle i Rossell wrote: > I hope this will not be any flame... but I hardly can believe that in > a normal linux/bsd distribution there isn't any tool for redirecting > stdin/stdout to a (new) tcp/udp connection. I think that > file-descriptor-fans will know something like that... Not sure if it's any different than netcat for you, but there's socat. Description: multipurpose relay for bidirectional data transfer Socat (for SOcket CAT) establishes two bidirectional byte streams and transfers data between them. Data channels may be files, pipes, devices (terminal or modem, etc.), or sockets (Unix, IPv4, IPv6, raw, UDP, TCP, SSL). It provides forking, logging and tracing, different modes for interprocess communication and many more options. . It can be used, for example, as a TCP relay (one-shot or daemon), as an external socksifier, as a shell interface to Unix sockets, as an IPv6 relay, as a netcat and rinetd replacement, to redirect TCP-oriented programs to a serial line, or to establish a relatively secure environment (su and chroot) for running client or server shell scripts inside network connections. Upstream would appear to be http://www.dest-unreach.org/socat/ --=20 My kettle just sits there steaming, and won't tell me anything. Much like my first wife. -- Paul Tomblin