Date: Thu, 24 Jul 2003 10:36:41 -0700 From: John-Mark Gurney <gurney_j@efn.org> To: Diomidis Spinellis <dds@aueb.gr> Cc: freebsd-hackers@freebsd.org Subject: Re: Network pipes Message-ID: <20030724173640.GA10708@funkthat.com> In-Reply-To: <3F1FBD35.82A3629E@aueb.gr> References: <3F1F96A5.A7D2D221@aueb.gr> <20030724021426.A28546@xorpc.icir.org> <3F1FBD35.82A3629E@aueb.gr>
next in thread | previous in thread | raw e-mail | index | archive | help
Diomidis Spinellis wrote this message on Thu, Jul 24, 2003 at 14:04 +0300:
> separate command "netpipe". Netpipe takes as arguments the originating
> host, the socket port, the command to execute, and its arguments.
> Netpipe opens the socket back to the originating host, redirects its I/O
> to the socket, and execs the specified command.
This breaks nat firewalls. It is very common occurance to only accept
incoming connections, and only on certain ports. This means any system
of firewill will probably be broken by this. :(
i.e. behind a nat to a public system, the return connection can't be
established. From any system to a nat redirected ssh server, the
incoming connection won't make it to the destination machine.
I think this should just be a utility like Luigi suggested. This will
help "solve" these problems.
--
John-Mark Gurney Voice: +1 415 225 5579
"All that I will do, has been done, All that I have, has not."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030724173640.GA10708>