Fix issue occurring when multiple DNS Servers are configured #72
Conversation
This file contains hidden or 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
When two or more DNS Servers are configured (in my case, via DHCP) on the system, Fakenet would improperly reset the DNS server setting upon exiting to the IP address of my machine, thus causing me to lose internet access. The cause was an unhandle error case in a Windows API call to retrieve network information. The fix was to handle this error case similarly to what is shown here: https://msdn.microsoft.com/en-us/library/windows/desktop/aa365900(v=vs.85).aspx
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
When two or more DNS Servers are configured (in my case, via DHCP)
on the system, Fakenet would improperly reset the DNS server setting
upon exiting to the IP address of my machine, thus causing me to
lose internet access. The cause was an unhandle error case in
a Windows API call to retrieve network information. The fix was
to handle this error case similarly to what is shown here:
https://msdn.microsoft.com/en-us/library/windows/desktop/aa365900(v=vs.85).aspx