From mint-bounce@lists.fishpool.fi Wed Jun 29 20:42:47 2005 X-Original-To: fnaumann@mail.boerde.de Delivered-To: fnaumann@mail.boerde.de Subject: Re: [MiNT] ssh or telnet with zmodem From: Evan Langlois To: mint@fishpool.com Cc: hyc@highlandsun.com, "Szymanski, Frank-Peter (DMT)" In-Reply-To: <42B936BD.7090002@highlandsun.com> References: <66DC18A8418BEC40A860F6DE165FE29F03B1704C@EATPEX01.dmt.de> <42B936BD.7090002@highlandsun.com> Content-Type: text/plain Date: Wed, 29 Jun 2005 13:40:57 -0500 Message-Id: <1120070460.7070.52.camel@taro.coolrunningconcepts.com> Mime-Version: 1.0 X-Mailer: Evolution 2.2.1.1 Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - esc14.midphase.com X-AntiAbuse: Original Domain - fishpool.com X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - CoolRunningConcepts.com X-Source: X-Source-Args: X-Source-Dir: X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-To: mint-bounce@lists.fishpool.fi X-original-sender: Evan@CoolRunningConcepts.com Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: X-Virus-Scanned: by amavisd-new at relay.boerde.de X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on relay.boerde.de X-Spam-Status: No, hits=-1.2 tagged_above=-50.5 required=7.0 tests=AWL, BAYES_01 X-Spam-Level: On Wed, 2005-06-22 at 03:00 -0700, Howard Chu wrote: > Szymanski, Frank-Peter (DMT) wrote: > > Hello, > > > > is there any ssh or telnet with integrated zmodem available for mint? Not integrated, but both telnet and ssh will allow you to run external programs connected to the current terminal. I haven't done this in awhile, but I have used the capability to zmodem over tcp/ip. Its probably been 2 years though. > Why would you use zmodem over ssh when you could just use scp? A ---> B ---> C A = myhost.mydomain.com B = yourhost.yourdomain.com C = 192.168.10.10 Assume you want to reach host C. You are computer A. You can not reach host C because it is on a private network (assume there is no port forwarding from B to C, or NAT of any kind). You can only reach host B. You could scp from C back to A if C can reach the internet, but host C is a private NFS or MySQL server that is only for internal use, so no NAT or port forward or anything allows C to talk to anything but the internal network. bash@A> ssh B bash@B> ssh C bash@C> sz myfile.tar.gz escape from your terminal and use 'rz'