In message , Richard Kettlewell
 writes
>That looks like a normal SSH disconnect[1]. There’s quite a few reasons
>the OpenSSH client might send that with the most obvious being rsync
>closing the pipe to the SSH client.
>
>There’s an apparent inconsistency here, assuming that these log traces
>reflect the same session:
>
>* The client reports that server has closed the TCP session when it
>  still had something to write.
>
>* The server thinks the client has sent it a disconnect in the SSH
>  session.
>
>The former could be faked by an intermediate router but I think you said
>there wasn’t one, and the latter is not practical to fake.
>

The LAN has a router (which also acts as the modem and handles local
DHCP etc), but physically, it is beyond the section of network that the
source and target are on.  Whether packets take the direct route or the
scenic route, I don't know.

>Are you familiar with strace? At this point that’s definitely the tool
>I’d reach for.
>
>  [1] https://tools.ietf.org/html/rfc4253#section-11.1
>

I've heard of it, but I haven't (yet) had a reason to use it.


Adrian
--
To Reply :
replace "bulleid" with "adrian" - all mail to bulleid is rejected
Sorry for the rigmarole, If I want spam, I'll go to the shops
Every time someone says "I don't believe in trolls", another one dies.

--- SoupGate-Win32 v1.05