Jira (FACT-605) facter ignores RFC 4193 ULAs when creating interface-specific ipaddress6 facts
Title: Message Title
Matthew Pounsett commented on an issue
Re: facter ignores RFC 4193 ULAs when creating interface-specific ipaddress6 facts
This is a fairly simple bug with a simple fix, and could be fixed pretty quickly. I'd caution against dragging other issues into this. FACT-345 has been re-opened as it is similar but unrelated.
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
Jira (FACT-605) facter ignores RFC 4193 ULAs when creating interface-specific ipaddress6 facts
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 :1aa4:5004:106::e891/64 scope global deprecated \ valid_lft forever preferred_lft forever 2: eth0 inet6 :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...
Jira (FACT-605) facter ignores RFC 4193 ULAs when creating interface-specific ipaddress6 facts
Title: Message Title Matthew Pounsett updated an issue Facter / FACT-605 facter ignores RFC 4193 ULAs when creating interface-specific ipaddress6 facts Change By: Matthew Pounsett Assignee: Matthew Pounsett Adrien Thebo Add Comment 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.
Jira (FACT-605) facter ignores RFC 4193 ULAs when creating interface-specific ipaddress6 facts
Title: Message Title
Matthew Pounsett commented on an issue
Re: facter ignores RFC 4193 ULAs when creating interface-specific ipaddress6 facts
Expected values were included in the original report. PE 3 and the FreeBSD hosts both use Ruby 1.9
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
Jira (FACT-605) facter ignores RFC 4193 ULAs when creating interface-specific ipaddress6 facts
Title: Message Title
Adrien Thebo commented on an issue
Re: facter ignores RFC 4193 ULAs when creating interface-specific ipaddress6 facts
What version of Ruby are you using with Facter? Could you provide the expected values of the missing facts?
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.
Jira (FACT-605) facter ignores RFC 4193 ULAs when creating interface-specific ipaddress6 facts
Title: Message Title Adrien Thebo updated an issue Facter / FACT-605 facter ignores RFC 4193 ULAs when creating interface-specific ipaddress6 facts Change By: Adrien Thebo Assignee: Eric Sorenson Matthew Pounsett Add Comment 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.
Jira (FACT-605) facter ignores RFC 4193 ULAs when creating interface-specific ipaddress6 facts
Title: Message Title
Matthew Pounsett updated an issue
Facter / FACT-605
facter ignores RFC 4193 ULAs when creating interface-specific ipaddress6 facts
Change By:
Matthew Pounsett
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 globally unique ipv6 address.In the following example, there should be an ipaddress6_em1 fact with the address fc00::56:9.{code}root@app2:~ # ifconfigem0: flags=8843 metric 0 mtu 1500options=9bether 08:00:27:95:b4:cfinet 192.168.4.9 netmask 0xff00 broadcast 192.168.4.255inet6 fe80::a00:27ff:fe95:b4cf%em0 prefixlen 64 scopeid 0x1 inet6 fc00::4:9 prefixlen 64 inet6 2001:500:a:300::136 prefixlen 64 nd6 options=21media: Ethernet autoselect (1000baseT )status: activeem1: flags=8843 metric 0 mtu 1500options=9bether 08:00:27:b2:fd:ffinet 192.168.56.9 netmask 0xff00 broadcast 192.168.56.255inet6 fe80::a00:27ff:feb2:fdff%em1 prefixlen 64 scopeid 0x3 inet6 fc00::56:9 prefixlen 64 nd6 options=21media: Ethernet autoselect (1000baseT )status: activelo0: flags=8049 metric 0 mtu 16384options=63inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 inet 127.0.0.1 netmask 0xff00 nd6 options=21root@app2:~ # facter | grep ipaddressipaddress => 192.168.4.9ipaddress6 => fc00::4:9ipaddress6_em0 => 2001:500:a:300::136ipaddress_em0 => 192.168.4.9ipaddress_em1 => 192.168.56.9ipaddress_lo0 => 127.0.0.1{code}
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (FACT-605) facter ignores RFC 4193 ULAs when creating interface-specific ipaddress6 facts
Title: Message Title
Matthew Pounsett updated an issue
Facter / FACT-605
facter ignores RFC 4193 ULAs when creating interface-specific ipaddress6 facts
Change By:
Matthew Pounsett
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 globally unique ipv6 address.In the following example, there should be an ipaddress6_em1 fact with the address fc00::56:9. {code} root@app2:~ # ifconfigem0: flags=8843 metric 0 mtu 1500options=9bether 08:00:27:95:b4:cfinet 192.168.4.9 netmask 0xff00 broadcast 192.168.4.255inet6 fe80::a00:27ff:fe95:b4cf%em0 prefixlen 64 scopeid 0x1 inet6 fc00::4:9 prefixlen 64 inet6 2001:500:a:300::136 prefixlen 64 nd6 options=21media: Ethernet autoselect (1000baseT )status: activeem1: flags=8843 metric 0 mtu 1500options=9bether 08:00:27:b2:fd:ffinet 192.168.56.9 netmask 0xff00 broadcast 192.168.56.255inet6 fe80::a00:27ff:feb2:fdff%em1 prefixlen 64 scopeid 0x3 inet6 fc00::56:9 prefixlen 64 nd6 options=21media: Ethernet autoselect (1000baseT )status: activelo0: flags=8049 metric 0 mtu 16384options=63inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 inet 127.0.0.1 netmask 0xff00 nd6 options=21root@app2:~ # facter | grep ipaddressipaddress => 192.168.4.9ipaddress6 => fc00::4:9ipaddress6_em0 => 2001:500:a:300::136ipaddress_em0 => 192.168.4.9ipaddress_em1 => 192.168.56.9ipaddress_lo0 => 127.0.0.1 {code}
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (FACT-605) facter ignores RFC 4193 ULAs when creating interface-specific ipaddress6 facts
Title: Message Title
Matthew Pounsett commented on an issue
Re: facter ignores RFC 4193 ULAs when creating interface-specific ipaddress6 facts
I think I've found the bug. The regexes in facter-1.7.5/lib/facter/util/ip.rb have a character set where they should have a grouping:
:ipaddress6 => /inet6 (?:addr: )?((?![fe80|::1])(?>[0-9,a-f,A-F]*\: {1,2})+[0-9,a-f,A-F]{0,4})/, should be :ipaddress6 => /inet6 (?:addr: )?((?!(fe80|::1))(?>[0-9,a-f,A-F]*\:{1,2}
)+[0-9,a-f,A-F] {0,4}
)/,
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 globally ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message be
Jira (FACT-605) facter ignores RFC 4193 ULAs when creating interface-specific ipaddress6 facts
Title: Message Title
Matthew Pounsett created an issue
Facter / FACT-605
facter ignores RFC 4193 ULAs when creating interface-specific ipaddress6 facts
Issue Type:
Bug
Affects Versions:
1.7.5
Assignee:
Eric Sorenson
Created:
26/Jun/14 10:21 AM
Environment:
FreeBSD 9.2, Unbuntu 12.04 LTS
Priority:
Normal
Reporter:
Matthew Pounsett
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 globally unique ipv6 address.
In the following example, there should be an ipaddress6_em1 fact with the address fc00::56:9.
root@app2:~ # ifconfig em0: flags=8843 metric 0 mtu 1500 options=9b ether 08:00:27:95:b4:cf inet 192.168.4.9 netmask 0xff00 broadcast 192.168.4.255 inet6 fe80::a00:27ff:fe95:b4cf%em0 prefixlen 64 scopeid 0x1 inet6 fc00::4:9 prefixlen 64 inet6 2001:500:a:300::136 prefixlen 64 nd6 options=21 media: Ethernet autoselect (1000baseT ) status: active em1: flags=8843 metric 0 mtu 1500 options=9b ether 08:00:27:b2:fd:ff inet 192.168.56.9 netmask 0xff00 broadcast 192.168.56.255 inet6 fe80::a00:27ff:feb2:fdff%em1 prefixlen 64 scopeid 0x3 inet6 fc00::5
