Skip to content

Fix problem with getting machine's current IP address.#129

Open
jon4than wants to merge 1 commit intovisad:masterfrom
jon4than:localhost-fix
Open

Fix problem with getting machine's current IP address.#129
jon4than wants to merge 1 commit intovisad:masterfrom
jon4than:localhost-fix

Conversation

@jon4than
Copy link
Copy Markdown
Contributor

@jon4than jon4than commented Aug 8, 2017

On my Linux machine, the hostname will stay the same regardless of the network I'm on, while macOS will change the hostname according to the whims of DHCP. This behavior is especially noticeable when hopping between wifi networks.

This leads to VisAD attempting to resolve a potentially invalid hostname in an apparent effort to get the current IP (note: not the same thing as loopback/localhost). The commit simply grabs the local address from the extant Socket.

I've tried this on both macOS and Linux and there were no problems, though the pull request should remain unmerged so that we can check Windows.

On my Linux machine, the hostname will stay the same regardless of the
network I'm on, while macOS will change the hostname (particularly
evident when using wifi).

This leads to attempting to resolve a potentially invalid hostname in an
apparent effort to get the current IP (note: which is not the same thing
as loopback/localhost). This commit simply grabs the local address from
an extant Socket.
@ctrueden ctrueden force-pushed the master branch 2 times, most recently from 4b00692 to 2aeadff Compare August 9, 2018 19:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant