Jira (FACT-605) facter ignores RFC 4193 ULAs when creating interface-specific ipaddress6 facts

[Bernd Zeimetz (JIRA)]

Title: Message Title

Bernd Zeimetz commented on an issue   Re: facter ignores RFC 4193 ULAs when creating interface-specific ipaddress6 facts The first major problem is that the ipaddress6 fact uses ifconfig -a, which is deprectaed since a longish time and - which is much more important - is not able to show all IP addresses which are assigned to an interface. A good start would be something like this: ip -o -6 a sh | grep -Ev 'inet6 (fe80:|::1)' 2: eth0 inet6 xxxx:1aa4:5004:106::e891/64 scope global deprecated \ valid_lft forever preferred_lft forever 2: eth0 inet6 xxxx:1aa8:5004:106::6aaf/64 scope global \ valid_lft forever preferred_lft forever Non deprecated addresses should probably be listed first. See http://www.davidc.net/networking/ipv6-source-address-selection-linux for details. WIthout looking at the code I'm kinde sure that the ipaddress fact has similar issues, at least regarding the usage of the deprecated ifconfig tool. Add Comment   Facter / FACT-605 facter ignores RFC 4193 ULAs when creating interface-specific ipaddress6 facts Facter will use RFC 4193 addresses when creating the ipaddress6 fact, but ignores them when it tries to create interface-specific ipaddress6_$\{interface\} facts. It looks like in the latter case it is treating them the same as link-local addresses. Since these are usable, routable addresses within a LAN, they should be treated the same as any globall... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.