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.
e.g. http://blueos will 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 using hosts file instead of DNS) resolves to the IPv6 address.
Caveats:
When testing this, use service nginx reload NOT service nginx restart. In the blueos-core image, the config file nginx.conf is loaded from /home/pi/tools/nginx/ instead of /etc/nginx/. Using restart will cause the server to use the default config
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