Modified UDPCreateListenSocket() #11
Open
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
Modified UDPCreateListenSocket to include a specified ip address to bind socket to (by directing getaddrinfo() to look for a specific IP address instead of NULL, which seems to stop at the first default address, which if an IPv6 address, means we cannot create a listen socket if the system is IPv4)
fearworksmedia
changed the title
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.
Modified UDPCreateListenSocket to include a specified ip address to bind socket to (by directing getaddrinfo() to look for a specific IP address instead of NULL, which seems to stop at the first default address, which if an IPv6 address, means we cannot create a listen socket if the system is IPv4)
This is part of a dirty attempt to get a list of IP addresses on the PC and return them (as a string with each IP address on a new line... because I don't know how else to do it), and then be able to specify whichever one of these we choose when creating a listening socket to bind to a specific IP address instead of being at the mercy of whichever one getaddrinfo() finds first. At least I think that's how it works.