Have a look at ticket 0005095 isn't this the same underlying issue (but on the opposite direction) ?

I have tried the solution of ticket 0005095 :

1. add OPQoS=throughput to /etc/ssh/ssh_config
2. restart sshd: service ssh stop -> service ssh start
   but it's still not work

In your case, you might want to use it in /etc/ssh/sshd_config since you are connecting to the server. But maybe it's needed on both sides. It probably depends on what version of the SSH client you are using to connect to the kali machine.

I use PuTTY 0.70 to connect my kali machine, default setting I think

A few things to hopefully help this move along:

I have tried to reproduce this on the same VM as 0005095 - Windows 10 host with VMWare Workstation 15.0.2 build-10952284, running Kali 2018.4 with recent updates (up to date as of today, note that this means I'm running OpenSSH 7.9p1). I was NOT able to reproduce the problem with either Putty 0.70 or with OpenSSH for Windows 7.6p1 (understandably, since 7.6 would predate the issue, but that's what Windows currently ships with).

I then attempted to force my OpenSSH client to use -o IPQoS=AF21 and -o IPQoS=CS1. I was once again NOT able to reproduce the problem, connecting successfully in each instance.

I then tried downloading the latest test release of OpenSSH for Windows (7.7.2.0p1-Beta) - no change.

Finally, I spun up a completely fresh Kali 2018.4 VM with no updates. Once again, both my Windows clients were able to successfully ssh into the VM, even when forced to use the "bad" IPQoS settings.

Connections between the two VMs also work regardless of IPQoS settings, but that's somewhat understandable since it would all stay inside vmnat virtualisation in that scenario.

I suspect we'll need to find out more about the client that's causing the problem before we can reproduce it - I have a hunch it might be the client that's triggering the bug, and not the sshd in Kali. Some questions to perhaps get us started, @roger6:
-What operating system are you using?
-Is the client a virtual machine? If so, what virtualisation software are you using for it?
-What's the exact version of VMWare you're using for the server?
-Try using OpenSSH on the client side, with IPQoS=throuput set (either in /etc/ssh/ssh_config or by adding the -o IPQoS=throughput flag at run time). Does the problem persist?

Indeed, reading through your sshd log, it would appear that it's the client that broke the connection:

Read error from remote host 1.1.1.1 port 8888: Connection reset by peer

Hi,

as SexWarrior mentioned, I should post the associated scenario here:

-What operating system are you using?
Windows 7x64, with patched fully

-Is the client a virtual machine? If so, what virtualisation software are you using for it?
Client is real machine.

-What's the exact version of VMWare you're using for the server?
VMWare version is 14.0.0.build-666.1328

-Try using OpenSSH on the client side, with IPQoS=throuput set (either in /etc/ssh/ssh_config or by adding the -o IPQoS=throughput flag at run time). Does the problem persist?
I tried to do these steps to fix issue:

1. add IPQoS=throughput to /etc/ssh/ssh_config
2. restart sshd: service ssh stop -> service ssh start

But it still doesn't work fine, then I tried to change the way:

1. run sshd by command line:
   /usr/sbin/sshd -d -D -o IPQoS=throughput

It worked now, magic!

It perhaps mean current sshd don't reference the setting of /etc/ssh/ssh_config
Is it issue? How can I fix it if it's issue?

As @rhertzog mentioned, you need to be looking at /etc/ssh/sshd_config and not /etc/ssh/ssh_config.

ssh_config is the client configuration, and sshd_config is for the server, broadly speaking.

Yes you both are right, I change wrong file, it should be /etc/ssh/sshd_config
Now all works fine now, I'm apologized and many thanks to you both :)

Due to the age of the OS (Kali Moto [v1], Kali Safi [v2], Kali Rolling <= 2018.4), these legacy versions are no longer supported.
We will be closing this ticket due to inactivity.

Please could you see if you are able to replicate this issue with the latest version of Kali Linux - https://www.kali.org/downloads/)?

If you are still facing the same problem, feel free to re-open the ticket. If you choose to do this, could you provide more information to the issue you are facing, and also give information about your setup?
For more information, please read: https://kali.training/topic/filing-a-good-bug-report/