Networking mirrored can't access to windows by 127.0.0.1:port with WSL2 #11312

msojocs · 2024-03-16T07:57:50Z

Windows Version

Microsoft Windows [版本 10.0.22631.3296]

WSL Version

2.1.5.0

Are you using WSL 1 or WSL 2?

WSL 2
WSL 1

Kernel Version

5.15.146.1-microsoft-standard-WSL2

Distro Version

ubuntu 20.04

Other Software

Docker desktop was uninstalled from the windows system.

Repro Steps

Information

My laptop's IP is 192.168.0.102 in WLAN.

Is was worked for me before. But after I reset my system, I can not make it work again.

Start a clash app with port 7890
Go into the wsl environment
Execute command telnet 127.0.0.1 7890
Not connected

First

.wslconfig

[wsl2]
networkingMode=mirrored

commands and result

detail

msojocs@DESKTOP-1TV4OAG:~$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:50:56:c0:00:08 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::9c5b:a645:98b4:bfc2/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
3: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether da:80:83:b3:d6:cb brd ff:ff:ff:ff:ff:ff
4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:50:56:c0:00:01 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::de9f:1113:2891:d898/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
5: loopback0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:15:5d:e1:6c:93 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::3b9f:eb69:8d5e:9e71/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
6: eth3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether d8:80:83:b3:d6:cb brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.102/24 brd 192.168.0.255 scope global noprefixroute eth3
       valid_lft forever preferred_lft forever
    inet6 fe80::7df1:6f90:3370:4cd1/64 scope link nodad noprefixroute
       valid_lft forever preferred_lft forever
7: eth4: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether fa:80:83:b3:d6:cb brd ff:ff:ff:ff:ff:ff
8: eth5: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether ea:80:83:b3:d6:cb brd ff:ff:ff:ff:ff:ff
msojocs@DESKTOP-1TV4OAG:~$ telnet 127.0.0.1 7890
Trying 127.0.0.1...
telnet: Unable to connect to remote host: Connection refused
msojocs@DESKTOP-1TV4OAG:~$ telnet 192.168.0.102 7890
Trying 192.168.0.102...
telnet: Unable to connect to remote host: Connection refused
msojocs@DESKTOP-1TV4OAG:~$

Second

.wslconfig

[wsl2]
networkingMode=mirrored
[experimental]
hostAddressLoopback=true

commands and result

detail

msojocs@DESKTOP-1TV4OAG:~$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:50:56:c0:00:08 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::9c5b:a645:98b4:bfc2/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether da:80:83:b3:d6:cb brd ff:ff:ff:ff:ff:ff
    inet6 fe80::bf84:bc17:2e88:c5c0/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:50:56:c0:00:01 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::de9f:1113:2891:d898/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
5: loopback0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:15:5d:e1:6c:93 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::3b9f:eb69:8d5e:9e71/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
6: eth3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether d8:80:83:b3:d6:cb brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.102/24 brd 192.168.0.255 scope global noprefixroute eth3
       valid_lft forever preferred_lft forever
    inet6 fe80::7df1:6f90:3370:4cd1/64 scope link nodad noprefixroute
       valid_lft forever preferred_lft forever
7: eth4: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether fa:80:83:b3:d6:cb brd ff:ff:ff:ff:ff:ff
8: eth5: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether ea:80:83:b3:d6:cb brd ff:ff:ff:ff:ff:ff
msojocs@DESKTOP-1TV4OAG:~$ telnet 127.0.0.1 7890
Trying 127.0.0.1...
telnet: Unable to connect to remote host: Connection refused
msojocs@DESKTOP-1TV4OAG:~$ telnet 192.168.0.102 7890
Trying 192.168.0.102...
Connected to 192.168.0.102.
Escape character is '^]'.

Expected Behavior

The command telnet 127.0.0.1 7890 can success.

Actual Behavior

The command telnet 127.0.0.1 7890 is failed.

Diagnostic Logs

Log

Collected log

Steps:

execute wsl --shutdown
execute .\collect-networking-logs.ps1
execute wsl
execute curl 127.0.0.1:7890
execute telnet 127.0.0.1 7890
execute telnet 192.168.0.102 7890

WslNetworkingLogs-2024-03-16_15-43-33.zip

Other

cat /etc/resolv.conf
# This file was automatically generated by WSL. To stop automatic generation of this file, add the following entry to /etc/wsl.conf:
# [network]
# generateResolvConf = false
nameserver 180.76.76.76
nameserver 223.6.6.6

The text was updated successfully, but these errors were encountered:

github-actions · 2024-03-16T08:00:24Z

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.

msojocs · 2024-03-16T08:17:52Z

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

Can wsl use the port same with windows?

execute python -m http.server --bind 0.0.0.0 with windows, success
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.

