From: Harri Haataja <harriha@mail.student.oulu.fi>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] netcat, the only stdin/stdout redirector to tcp/udp conns?
Date: Wed, 5 Apr 2006 01:45:33 +0300 [thread overview]
Message-ID: <20060404224533.GK17716@XTL.antioffline.net> (raw)
In-Reply-To: <4432C4EA.10204@gmail.com>
On Tue, Apr 04, 2006 at 09:11:38PM +0200, Lluís 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/
--
My kettle just sits there steaming, and won't tell me anything.
Much like my first wife.
-- Paul Tomblin
next prev parent reply other threads:[~2006-04-04 22:45 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-04 19:11 Lluís Batlle i Rossell
2006-04-04 19:34 ` "Nils O. Selåsdal"
2006-04-04 19:43 ` Paul Hebble
2006-04-04 20:36 ` Lluís Batlle i Rossell
2006-04-05 0:36 ` matt
2006-04-04 20:44 ` David Leimbach
2006-04-04 20:53 ` uriel
2006-04-04 21:20 ` Lluís Batlle i Rossell
2006-04-04 22:10 ` Bruce Ellis
2006-04-05 2:32 ` David Leimbach
2006-04-05 16:54 ` Aharon Robbins
2006-04-04 23:46 ` geoff
2006-04-05 1:05 ` Anthony Sorace
2006-04-05 2:21 ` Ronald G Minnich
2006-04-05 2:35 ` David Leimbach
2006-04-05 2:39 ` geoff
2006-04-05 2:45 ` David Leimbach
2006-04-05 2:50 ` geoff
2006-04-05 4:38 ` [9fans] netcat, Skip Tavakkolian
2006-04-05 4:41 ` geoff
2006-04-05 4:54 ` Skip Tavakkolian
2006-04-05 4:46 ` Bruce Ellis
2006-04-05 6:02 ` Adrian Tritschler
2006-04-05 15:50 ` Jack Johnson
2006-04-05 16:55 ` David Leimbach
2006-04-05 2:44 ` [9fans] netcat, the only stdin/stdout redirector to tcp/udp conns? Ronald G Minnich
2006-04-05 4:38 ` Bruce Ellis
2006-04-05 4:56 ` Skip Tavakkolian
2006-04-04 20:17 ` Russ Cox
2006-04-04 20:41 ` Lluís Batlle i Rossell
2006-04-04 22:45 ` Harri Haataja [this message]
2006-04-04 23:33 ` Taj Khattra
2006-04-05 10:34 ` Heiko Dudzus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060404224533.GK17716@XTL.antioffline.net \
--to=harriha@mail.student.oulu.fi \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).