It was reported on VMware not VirtualBox but perhaps the NATs are similarly
broken - it might be worth trying to revert the change from old style QoS
to diffserv by setting "IPQoS lowdelay throughput".
--
Sent from a phone, apologies for poor formatting.
On 15 November 2019 14:29:39 Steve McAfee <smcafee.social@xxxxxxxxx> wrote:
Thanks everyone for the feedback on the OpenSSH hang. I'm going to ask the
customer to review mtu in their configuration first to see if they can find
a problem. Also, if their host OS is windows there are some things
suggested to check, but I don't think it is windows. If it ever happens
again I'll try to investigate more as suggested by Darren before we
interrupt it.
steve
On Sun, Nov 10, 2019 at 5:29 AM Philipp Marek <philipp@xxxxxxxxxxxxx> wrote:
ISTR that I've read about some bugs with packet traversal through VM NAT
setups.
It was something about the RST packet triggering NAT destruction but not
being relayed further all the time (some race condition?!), that sounds
as if it fit the bill here.
https://forums.virtualbox.org/viewtopic.php?f=1&t=20579 comes close but
is a bit old...
You could try to use the TCP keepalive settings in SSH, and/or to reduce
the MTU size (as mentioned in another mail here already).
Else a few more setup details might help...
_______________________________________________
openssh-unix-dev mailing list
openssh-unix-dev@xxxxxxxxxxx
https://lists.mindrot.org/mailman/listinfo/openssh-unix-dev
_______________________________________________
openssh-unix-dev mailing list
openssh-unix-dev@xxxxxxxxxxx
https://lists.mindrot.org/mailman/listinfo/openssh-unix-dev
