Networking mirrored can't access to windows by 127.0.0.1:port with WSL2 about wsl HOT 21 CLOSED

Try executing the command

sudo systemctl disable network-manager.service

followed by running wsl.exe --shutdown in PowerShell, and then restart WSL again.

from wsl.

Try executing the command

sudo systemctl disable network-manager.service

followed by running wsl.exe --shutdown in PowerShell, and then restart WSL again.

Ohhh!!!

It is working now. Thank you very much.

I tried disabling every service until I reached network-manager.service, and finally, the mirrored functionality started working properly. It took me a significant amount of time to figure this out.

from wsl.

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Open similar issues:

• Networking mirrored can't work on WSL2 (#10632), similarity score: 0.84

Closed similar issues:

• Mirrored network, port listen in Windows not accessable from WSL using external LAN ip. (#10611), similarity score: 0.87
• [WSL 2] LAN hosts can't reach ports listened on 0.0.0.0 in WSL 2 while Windows can (#4527), similarity score: 0.83
• WSL2 http.Server not accessible from Windows11 [experimental] networkingMode=mirrored (#10785), similarity score: 0.83
• WSL 2.0.6 mirrored network - can not connect to Docker container ports from Windows host (#10683), similarity score: 0.82

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

from wsl.

I did not changed anything and a couple of weeks ago all worked well.

from wsl.

Afte view this issue (#10632), I have checked the port binding in wsl:

Can wsl use the port same with windows?

1. execute python -m http.server --bind 0.0.0.0 with windows, success
2. execute python3 -m http.server --bind 0.0.0.0 with wsl, failed.

Can windows access web started by wsl?

When I use edge in windows, I can access the web by 192.168.0.102, but 127.0.0.1 is not worked.

from wsl.

What do you get from netstat -an | findstr /c:"7890" | findstr /c:"LISTENING"?

from wsl.

What do you get from netstat -an | findstr /c:"7890" | findstr /c:"LISTENING"?

This is the result.

from wsl.

Similar issue.
If I kill all WSL processes and restart it, I can access Windows localhost:port again.
But if I leave it running for hours, I cannot access Windows localhost:port from WSL.

from wsl.

Similar issue. If I kill all WSL processes and restart it, I can access Windows localhost:port again. But if I leave it running for hours, I cannot access Windows localhost:port from WSL.

This method does not work for me.

from wsl.

Similar issue.
If I kill all WSL processes and restart it, I can access Windows localhost:port again.
But if I leave it running for hours, I cannot access Windows localhost:port from WSL.

Did not work for me too.

from wsl.

If you want to connect to the host from the WSL container by the IP address assigned you'll need to connect to 127.0.01. If you want to connect to the assigned address, you need to set [experimental] hostAddressLoopback=true (see https://learn.microsoft.com/en-us/windows/wsl/wsl-config#experimental-configuration-settings).

But in the original repro, it was sent to 127.0.0.1, so that's valid.
We see a RST immediately returned.

15:44:12.145100 IP 127.0.0.1.60816 > 127.0.0.1.7890: Flags [S], seq 2455237139, win 65495, options [mss 65495,sackOK,TS val 260823200 ecr 0,nop,wscale 7], length 0
15:44:12.145107 IP 127.0.0.1.7890 > 127.0.0.1.60816: Flags [R.], seq 0, ack 2455237140, win 0, length 0

Everything else looks setup correctly (Hyper-V Firewall is setup correctly).
This suggests one of 2 things that I can see:

1. the app wasn't bound & listening to that port at the time
2. Cisco's VMWare solution has filters that are causing issues
   (I only bring up VMWare as we have observed many interop issues in the past).

from wsl.

If you want to connect to the host from the WSL container by the IP address assigned you'll need to connect to 127.0.01. If you want to connect to the assigned address, you need to set [experimental] hostAddressLoopback=true (see https://learn.microsoft.com/en-us/windows/wsl/wsl-config#experimental-configuration-settings).

But in the original repro, it was sent to 127.0.0.1, so that's valid. We see a RST immediately returned.

15:44:12.145100 IP 127.0.0.1.60816 > 127.0.0.1.7890: Flags [S], seq 2455237139, win 65495, options [mss 65495,sackOK,TS val 260823200 ecr 0,nop,wscale 7], length 0 15:44:12.145107 IP 127.0.0.1.7890 > 127.0.0.1.60816: Flags [R.], seq 0, ack 2455237140, win 0, length 0

Everything else looks setup correctly (Hyper-V Firewall is setup correctly). This suggests one of 2 things that I can see:

1. the app wasn't bound & listening to that port at the time
2. Cisco's VMWare solution has filters that are causing issues
   (I only bring up VMWare as we have observed many interop issues in the past).

I have uninstalled the VMWare just now and reboot the computer, but it still not work.

I think the app was bound the port at the time, because I can not access google without this proxy (google was blocked in my country).

And now I can access google(port is work in host), but telnet 127.0.0.1 7890 still can not work with wsl.

from wsl.

If you want to connect to the host from the WSL container by the IP address assigned you'll need to connect to 127.0.01. If you want to connect to the assigned address, you need to set [experimental] hostAddressLoopback=true (see https://learn.microsoft.com/en-us/windows/wsl/wsl-config#experimental-configuration-settings).

But in the original repro, it was sent to 127.0.0.1, so that's valid. We see a RST immediately returned.

15:44:12.145100 IP 127.0.0.1.60816 > 127.0.0.1.7890: Flags [S], seq 2455237139, win 65495, options [mss 65495,sackOK,TS val 260823200 ecr 0,nop,wscale 7], length 0 15:44:12.145107 IP 127.0.0.1.7890 > 127.0.0.1.60816: Flags [R.], seq 0, ack 2455237140, win 0, length 0

Everything else looks setup correctly (Hyper-V Firewall is setup correctly). This suggests one of 2 things that I can see:

1. the app wasn't bound & listening to that port at the time

2. Cisco's VMWare solution has filters that are causing issues
   (I only bring up VMWare as we have observed many interop issues in the past).

But I used mirrored mode and no VMWare.

from wsl.

Try executing the command

sudo systemctl disable network-manager.service

followed by running wsl.exe --shutdown in PowerShell, and then restart WSL again.

Ohhh!!!

It is working now. Thank you very much.

from wsl.

solved.

Answer:

#11312 (comment)

from wsl.

Try executing the command

sudo systemctl disable network-manager.service

followed by running wsl.exe --shutdown in PowerShell, and then restart WSL again.

Similar issue. It works for me. Thanks so much!

from wsl.

Try executing the command

sudo systemctl disable network-manager.service

followed by running wsl.exe --shutdown in PowerShell, and then restart WSL again.

Solved my problem, thanks

from wsl.

Try executing the command

sudo systemctl disable network-manager.service

followed by running wsl.exe --shutdown in PowerShell, and then restart WSL again.

Failed to disable unit: Unit file network-manager.service does not exist.😢

from wsl.

Try executing the command

sudo systemctl disable network-manager.service

followed by running wsl.exe --shutdown in PowerShell, and then restart WSL again.

Failed to disable unit: Unit file network-manager.service does not exist.😢

The NetworkManager service has been named NetworkManager. You can see https://askubuntu.com/questions/1371275/where-has-the-network-manager-service-in-21-10-gone for details.

from wsl.

Try executing the command

sudo systemctl disable network-manager.service

followed by running wsl.exe --shutdown in PowerShell, and then restart WSL again.

Failed to disable unit: Unit file network-manager.service does not exist.😢

The NetworkManager service has been named NetworkManager. You can see https://askubuntu.com/questions/1371275/where-has-the-network-manager-service-in-21-10-gone for details.

Unlucky😢😢, it also show: Failed to disable unit: Unit file NetworkManager.service does not exist.

from wsl.

Try executing the command

sudo systemctl disable network-manager.service

followed by running wsl.exe --shutdown in PowerShell, and then restart WSL again.

Failed to disable unit: Unit file network-manager.service does not exist.😢

The NetworkManager service has been named NetworkManager. You can see https://askubuntu.com/questions/1371275/where-has-the-network-manager-service-in-21-10-gone for details.

Unlucky😢😢, it also show: Failed to disable unit: Unit file NetworkManager.service does not exist.

same issue here

from wsl.