-
Notifications
You must be signed in to change notification settings - Fork 834
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WSL Cannot undertand linux host with mirrored mode and custom domain name #10813
Comments
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:
Closed similar issues:
|
After a new fresh install with Ubuntu 22.0.4 it's the same, connection refused |
Could you please follow the steps below and attach the diagnostic logs? https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#collect-wsl-logs-for-networking-issues |
@Dokman, can you please try setting dnsTunneling=true, restart WSL and retry your scenario? In mirrored mode, in order for Windows DNS policies (such as the Windows hosts file) to be applied to WSL DNS traffic, dnsTunneling must be enabled thanks |
it doesn't work too. sorry for being inactive too long, i was having troubles i tried with dnsTunneling=true but it doesn't work too |
@Dokman thanks for following up. Can you please collect networking logs using instructions below? The script will create a zip with name starting with "WslNetworkingLogs" https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#collect-wsl-logs-for-networking-issues please also share the name you are trying to resolve and is not working, so we can look for that in the traces thanks |
i'm trying to access to my nginx that i've made but it doesn't work i'll upload the zip |
The log file doesn't contain any WSL traces. Please make sure that you reproduced the issue while the log collection was running. Diagnostic information
|
@Dokman please use the networking script (https://github.com/microsoft/WSL/blob/master/diagnostics/collect-networking-logs.ps1). It looks like you used the regular https://github.com/microsoft/WSL/blob/master/diagnostics/collect-wsl-logs.ps1 can you please also share the name you are trying to resolve? from your description, I see "hostname.name" thanks |
I was trying to resolve localhost and 192.168.1.130 if I can't connect to the IP I cannot connect to the nginx hahahah WSLConfig
|
thanks. a few follow up questions to better understand your scenario how are you configuring the 192.168.1.130 IP? is it an IP assigned to Windows? |
Yes that's my windows IP, so if i want to test it on my end localhost doesn't work too. The network is mirrored, yes, but doesn't loopback or get any feedback from the server. i'm not adding any windows hosts editing there's my log PSA: I've disabled the firewall because it's having error too with firewall disabled too |
Diagnostic information
|
are you connecting from Windows to a Linux server listening on 192.168.1.130? or the opposite way (connecting from Linux to a Windows server listening on 192.168.1.130)? what is the port you are connecting to? |
i'm trying to connect my windows to the linux wsl machine, it's the same machine they are the same ip because it's the same machine |
thanks. from the Linux tcpdump output in the logs you shared, I see SYN packets sent to 192.168.1.130, port 80 reaching Linux, but I don't see a reply from the server listening on 192.168.1.130, port 80 do you have logs from your nginx server (I assume nginx is the server listening on 192.168.1.130, port 80), where you can check if nginx received the connection request? |
idk, i can install an apache if needed PSA: Log with apache2 |
Diagnostic information
|
After adding the firewall Rules works outside my PC but in localhost mode it doesn't work so i can't work in my pc vieweing anything |
thanks for your quick responses and patience for this issue from the latest logs you shared, I see the same case of SYN packets being sent to 192.168.1.130, port 80 reaching Linux, then there is no reply from the server listening on 192.168.1.130, port 80 can you please share the steps you use to install and start the nginx or apache2 server? I can try to reproduce this on my setup. |
I'm using a default config, so i cannot understand how it doesn't connect |
Failed to parse logs. Unexpected file: default.conf Diagnostic information
|
thanks. I tried installing nginx (looking at the /etc/nginx/ folder, nginx has the same default config as you shared) - unfortunately I was not able to repro the issue one additional question: are you running nginx inside a container, such as Docker? a few things to try:
Can you run "systemctl status network-manager.service" and if it shows the service as running, try disabling it using "systemctl disable network-manager.service", then retry your scenario.
Can you run "netstat -tlnp" and verify the output is similar to the one below, showing a listener on port 80 on IPv4 and one listener on IPv6 netstat -tlnp |
My windows was borken after a Windows 11 reinstall worked well |
Windows Version
Microsoft Windows [Versión 10.0.22631.2715]
WSL Version
2.0.11.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.133.1-1
Distro Version
Ubuntu 20.04
Other Software
Docker Desktop: 4.25.2
Repro Steps
Use mirrored in networking, set hosts file in windows to point your lAN ip 192.168.1.x hostname.name
Expected Behavior
Enter into the website
Actual Behavior
Refuses to connect but outside network is working
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: