Wifi tethering (android phone to PC via usb cable) stops when using wsl when downloading things (pulls, npm installs etc)

[Disco-Chef]

note: I am a lowly ruby/rails webdev, so my knowledge of CS and cache and my understanding of all the marvelous things you peeps do for us is non-existent. I have followed the issue submission to the best of my understanding.

Environment

Platform ServicePack Version VersionString

---

Win32NT 10.0.19041.0 Microsoft Windows NT 10.0.19041.0

Distribution version: 20.04
WSL 2 and/or WSL 1: (i think wsl2 but -> ) Linux version 4.19.128-microsoft-standard (oe-user@oe-host) (gcc version 8.2.0 (GCC)) #1 SMP Tue Jun 23 12:58:10 UTC 2020

Steps to reproduce

Use any android phone (I tried 4) that is connected to wifi. Plug it in the pc with a usb cable and then, from the phone's USB settings, select/enable USB tethering.

Perform any action that gets data through the connection (curl, npm install on a big project, git pull etc) cuts the connection abruptly. I cannot use my desktop at this point (I used to have an ethernet connection but since I moved in my new flat, the current router is unreachable without a 25m cable that would obstruct more and so I am trying to tether with some phones' wifi).

Expected behavior

The connection to maintain and the curl's/pulls not to stop 100kb in the process.

Actual behavior

The connection cuts out completely. Need to go back to phone's settings and disable tethering then re-enable it, only to have it cut out again, turning the laptop into a youtube and email device solely.

P.S. using the feedback hub but need to submit the issue to get the link (if i understood correctly)

[Disco-Chef]

P.P.S Seeing as the connection cuts, when i submit the feedback to send the recording of the logs, i cannot get a link to it after hitting Submit :/

[therealkenc]

/dupe #5972 ➡️ #5313

[ghost]

Hi! We've identified this issue as a duplicate of another one that already exists in this repository. This specific instance is being closed in favor of tracking the concern over on the referenced thread.

Thanks for your report!