WSL cannot use proxy with networkingMode=mirrored

[mingo99]

Windows Version

Microsoft Windows [Version 10.0.22631.2715]

WSL Version

2.0.9.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.90.1

Distro Version

Ubuntu20.04

Other Software

No response

Repro Steps

• Set .wslconfig：

[experimental]
autoMemoryReclaim=gradual
networkingMode=mirrored
dnsTunneling=true
firewall=true
autoProxy=true

• wsl --shutdown to stop WSL
• Set proxy port to 7890 in clash for windows and open system proxy
  
• Restart WSL

Expected Behavior

Both WSL and Windows can successfully access google.com(banned in my place) by curl

Actual Behavior

1. Execute curl in Wondows(Powershell)
   • curl google.com succeeded
     
2. Excute curl in WSl

• curl google.com failed
  

Diagnostic Logs

• My log https://github.com/mingo99/wsl2proxy/blob/main/WslNetworkingLogs-2023-11-19_17-03-14.zip
• Generate by https://github.com/microsoft/WSL/blob/master/diagnostics/collect-networking-logs.ps1

[github-actions]

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!

Closed similar issues:

• How to use proxy in WSL? (#2122), similarity score: 0.93
• how to properly set proxy in WSL2 (#5489), similarity score: 0.91
• WSL2 cannot access Windows proxy (#4402), similarity score: 0.90
• How to use WSL behind proxy server? (#1107), similarity score: 0.90
• WSL can not work (#5992), similarity score: 0.83
• WSL doesn't works (#4265), similarity score: 0.82
• WSL doesn't works (#3296), similarity score: 0.82
• The WSL cannot be used (#8933), similarity score: 0.81
• can't use wsl command (#10728), similarity score: 0.80
• WSL connect failed (#4786), similarity score: 0.79

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

[zhaoqiu-china]

try firewall=false?

[mingo99]

try firewall=false?
I've tried, but it still doesn't work

[zhaoqiu-china]

BTW, experimental feature has moved to wsl2.

[mingo99]

yeah，now my .wslconfig is below, but also come same problem

[wsl2]
kernel=C:\\WINDOWS\\System32\\lxss\\tools\\5.15.90.1-kernel-usb
networkingMode=mirrored
dnsTunneling=true
firewall=false
autoProxy=true

[experimental]
sparseVhd=true
autoMemoryReclaim=gradual

[mingo99]

Additionally, access the external network is normal, like ping github.com is ok

[PhyX-Meow]

It may not help but, I tried firewall=false then everything works fine. Did you restart wsl by wsl --shutdown?

[mingo99]

yeah,even reboot computer

[mingo99]

I upgraded from Ubuntu 20.04 to Ubuntu 22.04, and the issue got resolved, although I don't know how it was fixed. The reason I had this idea is that my other computer, which has Ubuntu 22.04 installed, could successfully use the proxy.

[zhaoqiu-china]

@mingo99

I upgraded from Ubuntu 20.04 to Ubuntu 22.04, and the issue got resolved, although I don't know how it was fixed. The reason I had this idea is that my other computer, which has Ubuntu 22.04 installed, could successfully use the proxy.

whether you set the HTTP_PROXY environment variable?

[mingo99]

No, it will set itself.

[KnineF]

我也遇到了这个问题。请问你解决了吗

[mingo99]

升级到 22.04 就没问题了🤣

[HawtinZeng]

Additionally, access the external network is normal, like ping github.com is ok

Me too, but the tip about the local proxy is not mirrored into WSL still appears.And can't ping google.com

[SuAutumn]

I changed the inbound rules of the Clash for windows in firewall, that does work in Ubuntu 20.

[Minphie]

I changed the inbound rules of the Clash for windows in firewall, that does work in Ubuntu 20.
@SuAutumn
怎么改的？我的都勾选了还是不行。

[SuAutumn]

I changed the inbound rules of the Clash for windows in firewall, that does work in Ubuntu 20.
@SuAutumn
怎么改的？我的都勾选了还是不行。

You can curl http://<host_ip>:7890 -v in wsl terminal, get a 4xx status code means that you can successfully visit clash proxy in wsl. otherwise Just Shutdown firewall, and try again.
ps: Please confirm clash allow LAN setting enabled.

[amorZhu]

Try deleting the Linux distribution and reinstalling it.
wsl --unregister <DistributionName>
wsl --install