Uploaded image for project: 'TrueNAS'
  1. TrueNAS
  2. NAS-108078

TrueNAS-12.0-RELEASE + FREENAS-MINI-2.0 == igb0 goes offline

    XMLWordPrintable

Details

    • Medium

    Description

      # Questions concerning TrueNAS-12.0-RELEASE
      1. Why did the upgrade configure all my FREENAS-MINI-2.0 interfaces to use DHCP?
      2. Why did the upgrade cause igb1 to go into promiscuous mode?
      3. Why is the TrueNAS-12.0-FINAL stopping my WebGUI from working on my igb0 interface?

      # Overview
      For the past month or so, I've been running my FREENAS-MINI-2.0 under TrueNAS-12.0-RC1 without incident.   My configuration was: 
       - web access is set to 0.0.0.0 
       - igb0 is assigned by DHCP to 192.168.10.32
       - IPMI - Channel-1 is statically assigned 192.168.10.30
       - IPMI - Channel-2 is statically assigned 192.168.10.31
       - igb1 is statically assigned 192.168.9.17

      (My deployment goal is igb0 and IPMI are on a protected network (192.168.10.0/24) for WebGUI,  SAMBA services and IPMI access.  igb1 is being prepared as a DMZ subnet (192.168.9.0/24) for WAN services such as TrueNAS Jails like rslsync.  Eventually, I want to restrict the WebGUI to 192.168.10.32).

      Without warning four days ahead of TrueNAS-12.0-RELEASE, the WebGUI on https://192.168.10.32 stopped responding.  And now that I've upgraded to TrueNAS-12.0-RELEASE, the questions I've cited are open and unanswered.  NOTE: With the upgrade to TrueNAS-12.0-RELEASE, all my interfaces (igb0, IPMI and igb1) are now set to DHCP, rather than a mix of STATIC and DHCP.  And that igb1 is now running in promiscuous mode whereas I thought that was always to be igb0 due to its IPMI integration.

      # Diagnostics

      ## igb0
      > # dhclinet igb0
      > dhclient already running, pid: 1470
      > # ifconfig igb0
      > igb0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=e527bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCS UM,TSO4,TSO6,LRO,WOL_MAGIC,VLAN_HWFILTER,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6>
      >        ether d0:50:99:d0:b8:4b
      >        inet 192.168.10.32 netmask 0xffffff00 broadcast 192.168.10.255
      >        media: Ethernet autoselec

      note: igb0 does not respond to pings from other network connected devices on the 192.168.10.0/24 network.

      ## igb1
      > # dhclinet igb0
      > dhclient already running, pid: 1412
      ># ifconfig igb1
      >  igb1: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=a520b9<RXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,WOL_MAGIC,VLAN_HWFILTER,VLAN_HWTSO,RXCSUM_IPV6>
       >       ether d0:50:99:d0:b8:4c
       >       inet 192.168.9.17 netmask 0xffffff00 broadcast 192.168.9.255
       >       media: Ethernet autoselect (1000baseT <full-duplex>)
       

      Attachments

        Attachments

          JEditor

            Activity

              People

                releng Triage Team
                stumpy Chase Turner
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: