kaplan2539

@vjek @BCVerdouw I thought my comment to issue 155 might be interesting for you: https://github.com/billziss-gh/sshfs-win/issues/155#issuecomment-777466963

Wow, thanks for the *fast* reply! We are seeing the same symptoms as described in https://github.com/dorssel/usbipd-win/issues/300 The connection is closed on the Linux (WSL2) client side. Collecting logs and captures...

The exact cause of the drops is unknown. We have quite complex setup with some device constantly streaming real-time measurement data via an FTDI usb-serial interface. When reading it out...

Actually I found some old logs (still usbip v2.1 / Linux 5.4): [log-usbipd.txt](https://github.com/dorssel/usbipd-win/files/8870638/log-usbipd.txt) [log.txt](https://github.com/dorssel/usbipd-win/files/8870641/log.txt) No capture though...

Thank you for looking into this. So it is not the usbip client causing the connection to close, but the usbipd server on the Windows host site?

Hi Frans, I am still not 100% sure the random connections drops are cured by higher TCP keep-alive timeout values. I am perfectly OK of not making these values configurable...

Hi and sorry for the radio silence. If I would kike to try out different `TcpKeepAliveTime` settings, I guess I need to specify them in the Windows Registry? Where exactly?...

Ok, I believe I figured it out by starring at the code long enough, is the following a valid example? ```usbipd server usbipd:TcpKeepAliveTime=60000 usbipd:TcpKeepAliveInterval=1000```

Thanks Frans! We're still seeing connection drops. I'll open a new issue to discuss: #538

I believe this could help, however we'd need to change PyOxidizer code and use the nativeTLS stuff as described here: https://github.com/JuliaLang/juliaup/issues/170