Delitel

No, it doesn't matter, because I run the server locally.

I was able to see the server in the launcher in the Recent tab after I connected to the server by directly specifying the ip and port of the server in the client startup parameters.

When I start the server in WSL, it is not visible from under windows, in principle, I thought of an error in wsl that udp ports are not being thrown in windows(https://github.com/microsoft/WSL/issues/8783 ) but I can't connect to the server even using the "Direct connection" button along with the WSL ip that I get using "hostname -I" (172.19.38.79). Maybe someone knows how to help me? From the log ss -tuln, it can be seen that the server is running and listening on the necessary ports: udp UNCONN 0 0 0.0.0.0:2302 0.0.0.0:* udp UNCONN 0 0 0.0.0.0:2304 0.0.0.0:* udp UNCONN 0 0 0.0.0.0:27016 0.0.0.0:* I was able to connect to the server via wsl ip, but only by directly specifying the ip and port in the launcher settings. Still, I have a question, why don't I see my server in the launcher list and when I try to connect using the "Direct connection" button, nothing just happens? 

I was able to connect to the server via wsl ip, but only by directly specifying the ip and port in the launcher settings. Still, I have a question, why don't I see my server in the launcher list and when I try to connect using the "Direct connection" button, nothing just happens?

When I start the server in WSL, it is not visible from under windows, in principle, I thought of an error in wsl that udp ports are not being thrown in windows(https://github.com/microsoft/WSL/issues/8783 ) but I can't connect to the server even using the "Direct connection" button along with the WSL ip that I get using "hostname -I" (172.19.38.79). Maybe someone knows how to help me? From the log ss -tuln, it can be seen that the server is running and listening on the necessary ports: udp UNCONN 0 0 0.0.0.0:2302 0.0.0.0:* udp UNCONN 0 0 0.0.0.0:2304 0.0.0.0:* udp UNCONN 0 0 0.0.0.0:27016 0.0.0.0:*