This bug is wierd. I have a file which SSH will not
transmit from QNX. It can’t be copied with SFTP, and
it can’t be added with CVS. It’s only 2262 bytes.
You can get it here:
ftp://ftp.animats.com/pub/mlock2a.txt
Please try moving this file around with SFTP from
a QNX machine to various hosts. SFTP just stalls
when sending it from QNX 6.2.1 NC to a Red Hat Linux
machine. But I can send the same file from Windows
2000 to the same Red Hat Linux machine without
problems.
Other files work just fine. It’s the specific
text of this file that won’t work.
This is causing our CVS operations to stall, holding
up the movement of a large project to QNX.
OpenSSH: 3.5p1
John Nagle
Animats
It turns out that this is an IP fragmentation/MTU problem.
Some router between my home machine and my office machine
is mishandling fragmentation. I’ve set my local MTU to
1492 as a workaround. Thanks.
John Nagle
John Nagle wrote:
This bug is wierd. I have a file which SSH will not
transmit from QNX. It can’t be copied with SFTP, and
it can’t be added with CVS. It’s only 2262 bytes.
You can get it here:
ftp://ftp.animats.com/pub/mlock2a.txt
Please try moving this file around with SFTP from
a QNX machine to various hosts. SFTP just stalls
when sending it from QNX 6.2.1 NC to a Red Hat Linux
machine. But I can send the same file from Windows
2000 to the same Red Hat Linux machine without
problems.
Other files work just fine. It’s the specific
text of this file that won’t work.
This is causing our CVS operations to stall, holding
up the movement of a large project to QNX.
OpenSSH: 3.5p1
John Nagle
Animats
John Nagle <nagle@downside.com> wrote:
It turns out that this is an IP fragmentation/MTU problem.
Some router between my home machine and my office machine
is mishandling fragmentation. I’ve set my local MTU to
1492 as a workaround. Thanks.
You might also want to get the latest openssh package. It will
show up on QNX Online soon, but for now you can access it from
http://qnx.wox.org/packages/6.2/. I fixed a really nasty stall
bug that was causing scp/sftp to hang-up for most people.
chris
–
Chris McKillop <cdm@qnx.com> “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/
OK, thanks.
We’ve been climbing the walls getting CVS to work with
QNX clients, a Linux server, three intermediate low-end
routers, SSH, and a novice syadmin, but I think it’s
working now. Took two weeks we didn’t have, though.
CVS over SSH loses too many error messages.
Network errors result in meaningless messages like
“line too long”. Bad design.
John Nagle
Chris McKillop wrote:
John Nagle <> nagle@downside.com> > wrote:
It turns out that this is an IP fragmentation/MTU problem.
Some router between my home machine and my office machine
is mishandling fragmentation. I’ve set my local MTU to
1492 as a workaround. Thanks.
You might also want to get the latest openssh package. It will
show up on QNX Online soon, but for now you can access it from
http://qnx.wox.org/packages/6.2/> . I fixed a really nasty stall
bug that was causing scp/sftp to hang-up for most people.
chris