Fix the connection between server and tracker when using WSL2 #17349
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There is a bug when we use WSL2 or other virtual machine in NAT mode as host, the host can find the device easily, but when device respond to the host, it will lose the device ip address, in this case, host will just try to find a IP that is used for visiting from virtual machine(e,g, WSL2, 172.xxx.xxx.xxx) to physical host, this IP cannot be used to visit device, this will make the server in device print"no incoming connections ", because the host cannot find the device
To fix the bug, I just pass the real IP of device to host,which can solve this problem. But this fix need Internet to get device IP, I wonder if there is a better way.
