On 13/06/2020 18:09, Richard Kettlewell wrote:
> The silence from this point is hard to explain. In the absence of an
> acknowledgement from .118, .18 should be retransmitting, and when it
> gives up (as the RST below suggests it has) that should provoke some
> kind traffic. And it’s certainly surprising not to see the final RST
> shown below.
>
> My current guess is that something has gone wrong in .18’s kernel
> network stack, possibly related to the the packet size. Since I’m not up
> for debugging the Linux IP stack, the only way I have to test this
> theory would be to upgrade .18 to buster and see if gets better
> (essentially: if there’s a bug that was fixed between the stretch and
> buster kernels). I appreciate that this is “perturb the problem and see
> if it goes away” but I don’t have a better suggestion at this point.

I think its hardware.

Because we are all software people doesn't mean it *is* software...

--
If I had all the money I've spent on drink...
..I'd spend it on drink.

Sir Henry (at Rawlinson's End)

--- SoupGate-Win32 v1.05