Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    XG-7100 - Upgrading from 2.4.4-p2 to 2.4.4-p3 broke DHCP?

    Scheduled Pinned Locked Moved Official Netgate® Hardware
    16 Posts 5 Posters 853 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • V
      victorhooi
      last edited by

      I have a Netgate XG-7100 appliance.

      This was previously running 2.4.4-p2.

      I just did an update to 2.4.4-p3, as well as updating to the latest the Coreboot on the device - and for some reason, DHCP seems to no longer be working - I can't seem to get a DHCP lease on any of the eth1-eth7 ports.

      Any advice on how to troubleshoot this? It seems too coincidental that it stopped working after the 2.4.4-p3 and Coreboot upgrade.

      1 Reply Last reply Reply Quote 0
      • stephenw10S
        stephenw10 Netgate Administrator
        last edited by

        Do you still see a link on the switch ports?

        Do you see dhclient entries in the dhcp logs?

        It's not something we ever saw in testing and we've not seen any other reports of that so I think it must be something specific you your setup. What is the DHCP server there?

        Steve

        1 Reply Last reply Reply Quote 0
        • V
          victorhooi
          last edited by

          Thanks for getting back - I'm so sorry, I needed it working desperately, so I did a factory reset and loaded back the old configuration.

          (I am giving a demo of the whole pfSense + Proxmox + Ceph system in a few hours, so it was just very bad timing - I was just worried about the 2.4.4-p3 security patch, but in hindsight, should have done it on a different machine first.)

          I'm happy to share my config.xml file with you though, if that helps at all?

          I also did save a copy of the upgrade_log file from /conf, in case that's useful?

          upgrade_log.latest.txt

          Currently the X7100 is working in that it's serving traffic, however, I can't SSH or browse to the Web UI - however, I assume this is related to it reinstalling all packages, due to loading a new backup config? (It's been around 5 hours so far).

          1 Reply Last reply Reply Quote 0
          • stephenw10S
            stephenw10 Netgate Administrator
            last edited by

            That log looks clean, nothing unexpected there.

            Do you have any expansion cards in there? SFP modules?

            If shouldn't take longer than, say, 10mins to load packages unless maybe you have a very slow WAN connection.

            It's handing out DHCP leases and is pingable?

            Steve

            1 Reply Last reply Reply Quote 0
            • V
              victorhooi
              last edited by

              No expansion cards (i.e. PCIe cards).

              There are SFP+ modules - Intel 10GBase-LR one, which is going downstream to a switch.

              Our WAN connection is 100 Mbps up/down (i.e. symmetrical).

              Yup, the router is handing out DHCP leases, and is pingable.

              If I try to SSH to it, it hangs here:

              victorhooi-macbookpro5:~ victorhooi$ ssh admin@27.111.246.206
Netgate XG-7100 - Serial: 1436180441 -

              I can go back on-site, and plug in a console cable, if you think there's anything helpful to extract from it?

              Could the coreboot update have done something?

              1 Reply Last reply Reply Quote 0
              • stephenw10S
                stephenw10 Netgate Administrator
                last edited by

                The Coreboot update corrected more PCIe issues. I think I replied to you previously that it allowed me to run a Mellanox card in the 7100 that was previously undetected. If you had had a card in there it might have changed that behaviour.

                Odd connectivity issues on the 7100 can be caused by an incompatible SFP module. It can in some circumstances prevent the ix driver attaching to the NIC. That leaves one missing and changes the interfaces order. Running ifconfig at the console would show that. It's also reported in dmesg at boot.

                Where that is hanging is odd. It could be a lib error in which case the console will show that very obviously as it tries, and fails, to display the menu. Did you completely re-install or just restore a previous config?

                Steve

                1 Reply Last reply Reply Quote 0
                • V
                  victorhooi
                  last edited by

                  I did a factory reset using the console menu - then when it came up, I went to 192.168.1.1, and loaded up the old config.xml configuration file.

                  I'm not on-site at data center anymore, but I can run out there again if needed.

                  From memory, there isn't anything plugged into PCIe slot right now.

                  If I can get console access to the machine, what would you like me to get from it? (Apart from ifconfig and dmesg output)

                  1 Reply Last reply Reply Quote 0
                  • stephenw10S
                    stephenw10 Netgate Administrator
                    last edited by

                    Ok, then that is definitely a config issue of some sort since the factory reset at the console only replaces the config.

                    Hard to explain why SSH is failing like that. Really looks like a filesystem issue but usually that would also break the console. Yet you were able to reset the config from there.

                    I would probably re-install 2.4.4p3 at this point and restore the config into that. I suspect you do have some subtle filesystem issue and that's really the only way to be sure it is resolved.

                    Steve

                    1 Reply Last reply Reply Quote 0
                    • V
                      victorhooi
                      last edited by

                      I came back on-site - I can connect via the console port (Mini-USB).

                      However, I still can't SSH and it hangs at the same point.

                      Is there any way this could be a hardware issue? (We bought several XG-7100's in the last few months)

                      I've also uploaded the following files from /var/log (watchdogd.log seems to be a binary file - which I thought was odd, and is why I uploaded it):

                      • system.log.txt
                      • dhcpd.log.txt
                      • watchdogd.log.txt

                      DHCP is working - but some of our customers were complaining that servers (which are behind this router) are no longer accessible.

                      Output of ifconfig and dmesg are below:

                      [2.4.4-RELEASE][root@angussyd.localdomain]/var/log: ifconfig
ix0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=e400bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6>
        ether 00:08:a2:0e:da:4d
        hwaddr 00:08:a2:0e:da:4d
        inet6 fe80::208:a2ff:fe0e:da4d%ix0 prefixlen 64 scopeid 0x1 
        inet 27.111.246.206 netmask 0xfffffffc broadcast 27.111.246.207 
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        media: Ethernet autoselect (1000baseLX <full-duplex,rxpause,txpause>)
        status: active
ix1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=e500bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,VLAN_HWFILTER,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6>
        ether 00:08:a2:0e:da:4e
        hwaddr 00:08:a2:0e:da:4e
        inet6 fe80::208:a2ff:fe0e:da4e%ix1 prefixlen 64 scopeid 0x2 
        inet 10.0.156.1 netmask 0xffffff00 broadcast 10.0.156.255 
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        media: Ethernet autoselect (10Gbase-LR <full-duplex,rxpause,txpause>)
        status: active
ix2: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=e500bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,VLAN_HWFILTER,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6>
        ether 00:08:a2:0e:da:4f
        hwaddr 00:08:a2:0e:da:4f
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        media: Ethernet autoselect (2500Base-KX <full-duplex,rxpause,txpause>)
        status: active
ix3: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=e500bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,VLAN_HWFILTER,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6>
        ether 00:08:a2:0e:da:4f
        hwaddr 00:08:a2:0e:da:50
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        media: Ethernet autoselect (2500Base-KX <full-duplex,rxpause,txpause>)
        status: active
enc0: flags=0<> metric 0 mtu 1536
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        groups: enc 
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
        options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
        inet6 ::1 prefixlen 128 
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x10 
        inet 127.0.0.1 netmask 0xff000000 
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        groups: lo 
pflog0: flags=100<PROMISC> metric 0 mtu 33160
        groups: pflog 
pfsync0: flags=0<> metric 0 mtu 1500
        groups: pfsync 
        syncpeer: 224.0.0.240 maxupd: 128 defer: on
        syncok: 1
lagg0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=e500bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,VLAN_HWFILTER,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6>
        ether 00:08:a2:0e:da:4f
        inet6 fe80::208:a2ff:fe0e:da4f%lagg0 prefixlen 64 scopeid 0x13 
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        media: Ethernet autoselect
        status: active
        groups: lagg 
        laggproto loadbalance lagghash l2,l3,l4
        laggport: ix2 flags=4<ACTIVE>
        laggport: ix3 flags=4<ACTIVE>
lagg0.4090: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
        ether 00:08:a2:0e:da:4f
        inet6 fe80::208:a2ff:fe0e:da4f%lagg0.4090 prefixlen 64 scopeid 0x14 
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        media: Ethernet autoselect
        status: active
        vlan: 4090 vlanpcp: 0 parent interface: lagg0
        groups: vlan 
lagg0.4091: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
        ether 00:08:a2:0e:da:4f
        inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255 
        inet6 fe80::1:1%lagg0.4091 prefixlen 64 scopeid 0x15 
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        media: Ethernet autoselect
        status: active
        vlan: 4091 vlanpcp: 0 parent interface: lagg0
        groups: vlan 
ix1.10: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
        ether 00:08:a2:0e:da:4e
        inet6 fe80::208:a2ff:fe0e:da4e%ix1.10 prefixlen 64 scopeid 0x16 
        inet 10.0.10.1 netmask 0xffffff00 broadcast 10.0.10.255 
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        media: Ethernet autoselect (10Gbase-LR <full-duplex,rxpause,txpause>)
        status: active
        vlan: 10 vlanpcp: 0 parent interface: ix1
        groups: vlan 
ix1.12: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
        ether 00:08:a2:0e:da:4e
        inet6 fe80::208:a2ff:fe0e:da4e%ix1.12 prefixlen 64 scopeid 0x17 
        inet 10.0.12.1 netmask 0xfffffe00 broadcast 10.0.13.255 
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        media: Ethernet autoselect (10Gbase-LR <full-duplex,rxpause,txpause>)
        status: active
        vlan: 12 vlanpcp: 0 parent interface: ix1
        groups: vlan 
ix1.15: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
        ether 00:08:a2:0e:da:4e
        inet6 fe80::208:a2ff:fe0e:da4e%ix1.15 prefixlen 64 scopeid 0x18 
        inet 10.0.15.1 netmask 0xffffff00 broadcast 10.0.15.255 
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        media: Ethernet autoselect (10Gbase-LR <full-duplex,rxpause,txpause>)
        status: active
        vlan: 15 vlanpcp: 0 parent interface: ix1
        groups: vlan 
ix1.19: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
        ether 00:08:a2:0e:da:4e
        inet6 fe80::208:a2ff:fe0e:da4e%ix1.19 prefixlen 64 scopeid 0x19 
        inet 10.0.19.1 netmask 0xffffff00 broadcast 10.0.19.255 
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        media: Ethernet autoselect (10Gbase-LR <full-duplex,rxpause,txpause>)
        status: active
        vlan: 19 vlanpcp: 0 parent interface: ix1
        groups: vlan

                      And here is the output of dmesg:

                      [2.4.4-RELEASE][root@angussyd.localdomain]/var/log: dmesg
Copyright (c) 1992-2018 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
        The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 11.2-RELEASE-p10 #9 10fea60fdde(factory-RELENG_2_4_4): Thu May 16 06:55:01 EDT 2019
    root@buildbot1-nyi.netgate.com:/build/factory-crossbuild-244/obj/amd64/bwlyKhYx/build/factory-crossbuild-244/pfSense/tmp/FreeBSD-src/sys/pfSense amd64
FreeBSD clang version 6.0.0 (tags/RELEASE_600/final 326565) (based on LLVM 6.0.0)
VT(vga): resolution 640x480
CPU: Intel(R) Atom(TM) CPU C3558 @ 2.20GHz (2200.07-MHz K8-class CPU)
  Origin="GenuineIntel"  Id=0x506f1  Family=0x6  Model=0x5f  Stepping=1
  Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
  Features2=0x4ff8ebbf<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,SDBG,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,RDRAND>
  AMD Features=0x2c100800<SYSCALL,NX,Page1GB,RDTSCP,LM>
  AMD Features2=0x101<LAHF,Prefetch>
  Structured Extended Features=0x2294e283<FSGSBASE,TSCADJ,SMEP,ERMS,NFPUSG,MPX,PQE,RDSEED,SMAP,CLFLUSHOPT,PROCTRACE,SHA>
  Structured Extended Features3=0x2c000000<IBPB,STIBP,ARCH_CAP>
  XSAVE Features=0xf<XSAVEOPT,XSAVEC,XINUSE,XSAVES>
  IA32_ARCH_CAPS=0x1<RDCL_NO>
  VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID,VID,PostIntr
  TSC: P-state invariant, performance statistics
real memory  = 10737418240 (10240 MB)
avail memory = 8204009472 (7823 MB)
Event timer "LAPIC" quality 600
ACPI APIC Table: <CORE   COREBOOT>
WARNING: L1 data cache covers less APIC IDs than a core
0 < 1
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
FreeBSD/SMP: 1 package(s) x 4 core(s)
ioapic0: Changing APIC ID to 2
ioapic0 <Version 2.0> irqs 0-23 on motherboard
SMP: AP CPU #1 Launched!
SMP: AP CPU #3 Launched!
SMP: AP CPU #2 Launched!
Timecounter "TSC-low" frequency 1100035058 Hz quality 1000
ipw_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw.LICENSE.
ipw_bss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
module_register_init: MOD_LOAD (ipw_bss_fw, 0xffffffff80685700, 0) error 1
random: entropy device external interface
ipw_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw.LICENSE.
ipw_ibss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
module_register_init: MOD_LOAD (ipw_ibss_fw, 0xffffffff806857b0, 0) error 1
ipw_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw.LICENSE.
ipw_monitor: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
module_register_init: MOD_LOAD (ipw_monitor_fw, 0xffffffff80685860, 0) error 1
iwi_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi.LICENSE.
iwi_bss: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
module_register_init: MOD_LOAD (iwi_bss_fw, 0xffffffff806ac730, 0) error 1
iwi_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi.LICENSE.
iwi_ibss: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
module_register_init: MOD_LOAD (iwi_ibss_fw, 0xffffffff806ac7e0, 0) error 1
iwi_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi.LICENSE.
iwi_monitor: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
module_register_init: MOD_LOAD (iwi_monitor_fw, 0xffffffff806ac890, 0) error 1
wlan: mac acl policy registered
kbd0 at kbdmux0
netmap: loaded module
module_register_init: MOD_LOAD (vesa, 0xffffffff8120faa0, 0) error 19
random: registering fast source Intel Secure Key RNG
random: fast provider: "Intel Secure Key RNG"
nexus0
vtvga0: <VT VGA driver> on motherboard
cryptosoft0: <software crypto> on motherboard
padlock0: No ACE support.
acpi0: <CORE COREBOOT> on motherboard
acpi0: Power Button (fixed)
hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
Timecounter "HPET" frequency 24000000 Hz quality 950
Event timer "HPET" frequency 24000000 Hz quality 550
Event timer "HPET1" frequency 24000000 Hz quality 440
Event timer "HPET2" frequency 24000000 Hz quality 440
Event timer "HPET3" frequency 24000000 Hz quality 440
Event timer "HPET4" frequency 24000000 Hz quality 440
cpu0: <ACPI CPU> on acpi0
cpu1: <ACPI CPU> on acpi0
cpu2: <ACPI CPU> on acpi0
cpu3: <ACPI CPU> on acpi0
atrtc0: <AT realtime clock> port 0x70-0x77 on acpi0
atrtc0: Warning: Couldn't map I/O.
atrtc0: registered as a time-of-day clock, resolution 1.000000s
Event timer "RTC" frequency 32768 Hz quality 0
attimer0: <AT timer> port 0x40-0x43,0x50-0x53 irq 0 on acpi0
Timecounter "i8254" frequency 1193182 Hz quality 0
Event timer "i8254" frequency 1193182 Hz quality 100
Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1808-0x180b on acpi0
acpi_button0: <Power Button> on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pcib1: <ACPI PCI-PCI bridge> irq 18 at device 6.0 on pci0
pci1: <ACPI PCI bus> on pcib1
pci1: <processor> at device 0.0 (no driver attached)
pcib2: <ACPI PCI-PCI bridge> mem 0xdfe00000-0xdfe1ffff irq 20 at device 14.0 on pci0
pci2: <ACPI PCI bus> on pcib2
pcib3: <ACPI PCI-PCI bridge> mem 0xdfe20000-0xdfe3ffff irq 22 at device 16.0 on pci0
pci3: <ACPI PCI bus> on pcib3
pcib4: <ACPI PCI-PCI bridge> mem 0xdfe40000-0xdfe5ffff irq 23 at device 17.0 on pci0
pci4: <ACPI PCI bus> on pcib4
ahci0: <Intel Denverton AHCI SATA controller> port 0x1c20-0x1c27,0x1c28-0x1c2b,0x1c00-0x1c1f mem 0xdfe74000-0xdfe75fff,0xdfe7c000-0xdfe7c0ff,0xdfe7a000-0xdfe7a7ff irq 21 at device 20.0 on pci0
ahci0: AHCI v1.31 with 5 6Gbps ports, Port Multiplier supported
ahcich1: <AHCI channel> at channel 1 on ahci0
ahcich3: <AHCI channel> at channel 3 on ahci0
ahcich4: <AHCI channel> at channel 4 on ahci0
ahcich5: <AHCI channel> at channel 5 on ahci0
ahcich6: <AHCI channel> at channel 6 on ahci0
xhci0: <Intel Denverton USB 3.0 controller> mem 0xdfe60000-0xdfe6ffff irq 19 at device 21.0 on pci0
xhci0: 32 bytes context size, 64-bit DMA
usbus0 on xhci0
usbus0: 5.0Gbps Super Speed USB v3.0
pcib5: <ACPI PCI-PCI bridge> irq 16 at device 22.0 on pci0
pci5: <ACPI PCI bus> on pcib5
pcib0: no PRT entry for 0.22.INTB
ix0: <Intel(R) PRO/10GbE PCI-Express Network Driver, Version - 3.2.12-k> mem 0xde800000-0xde9fffff,0xdec00000-0xdec03fff irq 16 at device 0.0 on pci5
ix0: Using MSI-X interrupts with 5 vectors
ix0: Ethernet address: 00:08:a2:0e:da:4d
ix0: netmap queues/slots: TX 4/2048, RX 4/2048
ix1: <Intel(R) PRO/10GbE PCI-Express Network Driver, Version - 3.2.12-k> mem 0xdea00000-0xdebfffff,0xdec04000-0xdec07fff irq 10 at device 0.1 on pci5
ix1: Using MSI-X interrupts with 5 vectors
ix1: Ethernet address: 00:08:a2:0e:da:4e
ix1: netmap queues/slots: TX 4/2048, RX 4/2048
pcib6: <ACPI PCI-PCI bridge> irq 17 at device 23.0 on pci0
pci6: <ACPI PCI bus> on pcib6
pcib0: no PRT entry for 0.23.INTB
ix2: <Intel(R) PRO/10GbE PCI-Express Network Driver, Version - 3.2.12-k> mem 0xdee00000-0xdeffffff,0xdf200000-0xdf203fff irq 17 at device 0.0 on pci6
ix2: Using MSI-X interrupts with 5 vectors
ix2: Ethernet address: 00:08:a2:0e:da:4f
mdio0: <MDIO> on ix2
e6000sw0: <Marvell 88E6190> on mdio0
e6000sw0: single-chip addressing mode
miibus0: <MII bus> on e6000sw0
e1000phy0: <Marvell 88E1000 Gigabit PHY> PHY 1 on miibus0
e1000phy0:  none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto
miibus1: <MII bus> on e6000sw0
e1000phy1: <Marvell 88E1000 Gigabit PHY> PHY 2 on miibus1
e1000phy1:  none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto
miibus2: <MII bus> on e6000sw0
e1000phy2: <Marvell 88E1000 Gigabit PHY> PHY 3 on miibus2
e1000phy2:  none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto
miibus3: <MII bus> on e6000sw0
e1000phy3: <Marvell 88E1000 Gigabit PHY> PHY 4 on miibus3
e1000phy3:  none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto
miibus4: <MII bus> on e6000sw0
e1000phy4: <Marvell 88E1000 Gigabit PHY> PHY 5 on miibus4
e1000phy4:  none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto
miibus5: <MII bus> on e6000sw0
e1000phy5: <Marvell 88E1000 Gigabit PHY> PHY 6 on miibus5
e1000phy5:  none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto
miibus6: <MII bus> on e6000sw0
e1000phy6: <Marvell 88E1000 Gigabit PHY> PHY 7 on miibus6
e1000phy6:  none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto
miibus7: <MII bus> on e6000sw0
e1000phy7: <Marvell 88E1000 Gigabit PHY> PHY 8 on miibus7
e1000phy7:  none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto
e6000sw0: switch is ready.
etherswitch0: <Switch controller> on e6000sw0
ix2: netmap queues/slots: TX 4/2048, RX 4/2048
e6000sw0port1: link state changed to DOWN
e6000sw0port2: link state changed to UP
e6000sw0port3: link state changed to DOWN
ix3: <Intel(R) PRO/10GbE PCI-Express Network Driver, Version - 3.2.12-k>
e6000sw0port4: link state changed to DOWN
 mem 0xdf000000-0xdf1fffff,0xdf204000-0xdf207fff irq 10 at device 0.1 on pci6
ix3: 
e6000sw0port5: link state changed to DOWN
e6000sw0port6: link state changed to DOWN
Using MSI-X interrupts with 5 vectors
e6000sw0port7: link state changed to UP
e6000sw0port8: link state changed to DOWN
ix3: Ethernet address: 00:08:a2:0e:da:50
ix3: netmap queues/slots: TX 4/2048, RX 4/2048
pci0: <simple comms> at device 24.0 (no driver attached)
sdhci_pci0: <Intel Denverton eMMC 5.0 Controller> mem 0xdfe77000-0xdfe77fff,0xdfe78000-0xdfe78fff irq 16 at device 28.0 on pci0
sdhci_pci0: 1 slot(s) allocated
mmc0: <MMC/SD bus> on sdhci_pci0
isab0: <PCI-ISA bridge> at device 31.0 on pci0
isa0: <ISA bus> on isab0
pci0: <memory> at device 31.2 (no driver attached)
pci0: <serial bus> at device 31.5 (no driver attached)
uart0: <Non-standard ns8250 class UART with FIFOs> port 0x3f8-0x3ff irq 19 flags 0x10 on acpi0
uart0: console (115200,n,8,1)
uart1: <Non-standard ns8250 class UART with FIFOs> port 0x2f8-0x2ff irq 18 on acpi0
orm0: <ISA Option ROMs> at iomem 0xc0000-0xc0fff,0xee800-0xeffff on isa0
ppc0: cannot reserve I/O port range
est0: <Enhanced SpeedStep Frequency Control> on cpu0
est1: <Enhanced SpeedStep Frequency Control> on cpu1
est2: <Enhanced SpeedStep Frequency Control> on cpu2
est3: <Enhanced SpeedStep Frequency Control> on cpu3
Timecounters tick every 1.000 msec
ugen0.1: <0x8086 XHCI root HUB> at usbus0
uhub0: <0x8086 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0
mmcsd0: 31GB <MMCHC M52532 0.1 SN 198C3778 MFG 08/2018 by 112 0x0000> at mmc0 50.0MHz/8bit/65535-block
mmcsd0boot0: 4MB partion 1 at mmcsd0
mmcsd0boot1: 4MB partion 2 at mmcsd0
mmcsd0rpmb: 4MB partion 3 at mmcsd0
ada0 at ahcich1 bus 0 scbus0 target 0 lun 0
ada0: <G6312 R0522A0> ACS-2 ATA SATA 3.x device
ada0: Serial Number 1832005701182
ada0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 512bytes)
ada0: Command Queueing enabled
ada0: 228936MB (468862128 512 byte sectors)
Trying to mount root from ufs:/dev/ufsid/5b0df81c099aa6c1 [rw]...
random: unblocking device.
uhub0: 8 ports with 8 removable, self powered
e6000sw0port3: link state changed to UP
e6000sw0port4: link state changed to UP
e6000sw0port5: link state changed to UP
e6000sw0port6: link state changed to UP
e6000sw0port8: link state changed to UP
CPU: Intel(R) Atom(TM) CPU C3558 @ 2.20GHz (2200.07-MHz K8-class CPU)
  Origin="GenuineIntel"  Id=0x506f1  Family=0x6  Model=0x5f  Stepping=1
  Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
  Features2=0x4ff8ebbf<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,SDBG,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,RDRAND>
  AMD Features=0x2c100800<SYSCALL,NX,Page1GB,RDTSCP,LM>
  AMD Features2=0x101<LAHF,Prefetch>
  Structured Extended Features=0x2294e283<FSGSBASE,TSCADJ,SMEP,ERMS,NFPUSG,MPX,PQE,RDSEED,SMAP,CLFLUSHOPT,PROCTRACE,SHA>
  Structured Extended Features3=0xac000400<IBPB,STIBP,ARCH_CAP,SSBD>
  XSAVE Features=0xf<XSAVEOPT,XSAVEC,XINUSE,XSAVES>
  IA32_ARCH_CAPS=0x69<RDCL_NO>
  VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID,VID,PostIntr
  TSC: P-state invariant, performance statistics
padlock0: No ACE support.
aesni0: <AES-CBC,AES-XTS,AES-GCM,AES-ICM> on motherboard
coretemp0: <CPU On-Die Thermal Sensors> on cpu0
coretemp1: <CPU On-Die Thermal Sensors> on cpu1
coretemp2: <CPU On-Die Thermal Sensors> on cpu2
coretemp3: <CPU On-Die Thermal Sensors> on cpu3
e6000sw0port2: link state changed to DOWN
e6000sw0port3: link state changed to DOWN
e6000sw0port4: link state changed to DOWN
e6000sw0port5: link state changed to DOWN
e6000sw0port2: link state changed to UP
e6000sw0port6: link state changed to DOWN
e6000sw0port7: link state changed to DOWN
e6000sw0port3: link state changed to UP
e6000sw0port8: link state changed to DOWN
e6000sw0port4: link state changed to UP
lagg0: IPv6 addresses on ix2 have been removed before adding it as a member to prevent IPv6 address scope violation.
lagg0: link state changed to DOWN
e6000sw0port5: link state changed to UP
ix2: link state changed to UP
lagg0: link state changed to UP
lagg0: IPv6 addresses on ix3 have been removed before adding it as a member to prevent IPv6 address scope violation.
ix2: link state changed to DOWN
lagg0: link state changed to DOWN
vlan0: changing name to 'lagg0.4090'
vlan1: changing name to 'lagg0.4091'
ix2: link state changed to UP
lagg0: link state changed to UP
lagg0.4090: link state changed to UP
lagg0.4091: link state changed to UP
ix3: link state changed to UP
vlan2: changing name to 'ix1.10'
vlan3: changing name to 'ix1.12'
vlan4: changing name to 'ix1.15'
vlan5: changing name to 'ix1.19'
e6000sw0port6: link state changed to UP
e6000sw0port7: link state changed to UP
ix1: link state changed to UP
ix1.19: link state changed to UP
ix1.10: link state changed to UP
ix1.12: link state changed to UP
ix1.15: link state changed to UP
pflog0: promiscuous mode enabled
ix0: link state changed to UP
e6000sw0port8: link state changed to UP
e6000sw0port2: link state changed to DOWN
e6000sw0port2: link state changed to UP
e6000sw0port2: link state changed to DOWN
e6000sw0port2: link state changed to UP
e6000sw0port7: link state changed to DOWN
e6000sw0port7: link state changed to UP
e6000sw0port7: link state changed to DOWN
e6000sw0port7: link state changed to UP
e6000sw0port7: link state changed to DOWN
e6000sw0port7: link state changed to UP
e6000sw0port7: link state changed to DOWN
e6000sw0port7: link state changed to UP
e6000sw0port7: link state changed to DOWN
e6000sw0port7: link state changed to UP
e6000sw0port2: link state changed to DOWN
e6000sw0port2: link state changed to UP
e6000sw0port2: link state changed to DOWN
                      1 Reply Last reply Reply Quote 0
                      • chrismacmahonC
                        chrismacmahon
                        last edited by

                        You can open a ticket to get an image file and reflash the unit, https://go.netgate.com

                        If there is a hardware fault, and it's with in the warranty period we will stand behind our product.

                        If there is a configuration issue we might need to have a support agreement in place to resolve this problem with you.

                        Need help fast? Our support is available 24/7 https://www.netgate.com/support/

                        Do Not PM For Help!

                        1 Reply Last reply Reply Quote 0
                        • V
                          victorhooi
                          last edited by

                          Got it - I've filed https://go.netgate.com/support/tickets/28699 to get access to the firmware images. Thanks!

                          I'm hoping it's not hardware =(, we bought quite a few of these in the one go. I've staked this project on pfSense (and just yesterday got asked, "You're using whitebox routers?"), so hoping it's just bad luck, or there was some config setting that the upgrade process didn't like.

                          I'll try re-flashing it to 2.4.4-p3, and then rebuilding our config from scratch again. Any other advice, or things I should watch out for?

                          Is there any word at all on TNSR for XG-7100's? Are we weeks or months away? Or longer? Happy to pay for that, if it improves manageability. (We don't need the 10Gb speeds).

                          1 Reply Last reply Reply Quote 0
                          • V
                            victorhooi
                            last edited by

                            I'm attempting to reinstall pfSense 2.4.4-p3 on the Netgate XG-7100 now.

                            However, the documentation doesn't seem to actually match the current installer.

                            For example, the documentation refers to picking "Quick/Easy Install" which should automatically select the most common options. However, there's no such option, only the full "Install":

                            alt text

                            Furthermore - when you're prompted to select a disk to install to - it's incredibly confusing:

                            alt text

                            In my case, I purchased several XG-7100's, and I got the SSD upgrade on all of them.

                            SanDisk Extreme is the USB disk containing the pfSense installer.

                            However, what is "G6312"?

                            And there seem to be three devices representing my SSD, right? I assume the second and third are partitions (or slices) on the disk. But which one should I be picking?

                            Also - did the pfSense installer change, to get rid of the "Quick/Easy Install" option?

                            1 Reply Last reply Reply Quote 0
                            • V
                              victorhooi
                              last edited by

                              Also - I just picked the "mmcsd0" option - went through the installer...the system rebooted.

                              And I seem to be back in my old install? confused

                              So what did it actually install to?

                              G 1 Reply Last reply Reply Quote 0
                              • RicoR
                                Rico LAYER 8 Rebel Alliance
                                last edited by

                                G6312 is your SSD.

                                -Rico

                                1 Reply Last reply Reply Quote 0
                                • G
                                  gfeiner @victorhooi
                                  last edited by

                                  @victorhooi said in XG-7100 - Upgrading from 2.4.4-p2 to 2.4.4-p3 broke DHCP?:

                                  Also - I just picked the "mmcsd0" option - went through the installer...the system rebooted.

                                  And I seem to be back in my old install? confused

                                  So what did it actually install to?

                                  mmcsd0 is the embedded 32GB eMMC storage (soldered to the system board). And yes, the pfSense re-install instructions are out of date and don't match the current options.

                                  1 Reply Last reply Reply Quote 0
                                  • stephenw10S
                                    stephenw10 Netgate Administrator
                                    last edited by

                                    For most installs you should just be able to hit return to agree to the default selections.

                                    If you have two available devices, SSD or eMMC here, you will have to select that. If you choose to use ZFS then you need to go through the installer steps more carefully there.

                                    Coreboot will, by default, boot the SSD in preference to the eMMC. So if you installed to eMMC and rebooted it will just boo the old install on the SSD. You would have to choose to boot eMMC at the console. The boot order can be changed there though.

                                    Steve

                                    1 Reply Last reply Reply Quote 0
                                    • First post
                                      Last post
                                    Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.