It proved confusing for users who entered a DUID as a certain type to
see the resulting DUID file displayed as a "Raw DUID" upon page reload.
Still work with dhcp6c_duid file data, but parse it and show the Form
corresponding to the DUID type with the inputs filled in, so the user
sees what she previously entered.
Raw edits to the DUID file are still possible.
dhcp6c stores the entirety of the OPTION_CLIENTID option in DHCPv6 datagrams in
its DUID file (named dhcp6c_duid), except for the option code itself. The first
two octets in the DUID file are the option-len field, and are saved according to
machine order. The remainder is the option-data field in network order.
Support configuring current and future DUID types in webConfigurator.
Save and read option-len correctly in the DUID file for the machine type (was
probably broken before on ARM).
DHCPv6 option fmt: https://tools.ietf.org/html/rfc3315#section-22.1
OPTION_CLIENTID: https://tools.ietf.org/html/rfc3315#section-22.2
DUID types: https://tools.ietf.org/html/rfc3315#section-9.1,
https://tools.ietf.org/html/rfc6355
If IPv6 is disallowed in system->advanced->network, then any IPv6 lookups by Unbound will always be blocked, so there's no point sending them.
The practical purpose is that they also clog up the log and may fractionally slow down the resolver because the resolver then has to deal with IPv6 not replying, fallback lookups, etc.
I'm aware that we state that the system setting doesn't affect any service, but in this case the service simply doesn't send packets that we know will be blocked anyway on egress, so it's probably not going to be an issue. If it is, we can add an explicit "Disable IPv6" setting to this and other functions, but then if IPv6 is later used, the user has to remember to unset "IPv6 not allowed" in all the pages they were set, which is a pain and pretty much duplicates the main setting for all practical purposes.
At the moment verbosity is a bare list of digits, 0 to 5. No explanation, nothing else. This PR replaces the visible text by user-friendly info as to what will be logged. Source is https://www.unbound.net/documentation/unbound.conf.html
removed unused parameters from definition of convert_real_interface_to_friendly_interface_name_fast()
interfaces_assign.php: removed profiling code
removed unncessary comments
shortened some comment blocks
removed parameters from a function call that didn't use them
