Re: Compression with ssh tunneling
- From: Ben Harris <bjharris@xxxxxxxxxxxxxxxxxxxxxx>
- Date: 10 May 2007 16:17:34 +0100 (BST)
In article <464251a1@xxxxxxxxxxxx>,
David Gempton <davidg@ttc4it_dot_co_dot_nz> wrote:
Here was the test:
# ssh -L222:localhost:22 root@server
# scp -P222 root@localhost:/tmp/file1 .
Then I repoeated the test with compression on the tunnel...
# ssh -C -L222:localhost:22 root@server
# scp -P222 root@localhost:/tmp/file1 .
And the speeds were about the same.
If I put the compression on the scp command instead of the tunnel there
was a major speed increase.
Is this likely to be because the binary network traffic generated by scp
is not very compressable or is it that compression on tunnels does not
work ??
The former, effectively. The network traffic generated by scp is an SSH
session, which is encrypted. Encryption produces what looks like random
data to anyone without the key, and so applying compression to encrypted
data is useless.
--
Ben Harris
.
- Follow-Ups:
- Re: Compression with ssh tunneling
- From: David Gempton
- Re: Compression with ssh tunneling
- References:
- Compression with ssh tunneling
- From: David Gempton
- Compression with ssh tunneling
- Prev by Date: Read from remote host web01.sti.local: Connection reset by peer
- Next by Date: Re: Compression with ssh tunneling
- Previous by thread: Re: Compression with ssh tunneling
- Next by thread: Re: Compression with ssh tunneling
- Index(es):
Relevant Pages
|
|
