[GLLUG] scp question

Stanley Mortel mortel at cyber-nos.com
Sat Jan 25 13:40:04 EST 2014


Thanks Karl and Marshal.  My version of ssh does not have the -3 option, 
so maybe I'll update it.  The reverse port forward idea is a slick idea.

Appreciate the suggestions.


Stan


On 01/25/2014 02:30 AM, Karl Schuttler wrote:
> Another avenue you could pursue would be to reverse ssh port forward 
> port 22 on wirelessserverIPaddress to a high port on your laptop (eg 
> 8888).
>
> Then you could log into wiredserverIPaddress over ssh and initiate the 
> scp, (scp -P 8888 localfile wirelesserverusername at laptopIPaddress:path)
>
> Less elegant but maybe easier?
>
>
> On Sat, Jan 25, 2014 at 1:52 AM, Marshal Newrock <marshal at zordio.com 
> <mailto:marshal at zordio.com>> wrote:
>
>     I found a useful article about this:
>
>     http://stackoverflow.com/questions/3407442/how-does-scp-traffic-flow-between-two-remote-hosts
>
>     The upshot is that unless the two remote hosts can see each other, you
>     can use the -3 option to force traffic through the local host.
>
>     Marshal
>
>
>     On Fri, 24 Jan 2014 23:56:08 -0500
>     Stanley Mortel <mortel at cyber-nos.com
>     <mailto:mortel at cyber-nos.com>> wrote:
>
>     > OK, so I'm trying to copy some files from a server on a 192.168.16.0
>     > network to another server on a 192.168.10.0 network.  My laptop has
>     > its wired port eth0 manually set at 192.168.16.2 and its
>     wireless set
>     > via DHCP to 192.168.10.100.  I thought the following would do what I
>     > want:
>     >
>     > scp user at wiredserverIPaddress:/path/files
>     > user at wirelessserverIPaddress:/path/
>     >
>     > I get the request for a password on the first server, then I get an
>     > error trying to connect to the second server via the wireless
>     > connection:
>     >
>     > ssh: connect to host <IP address> port 22: No route to host
>     > lost connection
>     >
>     > I can ping both servers, and ssh into both individually, but scp
>     > doesn't seem to be able to figure out that the destination server
>     > needs to go out the wireless port.
>     >
>     > Yes, I realize this is not a terribly efficient way to transfer
>     > files. That's OK.  I can just change IP addresses and do an scp
>     > direct from server1 to server2.  But..... it just seems like this
>     > should work, so I thought I'd try it.
>     >
>     > Any suggestions?
>     >
>     >
>     > Stan
>     > _______________________________________________
>     > linux-user mailing list
>     > linux-user at egr.msu.edu <mailto:linux-user at egr.msu.edu>
>     > http://mailman.egr.msu.edu/mailman/listinfo/linux-user
>
>
>     --
>     Marshal Newrock
>     Zordio, LLC - http://www.zordio.com
>
>     _______________________________________________
>     linux-user mailing list
>     linux-user at egr.msu.edu <mailto:linux-user at egr.msu.edu>
>     http://mailman.egr.msu.edu/mailman/listinfo/linux-user
>
>
>
>
> _______________________________________________
> linux-user mailing list
> linux-user at egr.msu.edu
> http://mailman.egr.msu.edu/mailman/listinfo/linux-user

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.egr.msu.edu/mailman/public/linux-user/attachments/20140125/72b2f0bc/attachment.html>


More information about the linux-user mailing list