[BUG] Mirrored Mode

[Dokman]

Port forwarding not working

After setup the mirrored mode if you setup in docker desktop any kind of services like

• Nginx
• Nginx Proxy Manager
• ADGuard Home

Doesn't want to connect to them so the ports are closed or something

i recieved in service always ERR_CONN_RESET

[4-FLOSS-Free-Libre-Open-Source-Software]

Docker desktop only has limited networking vs docker-ce

instead of using wsl2 Mirrored Mode, I would recommend using bridged which results in a real non NATted networking, together with docker-ce unleashing full network capabilities

• Nginx

• Nginx Proxy Manager

• ADGuard Home

all those run under xanmod-kernel-WSL2 without trouble, if configured correctly

[TheRealMintd]

I have this same issue, and mirrored networking is useful since I have a lot of services in WSL that need to connect to services on the host.

[Dokman]

I have this same issue, and mirrored networking is useful since I have a lot of services in WSL that need to connect to services on the host.

I've modified a kernel that can use the mirrored mode and IO.Weight of CgroupsV2 check out my repos

[Dokman]

Docker desktop only has limited networking vs docker-ce

instead of using wsl2 Mirrored Mode, I would recommend using bridged which results in a real non NATted networking, together with docker-ce unleashing full network capabilities

• Nginx
• Nginx Proxy Manager
• ADGuard Home

all those run under xanmod-kernel-WSL2 without trouble, if configured correctly

at 2026 this doesn't work at all, the bridged mode is deprecated and useless

[4-FLOSS-Free-Libre-Open-Source-Software]

Docker desktop only has limited networking vs docker-ce
instead of using wsl2 Mirrored Mode, I would recommend using bridged which results in a real non NATted networking, together with docker-ce unleashing full network capabilities

• Nginx
• Nginx Proxy Manager
• ADGuard Home

all those run under xanmod-kernel-WSL2 without trouble, if configured correctly

at 2026 this doesn't work at all, the bridged mode is deprecated and useless

No, still in 2026 my answer s true and is the only fully unconstrained working network mode in WSL2 that's solving all your connection issues at once for all and for all mentioned services ports problems solved.

Wondering what you are using if you're saying that's not longer working, as it's working everyday in 2026 since using 2026 Kernel Version release 6.18.5-locietta-WSL2-xanmod1 and WSL2 2.7 win11 25h2
If it's not working at all for you, your WSL2 network must be misconfigured.

bridged mode is deprecated when?
No, I followed the upstream issue earlier and Microsoft didn't deprecated it.

[Dokman]

Docker desktop only has limited networking vs docker-ce
instead of using wsl2 Mirrored Mode, I would recommend using bridged which results in a real non NATted networking, together with docker-ce unleashing full network capabilities

• Nginx
• Nginx Proxy Manager
• ADGuard Home

all those run under xanmod-kernel-WSL2 without trouble, if configured correctly

at 2026 this doesn't work at all, the bridged mode is deprecated and useless

No, still in 2026 my answer s true and is the only fully unconstrained working network mode in WSL2 that's solving all your connection issues at once for all and for all mentioned services ports problems solved.

Wondering what you are using if you're saying that's not longer working, as it's working everyday in 2026 since using 2026 Kernel Version release 6.18.5-locietta-WSL2-xanmod1 and WSL2 2.7 win11 25h2 If it's not working at all for you, your WSL2 network must be misconfigured.

bridged mode is deprecated when? No, I followed the upstream issue earlier and Microsoft didn't deprecated it.

where i can follow a guide?

[juzi5201314]

I encountered this bug on the latest WSL (Arch Linux) as well. Mirror mode worked correctly on the original kernel. After installing xanmod-WSL2-zen3 using scoop install, I could no longer access services running in WSL (Docker) from Windows using http://localhost:port/, only receiving ERR_CONNECTION_REFUSED. However, the HTTP service was still accessible from within WSL itself.

[Dokman]

I encountered this bug on the latest WSL (Arch Linux) as well. Mirror mode worked correctly on the original kernel. After installing xanmod-WSL2-zen3 using scoop install, I could no longer access services running in WSL (Docker) from Windows using http://localhost:port/, only receiving ERR_CONNECTION_REFUSED. However, the HTTP service was still accessible from within WSL itself.

it will not be fixed

[Locietta]

Got some time to look into mirrored mode. I actually don't know if it's (solely) a kernel issue. And it really depends on how you set up the service in wsl...

I tested running HTTP services from WSL using kernel 6.6.114.1-microsoft-standard-WSL2 and connecting via telnet from the host. Here’s what I observed on my machine with mirrored mode enabled:

Bind to 127.0.0.1

# from wsl:
$ python3 -m http.server 7788 --bind 127.0.0.1
Serving HTTP on 127.0.0.1 port 7788 (http://127.0.0.1:7788/) ...

# from host:
PS> msys2 telnet 127.0.0.1 7788
Trying 127.0.0.1...
Connected to 127.0.0.1.
Escape character is '^]'
...

Bind to localhost

# from wsl:
$ python3 -m http.server 7788 --bind localhost
Serving HTTP on ::1 port 7788 (http://[::1]:7788/) ...

# from host:
PS> msys2 telnet 127.0.0.1 7788
Trying ::1...
Connection failed: Connection timed out
Trying 127.0.0.1...
telnet: Unable to connect to remote host: Connection refused

Bind to 0.0.0.0

# from wsl:
$ python3 -m http.server 7788 --bind localhost
Serving HTTP on 0.0.0.0 port 7788 (http://0.0.0.0:7788/) ...

# from host:
PS> msys2 telnet localhost 7788
Trying ::1...
Connection failed: Connection timed out
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.

This is the same behavior seen with 6.19.6-locietta-WSL2-xanmod1 on my machine. There's also microsoft/WSL#13013 reporting the similar issue on upstream. I’m not sure what the situation is for you guys though.