Rfc6724 use ipv6 as default
Checklist
- [X] I have read the OpenWISP Contributing Guidelines.
- [X] I have manually tested the changes proposed in this pull request.
- [ ] I have written new test cases for new code and/or updated existing tests for changes to existing code.
- [ ] I have updated the documentation.
Description of Changes
Added uci option management_interface_family 'inet6' Prefer ipv6 on new installations. for IPv4 backward compatibility use "inet" or leave it blank. default prio is "inet" then "inet6" For IPv4 only use "inet". Added uci option management_interface_ula If it set and there is no Public ipv6 than report ula address.
Please review it could broke backward compatibility
It is up for debate whether IPv6 should be the default returned address but this PR contains some pretty useful features regarding the IPv6 selection, such as the filtering of ula addresses and the option to prefer IPv6, when an interface also has an IPv4.
This enables the possibility to use IPv6 for management without the need for a VPN, one would just need to create a firewall rule (on the uplink router) that allows the OpenWISP server to access the relevant ports, given the devices and the server have a gua.
The Server should also ipv6 enabled.
openwisp2_nginx_ipv6: false
https://github.com/openwisp/ansible-openwisp2/blob/8ef0e8ea7f52bedd6286b48ae9e1bcb9e57183f5/defaults/main.yml#L58
The Server should also ipv6 enabled.
openwisp2_nginx_ipv6: false
I have seen users in the past having problems due to this: nginx not starting because they didn't have IPv6. Unfortunately a recurring issue with openwisp is that there's a good amount of users who have problems installing it. Therefore, that setting in the server has been changed to facilitate installation for new users. It's still possible to enable IPv6, but trust me, I am seeing many deployments which do not care at all about it, they're not using IPv6 at all.