core: change the priority order in static "ipv6.addresses"
The order of addresses matters. For "ipv4.addresses", the list contains the primary address first. For "ipv6.addresses", the order was reverted. This was also documented behavior. The previous patch just changed behavior with respect to relative order of static IPv6 addresses and autoconf6/DHCPv6. As we seem in the mood for changing behavior, here is another one. Now the addresses are interpreted in an order consistent with IPv4 and how one might expect: preferred addresses first.
This commit is contained in:
@@ -946,8 +946,9 @@ nm_setting_ip6_config_class_init(NMSettingIP6ConfigClass *klass)
|
||||
* format: a comma separated list of addresses
|
||||
* description: A list of IPv6 addresses and their prefix length. Multiple addresses
|
||||
* can be separated by comma. For example "2001:db8:85a3::8a2e:370:7334/64, 2001:db8:85a3::5/64".
|
||||
* The addresses are listed in increasing priority, meaning the last address will
|
||||
* be the primary address.
|
||||
* The addresses are listed in decreasing priority, meaning the first address will
|
||||
* be the primary address. This can make a difference with IPv6 source address selection
|
||||
* (RFC 6724, section 5).
|
||||
* ---end---
|
||||
*/
|
||||
_nm_properties_override_gobj(
|
||||
|
Reference in New Issue
Block a user