On 2022-10-05, Courtney <taeki...@gmail.com> wrote:
> $ ssh -V
> OpenSSH_9.1, LibreSSL 3.6.0
>
> scp has been stalling on my system and hanging up my networking stack.

Do you know when it started?

What snapshot are/were you running?

It is always helpful to include dmesg when reporting a problem.


> I am probably doing this wrong, but I have been having to delete, down, up
> and sh /etc/netstart to recover networking, or doing a reboot.

That you are having to do this to recover suggests that the problem
is not with ssh itself.


> It seems to happen with larger files, whether I use the -O flag for 
> legacy or
> not. I have tried sending to:
>
> - FreeBSD 13.1 (8.8)
> - Rocky 8 (8.0)
> - Ubuntu 22.04 (8.9)
>
> I have not been doing an path expansion to the dest path. I tested from
> OpenSSH 9.1 -> 9.1, no problem.
>
> This is the output I get when running scp to a host with an older ssh 
> version:
>
> scp: debug3: SSH2_FXP_STATUS 0
> scp: debug3: In write loop, ack for 1346 32768 bytes at 43941888
> scp: debug3: Sent message SSH2_FXP_WRITE I:1411 O:46071808 S:32768
> scp: debug3: SSH2_FXP_STATUS 0
> scp: debug3: In write loop, ack for 1347 32768 bytes at 43974656
> scp: debug3: Sent message SSH2_FXP_WRITE I:1412 O:46104576 S:32768
> scp: debug3: SSH2_FXP_STATUS 0
> scp: debug3: In write loop, ack for 1348 32768 bytes at 44007424
> scp: debug3: Sent message SSH2_FXP_WRITE I:1413 O:46137344 S:32768
> scp: debug3: SSH2_FXP_STATUS 0
> scp: debug3: In write loop, ack for 1349 32768 bytes at 44040192
> scp: debug3: Sent message SSH2_FXP_WRITE I:1414 O:46170112 S:32768
> scp: debug3: SSH2_FXP_STATUS 0
> scp: debug3: In write loop, ack for 1350 32768 bytes at 44072960
> scp: debug3: Sent message SSH2_FXP_WRITE I:1415 O:46202880 S:32768
> scp: debug3: SSH2_FXP_STATUS 0
> scp: debug3: In write loop, ack for 1351 32768 bytes at 44105728
> debug2: channel 0: rcvd adjust 131072
>
>
> I just did a sysupgrade -s today before posting. As it stands, with 9.1 
> I can't
> scp to versions of ssh older than 9.1.
>
>


-- 
Please keep replies on the mailing list.

Reply via email to