Uploaded image for project: 'Facter'
  1. Facter
  2. FACT-1776

FreeBSD network facts resolution surprise

    Details

    • Type: Bug
    • Status: Accepted
    • Priority: Normal
    • Resolution: Unresolved
    • Affects Version/s: FACT 3.9.0
    • Fix Version/s: None
    • Component/s: None
    • Template:
    • Team:
      Platform OS
    • Method Found:
      Needs Assessment
    • QA Risk Assessment:
      Needs Assessment

      Description

      I'm running FreeBSD 11.1 with facter 3.9 and I have a few jails that bind an address to the lo1 interface which is a local loopback address and perhap not an AF_LINK, but I don't know. To execute the facts in a jail, I run the following.

      #iocage exec git2 facter networking
      {
        domain => "lab.example.com",
        fqdn => "git2.lab.example.com",
        hostname => "git2",
        interfaces => {
          igb0 => {
            bindings => [
              {
                address => "10.0.0.122",
                netmask => "255.255.255.255",
                network => "10.0.0.122"
              }
            ],
            ip => "10.0.0.122",
            mac => "00:25:90:aa:aa:cc",
            mtu => 1500,
            netmask => "255.255.255.255",
            network => "10.0.0.122"
          },
          igb1 => {
            mac => "00:25:90:aa:aa:cd",
            mtu => 9000
          },
          lagg0 => {
            mac => "00:25:90:aa:aa:cd",
            mtu => 9000
          },
          lo0 => {
            mtu => 16384
          },
          lo1 => {
            bindings6 => [
              {
                address => "2000:100:20::105",
                netmask => "ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff",
                network => "2000:100:20::105"
              }
            ],
            ip6 => "2000:100:20::105",
            mtu => 9000,
            netmask6 => "ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff",
            network6 => "2000:100:20::105"
          }
        },
        ip => "10.0.0.122",
        mac => "00:25:90:aa:aa:cc",
        mtu => 1500,
        netmask => "255.255.255.255",
        network => "10.0.0.122",
        primary => "igb0"
      }
      

      Since the igb0 interface has an ipv4 address, it shows up under networking.ip4, but the ipv6 address from lo1 does not show up under inetworking.ip6, even though its the only ipv6 address that the jail has. I believe this is also causing facter ipaddress6 to return empty, which is a heavily used fact in my environment.

      I suspect that the desired behaviour for me here is that if an interface has an address on ip6, and it is the only interface with ip6, then it should be promoted to ipaddress6. Perhaps the reason for this issue I'm bumping into is due to being bound to a localhost interface of lo1.

        Attachments

          Activity

            jsd-sla-details-panel

              People

              • Assignee:
                Unassigned
                Reporter:
                xaque208 Zach L
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:

                  Zendesk Support