Jira (FACT-605) facter incorrectly filters localhost and link-local IPv6 addresses when creating interface-specific ipaddress6 facts

2014-09-03 Thread Matthew Pounsett (JIRA) 
Title: Message Title










 

 Matthew Pounsett updated an issue


















 Facter /  FACT-605



  facter incorrectly filters localhost and link-local IPv6 addresses when creating interface-specific ipaddress6 facts 










Change By:

 Matthew Pounsett




Affects Version/s:

 2.1.0












   

 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 incorrectly filters localhost and link-local IPv6 addresses when creating interface-specific ipaddress6 facts

2014-07-17 Thread Matthew Pounsett (JIRA) 
Title: Message Title










 

 Matthew Pounsett updated an issue


















 Facter /  FACT-605



  facter incorrectly filters localhost and link-local IPv6 addresses when creating interface-specific ipaddress6 facts 










Change By:

 Matthew Pounsett




Summary:

 facter ignoresRFC4193ULAs incorrectlyfilterslocalhostandlink-localIPv6addresses whencreatinginterface-specificipaddress6facts












   

 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

2014-07-02 Thread Matthew Pounsett (JIRA) 
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

2014-06-27 Thread Matthew Pounsett (JIRA) 
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

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

2014-06-27 Thread Matthew Pounsett (JIRA) 
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:

 MatthewPounsett AdrienThebo












   

 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

2014-06-26 Thread Matthew Pounsett (JIRA) 
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=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=9bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM 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=21PERFORMNUD,AUTO_LINKLOCAL media: Ethernet autoselect (1000baseT full-duplex) status: active em1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500

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

2014-06-26 Thread Matthew Pounsett (JIRA) 
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 because

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

2014-06-26 Thread Matthew Pounsett (JIRA) 
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









 FacterwilluseRFC4193addresseswhencreatingtheipaddress6fact,butignoresthemwhenittriestocreateinterface-specificipaddress6_${interface}facts.Itlookslikeinthelattercaseitistreatingthemthesameaslink-localaddresses.Sincetheseareusable,routableaddresseswithinaLAN,theyshouldbetreatedthesameasanygloballyuniqueipv6address.Inthefollowingexample,thereshouldbeanipaddress6_em1factwiththeaddressfc00::56:9. {code} root@app2:~#ifconfigem0:flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICASTmetric0mtu1500options=9bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUMether08:00:27:95:b4:cfinet192.168.4.9netmask0xff00broadcast192.168.4.255inet6fe80::a00:27ff:fe95:b4cf%em0prefixlen64scopeid0x1inet6fc00::4:9prefixlen64inet62001:500:a:300::136prefixlen64nd6options=21PERFORMNUD,AUTO_LINKLOCALmedia:Ethernetautoselect(1000baseTfull-duplex)status:activeem1:flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICASTmetric0mtu1500options=9bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUMether08:00:27:b2:fd:ffinet192.168.56.9netmask0xff00broadcast192.168.56.255inet6fe80::a00:27ff:feb2:fdff%em1prefixlen64scopeid0x3inet6fc00::56:9prefixlen64nd6options=21PERFORMNUD,AUTO_LINKLOCALmedia:Ethernetautoselect(1000baseTfull-duplex)status:activelo0:flags=8049UP,LOOPBACK,RUNNING,MULTICASTmetric0mtu16384options=63RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6inet6::1prefixlen128inet6fe80::1%lo0prefixlen64scopeid0x4inet127.0.0.1netmask0xff00nd6options=21PERFORMNUD,AUTO_LINKLOCALroot@app2:~#facter|grepipaddressipaddress=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

2014-06-26 Thread Matthew Pounsett (JIRA) 
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









 FacterwilluseRFC4193addresseswhencreatingtheipaddress6fact,butignoresthemwhenittriestocreateinterface-specificipaddress6_$ \ {interface \ }facts.Itlookslikeinthelattercaseitistreatingthemthesameaslink-localaddresses.Sincetheseareusable,routableaddresseswithinaLAN,theyshouldbetreatedthesameasanygloballyuniqueipv6address.Inthefollowingexample,thereshouldbeanipaddress6_em1factwiththeaddressfc00::56:9.{code}root@app2:~#ifconfigem0:flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICASTmetric0mtu1500options=9bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUMether08:00:27:95:b4:cfinet192.168.4.9netmask0xff00broadcast192.168.4.255inet6fe80::a00:27ff:fe95:b4cf%em0prefixlen64scopeid0x1inet6fc00::4:9prefixlen64inet62001:500:a:300::136prefixlen64nd6options=21PERFORMNUD,AUTO_LINKLOCALmedia:Ethernetautoselect(1000baseTfull-duplex)status:activeem1:flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICASTmetric0mtu1500options=9bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUMether08:00:27:b2:fd:ffinet192.168.56.9netmask0xff00broadcast192.168.56.255inet6fe80::a00:27ff:feb2:fdff%em1prefixlen64scopeid0x3inet6fc00::56:9prefixlen64nd6options=21PERFORMNUD,AUTO_LINKLOCALmedia:Ethernetautoselect(1000baseTfull-duplex)status:activelo0:flags=8049UP,LOOPBACK,RUNNING,MULTICASTmetric0mtu16384options=63RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6inet6::1prefixlen128inet6fe80::1%lo0prefixlen64scopeid0x4inet127.0.0.1netmask0xff00nd6options=21PERFORMNUD,AUTO_LINKLOCALroot@app2:~#facter|grepipaddressipaddress=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)