pmartincic · 2024-03-19T22:57:00Z

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

msojocs · 2024-03-20T01:01:25Z

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

This is the result.

pffang · 2024-03-20T01:29:52Z

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.

msojocs · 2024-03-20T06:38:20Z

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.

GitUser200607 · 2024-03-25T12:18:56Z

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.

keith-horton · 2024-03-28T01:53:38Z

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:

the app wasn't bound & listening to that port at the time
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).

msojocs · 2024-03-28T02:17:37Z

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:

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

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.

pffang · 2024-03-28T02:44:38Z

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.

GitUser200607 · 2024-03-28T07:26:09Z

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

wangyw6716 · 2024-04-01T07:16:29Z

Try executing the command

sudo systemctl disable network-manager.service

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

msojocs · 2024-04-01T07:25:21Z

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.

wangyw6716 · 2024-04-01T07:31:09Z

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.

msojocs · 2024-04-01T11:58:27Z

solved.

Answer:

#11312 (comment)

yunus-sun · 2024-04-07T12:32:34Z

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!

qgyhd1234 · 2024-04-10T07:06:32Z

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

Kutius · 2024-05-14T06:07:40Z

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.😢

gsxgoldenlegendary · 2024-05-17T05:33:58Z

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.

Kutius · 2024-05-27T09:34:53Z

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.

pmartincic added the needs-author-feedback label Mar 19, 2024

microsoft-github-policy-service bot removed the needs-author-feedback label Mar 20, 2024

leorg99 mentioned this issue Mar 21, 2024

Split DNS problems #11321

Open

2 tasks

OneBlue added the network label Mar 21, 2024

msojocs closed this as completed Apr 1, 2024

github-actions bot mentioned this issue May 19, 2024

Networking mirrored, WSL2 and the host machine are unable to access each other's services bidirectionally. #11600

Open

2 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Networking mirrored can't access to windows by 127.0.0.1:port with WSL2 #11312

Networking mirrored can't access to windows by 127.0.0.1:port with WSL2 #11312

msojocs commented Mar 16, 2024

github-actions bot commented Mar 16, 2024

msojocs commented Mar 16, 2024 •

edited

pmartincic commented Mar 19, 2024

msojocs commented Mar 20, 2024

pffang commented Mar 20, 2024

msojocs commented Mar 20, 2024

GitUser200607 commented Mar 25, 2024 •

edited

keith-horton commented Mar 28, 2024

msojocs commented Mar 28, 2024

pffang commented Mar 28, 2024

GitUser200607 commented Mar 28, 2024 •

edited

wangyw6716 commented Apr 1, 2024

msojocs commented Apr 1, 2024

wangyw6716 commented Apr 1, 2024

msojocs commented Apr 1, 2024 •

edited

yunus-sun commented Apr 7, 2024

qgyhd1234 commented Apr 10, 2024

Kutius commented May 14, 2024

gsxgoldenlegendary commented May 17, 2024

Kutius commented May 27, 2024

Networking mirrored can't access to windows by 127.0.0.1:port with WSL2 #11312

Networking mirrored can't access to windows by 127.0.0.1:port with WSL2 #11312

Comments

msojocs commented Mar 16, 2024

Windows Version

WSL Version

Are you using WSL 1 or WSL 2?

Kernel Version

Distro Version

Other Software

Repro Steps

Information

First

.wslconfig

commands and result

Second

.wslconfig

commands and result

Expected Behavior

Actual Behavior

Diagnostic Logs

Log

Collected log

Other

github-actions bot commented Mar 16, 2024

Open similar issues:

Closed similar issues:

msojocs commented Mar 16, 2024 • edited

Can wsl use the port same with windows?

Can windows access web started by wsl?

pmartincic commented Mar 19, 2024

msojocs commented Mar 20, 2024

pffang commented Mar 20, 2024

msojocs commented Mar 20, 2024

GitUser200607 commented Mar 25, 2024 • edited

keith-horton commented Mar 28, 2024

msojocs commented Mar 28, 2024

pffang commented Mar 28, 2024

GitUser200607 commented Mar 28, 2024 • edited

wangyw6716 commented Apr 1, 2024

msojocs commented Apr 1, 2024

wangyw6716 commented Apr 1, 2024

msojocs commented Apr 1, 2024 • edited

yunus-sun commented Apr 7, 2024

qgyhd1234 commented Apr 10, 2024

Kutius commented May 14, 2024

gsxgoldenlegendary commented May 17, 2024

Kutius commented May 27, 2024

msojocs commented Mar 16, 2024 •

edited

GitUser200607 commented Mar 25, 2024 •

edited

GitUser200607 commented Mar 28, 2024 •

edited

msojocs commented Apr 1, 2024 •

edited