Network access from WSL2 -> windows host stopped working; How do I find out where the blockage is?
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 33.7k
- Forks
- 1.8k
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 116
Description
System:
Host: Windows 11, with all updates installed.
Software: mysql8.2
Guest: Ubuntu 22.04.5 LTS
Problem:
For the last year+, I have been connecting to the mysql service in the host from WSL2 via 172.26.240.1:3306 successfully. I've been out of office for 2 weeks, but made no configuration changes. Now, when I try to connect, the connection times out with no response.
Note that I can still connect to the DB, successfully, from mysql workbench in the windows host. I can also connect successfully to the outside Internet from the guest. It is specifically the connection from the guest to the host that has stopped working.
The issue appears to be that something is now stopping the connection from the guest to the host.
Where do I start looking to find out what is blocking the connection.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No repository file, test, or entry point is identified. Begin by reproducing the timeout from Ubuntu 22.04.5 to 172.26.240.1:3306 and compare it with the successful Windows MySQL Workbench connection, then trace the WSL2-to-host network path and host-side MySQL access. Done means identifying the blocking layer and restoring guest-to-host access.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- mysql, ubuntu
- Domain
- databases, networking, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100