On Thu, 17 Jan 2008 20:18:18 +0100
comfooc <comfooc%gmail.com@localhost> wrote:
> On Jan 17, 2008 7:42 PM, Steven M. Bellovin <smb%cs.columbia.edu@localhost>
> wrote:
> > But both machines are on the same LAN? I asked because there are
> > some things that can be done on fast, long-distance connections
> > that don't matter too much on a LAN, especially if you're not
> > running at gigE speeds.
>
> They are in the same LAN, two meters of wire afar
>
> >comfooc <comfooc%gmail.com@localhost> wrote:
> > > It is possible that NetBSD ssh client demanded different (more
> > > bandwidth or CPU consuming) cipher from server?
> > >
> > Yes, that's very possible; it's why I asked. Run 'ssh -v' to see
> > what ciphers are being negotiated, I believe.
>
> I've checked and Linux, OpenBSD, NetBSD are negotiating the same
> cipher AES128
Hmm... Try installing bench/ttcp; that will let you test the network
piece independent of the crypto. After that, perhaps run
openssl speed
to see if the crypto performance is seriously mismatched.
After that, I'm out of ideas.
--Steve Bellovin, http://www.cs.columbia.edu/~smb