ssh None cipher
allanjude at freebsd.org
Sat Oct 18 19:32:02 UTC 2014
On 2014-10-18 13:21, Freddie Cash wrote:
> On Oct 18, 2014 3:54 AM, "Mark Martinec" <Mark.Martinec+freebsd at ijs.si>
>> If the purpose of having a none cipher is to have a fast
>> file transfer, then one should be using sysutils/bbcp
>> for that purposes. Uses ssd for authentication, and
>> opens unencrypted channel(s) for the actual data transfer.
>> It's also very fast, can use multiple TCP streams.
> That's an interesting alternative to rsync, scp, and ftp, but doesn't help
> with zfs send/recv which is where the none cipher really shines.
> Without the none cipher, SSH becomes the bottleneck limiting transfers to
> around 400 Mbps on a gigabit LAN. With the none cipher, the network becomes
> the bottleneck limiting transfers to around 920 Mbps on the same gigabit
> This is between two 8-core AMD Opteron 6200 systems using igb(4) NICs.
> freebsd-current at freebsd.org mailing list
> To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"
Actually, looking into it, the bbcp command can support a pipe at each
end instead of files, so you can actually do a zfs send | zfs receive
via bbcp, and use multiple concurrent connections, to get around TCP
window stuff when going transatlantic
I am going to be trying it out shortly.
Note: the other big improvement in newer ssh is the HPN stuff, that is
switched on since 9.2 I think.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 834 bytes
Desc: OpenPGP digital signature
More information about the freebsd-current