Networking - listen for IPv6 connections #2894
Merged
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.
Previously, attempting to connect to the web interface via IPv6 address would fail. Now it succeeds. Same for the mavlink2rest service.
Note this does not affect DNS.
http://blueoswill still resolve to the IPv4 address.This will prevent problems with services that use host networking and connect to
localhost. As mentioned here,getent hosts localhost(resolve usinghostsfile instead of DNS) resolves to the IPv6 address.Caveats:
service nginx reloadNOTservice nginx restart. In theblueos-coreimage, the config filenginx.confis loaded from/home/pi/tools/nginx/instead of/etc/nginx/. Usingrestartwill cause the server to use the default config