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

    23.01 install results in no internet

    General pfSense Questions
    8
    69
    17.0k
    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.
    • P
      puneet1984 @Gertjan
      last edited by

      @gertjan

      the pppoe errors are coming after 12hrs of upgradation and multiple reboots...
      i upgraded to stable release of 23.01

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

        This is something closing the connection:

        Feb 16 10:34:46	ppp	25847	[wan] IPCP: Close event
Feb 16 10:34:46	ppp	25847	[wan] IFACE: Close event
Feb 16 10:34:46	ppp	25847	caught fatal signal TERM
Feb 16 10:33:27	ppp	25847	[wan] IFACE: Add description "WAN"

        So check the main system log at the time.

        J 1 Reply Last reply Reply Quote 0
        • J
          jeff3820 @stephenw10
          last edited by jeff3820

          @stephenw10 Reverted back to 22.05 and all was perfect. Took out my 3 packages, OpenVPN Client Export, NUT, and Patches. Rebooted. 22.05 came up fine. Deleted Boot environment for previous 23.01 and the backup that 23.01 did of 22.05. Did the upgrade again. Same result, no internet connection. I can't see anything in the system log...anything stand out to you??

          One other thing, under 23.01 the physical interfaces don't seem to be working right. Unplug LAN cable and connection light goes off...plug it in and no connection light unless I reboot.

          There look to be a few errors:
          Feb 16 11:43:44 kernel ns8250: UART FCR is broken
          Feb 16 11:43:44 kernel uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
          Feb 16 11:43:44 kernel ns8250: UART FCR is broken
          Feb 16 11:43:44 kernel ns8250: UART FCR is broken

          Feb 16 11:44:34 sshguard 76523 Now monitoring attacks.
          Feb 16 11:44:34 login 74709 login on ttyv0 as root
          Feb 16 11:44:32 root 39406 Bootup complete
          Feb 16 11:44:32 php-fpm 358 /rc.start_packages: Restarting/Starting all packages.
          Feb 16 11:44:32 kernel done.
          Feb 16 11:44:32 syslogd kernel boot file is /boot/kernel/kernel
          Feb 16 11:44:32 syslogd exiting on signal 15
          Feb 16 11:44:29 kernel done.
          Feb 16 11:44:29 root 85337 /etc/rc.d/hostid: WARNING: hostid: unable to figure out a UUID from DMI data, generating a new one
          Feb 16 11:44:29 php-cgi 411 rc.bootup: Creating rrd update script
          Feb 16 11:44:29 php-cgi 411 rc.bootup: The command '/usr/bin/nice -n20 /usr/local/bin/rrdtool update /var/db/rrd/system-sensors.rrd N:U:U:U:U:U:U' returned exit code '1', the output was 'ERROR: /var/db/rrd/system-sensors.rrd: found extra data on update argument: U:U:U:U'
          Feb 16 11:44:25 kernel .done.
          Feb 16 11:44:25 php-cgi 411 rc.bootup: The command '/usr/local/sbin/strongswanrc stop' returned exit code '1', the output was 'strongswan not running? (check /var/run/daemon-charon.pid).'
          Feb 16 11:44:25 kernel ....
          Feb 16 11:44:25 kernel done.
          Feb 16 11:44:25 check_reload_status 388 Updating all dyndns
          Feb 16 11:44:25 kernel done.
          Feb 16 11:44:24 php-cgi 411 rc.bootup: NTPD is starting up.
          Feb 16 11:44:24 kernel done.
          Feb 16 11:44:24 kernel done.
          Feb 16 11:43:54 kernel done.
          Feb 16 11:43:53 kernel done.
          Feb 16 11:43:53 php-cgi 411 rc.bootup: sync unbound done.
          Feb 16 11:43:52 php-fpm 358 /rc.newwanip: rc.newwanip: on (IP address: 192.168.100.1) (interface: []) (real interface: ovpns1).
          Feb 16 11:43:52 php-fpm 358 /rc.newwanip: rc.newwanip: Info: starting on ovpns1.
          Feb 16 11:43:52 kernel done.
          Feb 16 11:43:52 php-cgi 411 rc.bootup: Default gateway setting Interface WAN_DHCP Gateway as default.
          Feb 16 11:43:52 php-fpm 359 /rc.newwanip: rc.newwanip: on (IP address: 192.168.30.102) (interface: WAN[wan]) (real interface: em0).
          Feb 16 11:43:52 php-fpm 359 /rc.newwanip: rc.newwanip: Info: starting on em0.
          Feb 16 11:43:52 kernel .done.
          Feb 16 11:43:52 kernel ....
          Feb 16 11:43:51 kernel pflog0: promiscuous mode enabled
          Feb 16 11:43:51 check_reload_status 388 rc.newwanip starting ovpns1
          Feb 16 11:43:51 kernel ovpns1: link state changed to UP
          Feb 16 11:43:51 kernel tun1: changing name to 'ovpns1'
          Feb 16 11:43:51 kernel [fib_algo] inet.0 (bsearch4#28) rebuild_fd_flm: switching algo to radix4_lockless
          Feb 16 11:43:51 php-cgi 411 rc.bootup: Resyncing OpenVPN instances.
          Feb 16 11:43:51 check_reload_status 388 rc.newwanip starting em0
          Feb 16 11:43:48 check_reload_status 388 Linkup starting em1.30
          Feb 16 11:43:48 check_reload_status 388 Linkup starting em1.40
          Feb 16 11:43:48 check_reload_status 388 Linkup starting em1.50
          Feb 16 11:43:48 check_reload_status 388 Linkup starting em1
          Feb 16 11:43:48 kernel em1.30: link state changed to UP
          Feb 16 11:43:48 kernel em1.40: link state changed to UP
          Feb 16 11:43:48 kernel em1.50: link state changed to UP
          Feb 16 11:43:48 kernel em1: link state changed to UP
          Feb 16 11:43:48 kernel em0: link state changed to UP
          Feb 16 11:43:48 check_reload_status 388 Linkup starting em0
          Feb 16 11:43:45 kernel vlan2: changing name to 'em1.50'
          Feb 16 11:43:45 kernel vlan1: changing name to 'em1.40'
          Feb 16 11:43:45 kernel vlan0: changing name to 'em1.30'
          Feb 16 11:43:44 kernel lo0: link state changed to UP
          Feb 16 11:43:44 kernel coretemp0: <CPU On-Die Thermal Sensors> on cpu0
          Feb 16 11:43:44 kernel aesni0: <AES-CBC,AES-CCM,AES-GCM,AES-ICM,AES-XTS>
          Feb 16 11:43:44 kernel smbus0: <System Management Bus> on ichsmb0
          Feb 16 11:43:44 kernel ichsmb0: <Intel Sunrise Point-LP SMBus controller> port 0xf040-0xf05f mem 0xdf616000-0xdf6160ff irq 16 at device 31.4 on pci0
          Feb 16 11:43:44 kernel TSC: P-state invariant, performance statistics
          Feb 16 11:43:44 kernel VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID
          Feb 16 11:43:44 kernel IA32_ARCH_CAPS=0xc04<RSBA>
          Feb 16 11:43:44 kernel XSAVE Features=0xf<XSAVEOPT,XSAVEC,XINUSE,XSAVES>
          Feb 16 11:43:44 kernel Structured Extended Features3=0xbc002e00<MCUOPT,MD_CLEAR,TSXFA,IBPB,STIBP,L1DFL,ARCH_CAP,SSBD>
          Feb 16 11:43:44 kernel Structured Extended Features=0x29c67af<FSGSBASE,TSCADJ,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,NFPUSG,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PROCTRACE>
          Feb 16 11:43:44 kernel AMD Features2=0x121<LAHF,ABM,Prefetch>
          Feb 16 11:43:44 kernel AMD Features=0x2c100800<SYSCALL,NX,Page1GB,RDTSCP,LM>
          Feb 16 11:43:44 kernel Features2=0x7ffafbbf<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,SDBG,FMA,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND>
          Feb 16 11:43:44 kernel 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>
          Feb 16 11:43:44 kernel Origin="GenuineIntel" Id=0x806e9 Family=0x6 Model=0x8e Stepping=9
          Feb 16 11:43:44 kernel CPU: Intel(R) Core(TM) i3-7100U CPU @ 2.40GHz (2400.00-MHz K8-class CPU)
          Feb 16 11:43:44 kernel ada0: 476940MB (976773168 512 byte sectors)
          Feb 16 11:43:44 kernel ada0: Command Queueing enabled
          Feb 16 11:43:44 kernel ada0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 512bytes)
          Feb 16 11:43:44 kernel ada0: Serial Number S41NNB0M506476E
          Feb 16 11:43:44 kernel ada0: <Samsung SSD 860 EVO mSATA 500GB RVT43B6Q> ACS-4 ATA SATA 3.x device
          Feb 16 11:43:44 kernel ada0 at ahcich0 bus 0 scbus0 target 0 lun 0
          Feb 16 11:43:44 kernel Root mount waiting for: CAM
          Feb 16 11:43:44 kernel Root mount waiting for: CAM
          Feb 16 11:43:44 kernel Root mount waiting for: CAM
          Feb 16 11:43:44 kernel Root mount waiting for: CAM
          Feb 16 11:43:44 kernel Root mount waiting for: CAM
          Feb 16 11:43:44 kernel Root mount waiting for: CAM
          Feb 16 11:43:44 kernel Root mount waiting for: CAM
          Feb 16 11:43:44 kernel Root mount waiting for: CAM
          Feb 16 11:43:44 kernel uhid0: <USB Keyboard> on usbus0
          Feb 16 11:43:44 kernel uhid0 on uhub0
          Feb 16 11:43:44 kernel kbd2 at ukbd0
          Feb 16 11:43:44 kernel ukbd0: <USB Keyboard> on usbus0
          Feb 16 11:43:44 kernel ukbd0 on uhub0
          Feb 16 11:43:44 kernel ugen0.2: <Logitech USB Keyboard> at usbus0
          Feb 16 11:43:44 kernel Root mount waiting for: usbus0 CAM
          Feb 16 11:43:44 kernel uhub0: 18 ports with 18 removable, self powered
          Feb 16 11:43:44 kernel uhub0: <Intel XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0
          Feb 16 11:43:44 kernel uhub0 on usbus0
          Feb 16 11:43:44 kernel ugen0.1: <Intel XHCI root HUB> at usbus0
          Feb 16 11:43:44 kernel Trying to mount root from zfs:pfSense/ROOT/working2205 []...
          Feb 16 11:43:44 kernel ZFS storage pool version: features support (5000)
          Feb 16 11:43:44 kernel ZFS filesystem version: 5
          Feb 16 11:43:44 kernel Timecounters tick every 1.000 msec
          Feb 16 11:43:44 kernel Timecounter "TSC-low" frequency 1199997904 Hz quality 1000
          Feb 16 11:43:44 kernel hwpstate_intel3: <Intel Speed Shift> on cpu3
          Feb 16 11:43:44 kernel hwpstate_intel2: <Intel Speed Shift> on cpu2
          Feb 16 11:43:44 kernel hwpstate_intel1: <Intel Speed Shift> on cpu1
          Feb 16 11:43:44 kernel hwpstate_intel0: <Intel Speed Shift> on cpu0
          Feb 16 11:43:44 kernel orm0: <ISA Option ROM> at iomem 0xc0000-0xcffff pnpid ORM0000 on isa0
          Feb 16 11:43:44 kernel ns8250: UART FCR is broken
          Feb 16 11:43:44 kernel uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
          Feb 16 11:43:44 kernel ns8250: UART FCR is broken
          Feb 16 11:43:44 kernel ns8250: UART FCR is broken
          Feb 16 11:43:44 kernel atkbd0: [GIANT-LOCKED]
          Feb 16 11:43:44 kernel kbd0 at atkbd0
          Feb 16 11:43:44 kernel atkbd0: <AT Keyboard> irq 1 on atkbdc0
          Feb 16 11:43:44 kernel atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
          Feb 16 11:43:44 kernel acpi_tz1: <Thermal Zone> on acpi0
          Feb 16 11:43:44 kernel acpi_tz0: <Thermal Zone> on acpi0
          Feb 16 11:43:44 kernel acpi_button1: <Power Button> on acpi0
          Feb 16 11:43:44 kernel acpi_button0: <Sleep Button> on acpi0
          Feb 16 11:43:44 kernel pci0: <memory> at device 31.2 (no driver attached)
          Feb 16 11:43:44 kernel isa0: <ISA bus> on isab0
          Feb 16 11:43:44 kernel isab0: <PCI-ISA bridge> at device 31.0 on pci0
          Feb 16 11:43:44 kernel em5: netmap queues/slots: TX 1/1024, RX 1/1024
          Feb 16 11:43:44 kernel em5: Ethernet address: 00:e0:67:13:63:47
          Feb 16 11:43:44 kernel em5: Using an MSI interrupt
          Feb 16 11:43:44 kernel em5: Using 1024 TX descriptors and 1024 RX descriptors
          Feb 16 11:43:44 kernel em5: EEPROM V1.10-0
          Feb 16 11:43:44 kernel em5: <Intel(R) 82583V> port 0x9000-0x901f mem 0xdf000000-0xdf01ffff,0xdf020000-0xdf023fff irq 17 at device 0.0 on pci6
          Feb 16 11:43:44 kernel pci6: <ACPI PCI bus> on pcib6
          Feb 16 11:43:44 kernel pcib6: <ACPI PCI-PCI bridge> irq 17 at device 28.5 on pci0
          Feb 16 11:43:44 kernel em4: netmap queues/slots: TX 1/1024, RX 1/1024
          Feb 16 11:43:44 kernel em4: Ethernet address: 00:e0:67:13:63:46
          Feb 16 11:43:44 kernel em4: Using an MSI interrupt
          Feb 16 11:43:44 kernel em4: Using 1024 TX descriptors and 1024 RX descriptors
          Feb 16 11:43:44 kernel em4: EEPROM V1.10-0
          Feb 16 11:43:44 kernel em4: <Intel(R) 82583V> port 0xa000-0xa01f mem 0xdf100000-0xdf11ffff,0xdf120000-0xdf123fff irq 16 at device 0.0 on pci5
          Feb 16 11:43:44 kernel pci5: <ACPI PCI bus> on pcib5
          Feb 16 11:43:44 kernel pcib5: <ACPI PCI-PCI bridge> irq 16 at device 28.4 on pci0
          Feb 16 11:43:44 kernel em3: netmap queues/slots: TX 1/1024, RX 1/1024
          Feb 16 11:43:44 kernel em3: Ethernet address: 00:e0:67:13:63:45
          Feb 16 11:43:44 kernel em3: Using an MSI interrupt
          Feb 16 11:43:44 kernel em3: Using 1024 TX descriptors and 1024 RX descriptors
          Feb 16 11:43:44 kernel em3: EEPROM V1.10-0
          Feb 16 11:43:44 kernel em3: <Intel(R) 82583V> port 0xb000-0xb01f mem 0xdf200000-0xdf21ffff,0xdf220000-0xdf223fff irq 19 at device 0.0 on pci4
          Feb 16 11:43:44 kernel pci4: <ACPI PCI bus> on pcib4
          Feb 16 11:43:44 kernel pcib4: <ACPI PCI-PCI bridge> irq 19 at device 28.3 on pci0
          Feb 16 11:43:44 kernel em2: netmap queues/slots: TX 1/1024, RX 1/1024
          Feb 16 11:43:44 kernel em2: Ethernet address: 00:e0:67:13:63:44
          Feb 16 11:43:44 kernel em2: Using an MSI interrupt
          Feb 16 11:43:44 kernel em2: Using 1024 TX descriptors and 1024 RX descriptors
          Feb 16 11:43:44 kernel em2: EEPROM V1.10-0
          Feb 16 11:43:44 kernel em2: <Intel(R) 82583V> port 0xc000-0xc01f mem 0xdf300000-0xdf31ffff,0xdf320000-0xdf323fff irq 18 at device 0.0 on pci3
          Feb 16 11:43:44 kernel pci3: <ACPI PCI bus> on pcib3
          Feb 16 11:43:44 kernel pcib3: <ACPI PCI-PCI bridge> irq 18 at device 28.2 on pci0
          Feb 16 11:43:44 kernel em1: netmap queues/slots: TX 1/1024, RX 1/1024
          Feb 16 11:43:44 kernel em1: Ethernet address: 00:e0:67:13:63:43
          Feb 16 11:43:44 kernel em1: Using an MSI interrupt
          Feb 16 11:43:44 kernel em1: Using 1024 TX descriptors and 1024 RX descriptors
          Feb 16 11:43:44 kernel em1: EEPROM V1.10-0
          Feb 16 11:43:44 kernel em1: <Intel(R) 82583V> port 0xd000-0xd01f mem 0xdf400000-0xdf41ffff,0xdf420000-0xdf423fff irq 17 at device 0.0 on pci2
          Feb 16 11:43:44 kernel pci2: <ACPI PCI bus> on pcib2
          Feb 16 11:43:44 kernel pcib2: <ACPI PCI-PCI bridge> irq 17 at device 28.1 on pci0
          Feb 16 11:43:44 kernel em0: netmap queues/slots: TX 1/1024, RX 1/1024
          Feb 16 11:43:44 kernel em0: Ethernet address: 00:e0:67:13:63:42
          Feb 16 11:43:44 kernel em0: Using an MSI interrupt
          Feb 16 11:43:44 kernel em0: Using 1024 TX descriptors and 1024 RX descriptors
          Feb 16 11:43:44 kernel em0: EEPROM V1.10-0
          Feb 16 11:43:44 kernel em0: <Intel(R) 82583V> port 0xe000-0xe01f mem 0xdf500000-0xdf51ffff,0xdf520000-0xdf523fff irq 16 at device 0.0 on pci1
          Feb 16 11:43:44 kernel pci1: <ACPI PCI bus> on pcib1
          Feb 16 11:43:44 kernel pcib1: <ACPI PCI-PCI bridge> irq 16 at device 28.0 on pci0
          Feb 16 11:43:44 kernel ahcich2: <AHCI channel> at channel 2 on ahci0
          Feb 16 11:43:44 kernel ahcich1: <AHCI channel> at channel 1 on ahci0
          Feb 16 11:43:44 kernel ahcich0: <AHCI channel> at channel 0 on ahci0
          Feb 16 11:43:44 kernel ahci0: AHCI v1.31 with 3 6Gbps ports, Port Multiplier not supported
          Feb 16 11:43:44 kernel ahci0: <Intel Sunrise Point-LP AHCI SATA controller> port 0xf090-0xf097,0xf080-0xf083,0xf060-0xf07f mem 0xdf614000-0xdf615fff,0xdf618000-0xdf6180ff,0xdf617000-0xdf6177ff irq 16 at device 23.0 on pci0
          Feb 16 11:43:44 kernel pci0: <simple comms> at device 22.0 (no driver attached)
          Feb 16 11:43:44 kernel usbus0: 5.0Gbps Super Speed USB v3.0
          Feb 16 11:43:44 kernel usbus0 on xhci0
          Feb 16 11:43:44 kernel xhci_interrupt: host controller halted
          Feb 16 11:43:44 kernel usbus0: waiting for BIOS to give up control
          Feb 16 11:43:44 kernel xhci0: 32 bytes context size, 64-bit DMA
          Feb 16 11:43:44 kernel xhci0: <Intel Sunrise Point-LP USB 3.0 controller> mem 0xdf600000-0xdf60ffff irq 16 at device 20.0 on pci0
          Feb 16 11:43:44 kernel vgapci0: Boot video device
          Feb 16 11:43:44 kernel vgapci0: <VGA-compatible display> port 0xf000-0xf03f mem 0xde000000-0xdeffffff,0xc0000000-0xcfffffff irq 16 at device 2.0 on pci0
          Feb 16 11:43:44 kernel pci0: <ACPI PCI bus> on pcib0
          Feb 16 11:43:44 kernel pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
          Feb 16 11:43:44 kernel acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1808-0x180b on acpi0
          Feb 16 11:43:44 kernel Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
          Feb 16 11:43:44 kernel Event timer "i8254" frequency 1193182 Hz quality 100
          Feb 16 11:43:44 kernel Timecounter "i8254" frequency 1193182 Hz quality 0
          Feb 16 11:43:44 kernel attimer0: <AT timer> port 0x40-0x43,0x50-0x53 irq 0 on acpi0
          Feb 16 11:43:44 kernel Event timer "RTC" frequency 32768 Hz quality 0
          Feb 16 11:43:44 kernel atrtc0: registered as a time-of-day clock, resolution 1.000000s
          Feb 16 11:43:44 kernel atrtc0: Warning: Couldn't map I/O.
          Feb 16 11:43:44 kernel atrtc0: <AT realtime clock> port 0x70-0x77 irq 8 on acpi0
          Feb 16 11:43:44 kernel Event timer "HPET4" frequency 24000000 Hz quality 440
          Feb 16 11:43:44 kernel Event timer "HPET3" frequency 24000000 Hz quality 440
          Feb 16 11:43:44 kernel Event timer "HPET2" frequency 24000000 Hz quality 440
          Feb 16 11:43:44 kernel Event timer "HPET1" frequency 24000000 Hz quality 440
          Feb 16 11:43:44 kernel Event timer "HPET" frequency 24000000 Hz quality 550
          Feb 16 11:43:44 kernel Timecounter "HPET" frequency 24000000 Hz quality 950
          Feb 16 11:43:44 kernel hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
          Feb 16 11:43:44 kernel cpu0: <ACPI CPU> on acpi0
          Feb 16 11:43:44 kernel acpi0: Power Button (fixed)
          Feb 16 11:43:44 kernel acpi0: <ALASKA A M I >
          Feb 16 11:43:44 kernel smbios0: Version: 3.0, BCD Revision: 3.0
          Feb 16 11:43:44 kernel smbios0: <System Management BIOS> at iomem 0xf05e0-0xf05fe
          Feb 16 11:43:44 kernel netgate0: <unknown hardware>
          Feb 16 11:43:44 kernel vtvga0: <VT VGA driver>
          Feb 16 11:43:44 kernel WARNING: Device "spkr" is Giant locked and may be deleted before FreeBSD 14.0.
          Feb 16 11:43:44 kernel kbd1 at kbdmux0
          Feb 16 11:43:44 kernel module_register_init: MOD_LOAD (iwi_monitor_fw, 0xffffffff8077a580, 0) error 1
          Feb 16 11:43:44 kernel iwi_monitor: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
          Feb 16 11:43:44 kernel iwi_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi.LICENSE.
          Feb 16 11:43:44 kernel module_register_init: MOD_LOAD (iwi_ibss_fw, 0xffffffff8077a4d0, 0) error 1
          Feb 16 11:43:44 kernel iwi_ibss: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
          Feb 16 11:43:44 kernel iwi_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi.LICENSE.
          Feb 16 11:43:44 kernel module_register_init: MOD_LOAD (iwi_bss_fw, 0xffffffff8077a420, 0) error 1
          Feb 16 11:43:44 kernel iwi_bss: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
          Feb 16 11:43:44 kernel iwi_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi.LICENSE.
          Feb 16 11:43:44 kernel module_register_init: MOD_LOAD (ipw_monitor_fw, 0xffffffff8075d0d0, 0) error 1
          Feb 16 11:43:44 kernel ipw_monitor: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
          Feb 16 11:43:44 kernel ipw_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw.LICENSE.
          Feb 16 11:43:44 kernel module_register_init: MOD_LOAD (ipw_ibss_fw, 0xffffffff8075d020, 0) error 1
          Feb 16 11:43:44 kernel ipw_ibss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
          Feb 16 11:43:44 kernel ipw_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw.LICENSE.
          Feb 16 11:43:44 kernel module_register_init: MOD_LOAD (ipw_bss_fw, 0xffffffff8075cf70, 0) error 1
          Feb 16 11:43:44 kernel ipw_bss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
          Feb 16 11:43:44 kernel ipw_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw.LICENSE.
          Feb 16 11:43:44 kernel wlan: mac acl policy registered
          Feb 16 11:43:44 kernel random: entropy device external interface
          Feb 16 11:43:44 kernel TCP_ratelimit: Is now initialized
          Feb 16 11:43:44 kernel Launching APs: 1 3 2
          Feb 16 11:43:44 kernel ioapic0 <Version 2.0> irqs 0-119
          Feb 16 11:43:44 kernel random: unblocking device.
          Feb 16 11:43:44 kernel random: fast provider: "Intel Secure Key RNG"
          Feb 16 11:43:44 kernel random: registering fast source Intel Secure Key RNG
          Feb 16 11:43:44 kernel FreeBSD/SMP: 1 package(s) x 2 core(s) x 2 hardware threads
          Feb 16 11:43:44 kernel FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
          Feb 16 11:43:44 kernel ACPI APIC Table: <ALASKA A M I >
          Feb 16 11:43:44 kernel Event timer "LAPIC" quality 600
          Feb 16 11:43:44 kernel avail memory = 16481058816 (15717 MB)
          Feb 16 11:43:44 kernel real memory = 17179869184 (16384 MB)
          Feb 16 11:43:44 kernel TSC: P-state invariant, performance statistics
          Feb 16 11:43:44 kernel VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID
          Feb 16 11:43:44 kernel XSAVE Features=0xf<XSAVEOPT,XSAVEC,XINUSE,XSAVES>
          Feb 16 11:43:44 kernel Structured Extended Features3=0xc000000<IBPB,STIBP>
          Feb 16 11:43:44 kernel Structured Extended Features=0x29c67af<FSGSBASE,TSCADJ,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,NFPUSG,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PROCTRACE>
          Feb 16 11:43:44 kernel AMD Features2=0x121<LAHF,ABM,Prefetch>
          Feb 16 11:43:44 kernel AMD Features=0x2c100800<SYSCALL,NX,Page1GB,RDTSCP,LM>
          Feb 16 11:43:44 kernel Features2=0x7ffafbbf<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,SDBG,FMA,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND>
          Feb 16 11:43:44 kernel 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>
          Feb 16 11:43:44 kernel Origin="GenuineIntel" Id=0x806e9 Family=0x6 Model=0x8e Stepping=9
          Feb 16 11:43:44 kernel CPU: Intel(R) Core(TM) i3-7100U CPU @ 2.40GHz (2400.00-MHz K8-class CPU)
          Feb 16 11:43:44 kernel VT(vga): resolution 640x480
          Feb 16 11:43:44 kernel FreeBSD clang version 14.0.5 (https://github.com/llvm/llvm-project.git llvmorg-14.0.5-0-gc12386ae247c)
          Feb 16 11:43:44 kernel root@freebsd:/var/jenkins/workspace/pfSense-Plus-snapshots-23_01-main/obj/amd64/VDZvZksF/var/jenkins/workspace/pfSense-Plus-snapshots-23_01-main/sources/FreeBSD-src-plus-RELENG_23_01/amd64.amd64/sys/pfSense amd64
          Feb 16 11:43:44 kernel FreeBSD 14.0-CURRENT #0 plus-RELENG_23_01-n256037-6e914874a5e: Fri Feb 10 20:30:29 UTC 2023
          Feb 16 11:43:44 kernel FreeBSD is a registered trademark of The FreeBSD Foundation.
          Feb 16 11:43:44 kernel The Regents of the University of California. All rights reserved.
          Feb 16 11:43:44 kernel Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
          Feb 16 11:43:44 kernel Copyright (c) 1992-2022 The FreeBSD Project.
          F

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

            Are you also using PPPoE?

            If not check for a valid default route in Diag > Routes. Make sure the firewall can resolve IPs in Diag > DNS Lookup.

            Does the gateway show as up?

            Can the firewall itself connect out from Diag > Ping?

            Steve

            J 2 Replies Last reply Reply Quote 0
            • J
              jeff3820 @stephenw10
              last edited by

              @stephenw10 Thanks for the help...

              No PPPOE

              The default route is valid

              Gateway shows as up

              I cannot ping or DNS lookup anywhere except I can ping local gateways.

              No internet. Yet if I go back to 22.05 with exact same configuration then no issues at all. Exact same rules

              bmeeksB 1 Reply Last reply Reply Quote 0
              • J
                jeff3820 @stephenw10
                last edited by

                @stephenw10 So more background and more information. I have 2 identical firewalls...a main and a backup that I could use as a spare and I sometimes use it as a test firewall. When I use the backup firewall, I plug it into a switch that is on a vlan (30) of the main firewall so it get a WAN IP address of 192.168.30.102 or something similar. This has been working fine.

                I first upgraded the backup to 23.01. With 23.01 the WAN is connected but I cannot browse the internet. HOWEVER, if I connect the backup firewall directly to my fiber internet connection bypassing the main firewall...all works normally??! While that means 23.01 is working, why did it fail in the double NAT situation where 22.05 worked perfectly??

                I just updated my main firewall to 23.01 and all seems OK. I do notice either the CPU frequency is not being read right or Power-D is not working the same. My firewall used to drop down to 700 or 1000 MHz but now barely might reach 2078...typically hovers at main speed yet CPU usage is usually 2-3%.

                Any idea on the double NAT failure that fails in 23.01 but works fine in 22.05??

                1 Reply Last reply Reply Quote 0
                • bmeeksB
                  bmeeks @jeff3820
                  last edited by bmeeks

                  @jeff3820 said in 23.01 install results in no internet:

                  @stephenw10 Thanks for the help...

                  No PPPOE

                  The default route is valid

                  Gateway shows as up

                  I cannot ping or DNS lookup anywhere except I can ping local gateways.

                  No internet. Yet if I go back to 22.05 with exact same configuration then no issues at all. Exact same rules

                  Can you ping IP address 8.8.8.8?

                  What needs to be determined first is whether you have a basic Layer 2 connectivity problem or just a domain/hostname resolution problem.

                  If you can ping 8.8.8.8 successfully, (that is google.com by the way) it would indicate your physical and layer 2 connectivity is good. But if you can ping 8.8.8.8, but ping google.com fails, then that means DNS name resolution is your problem.

                  Edit: your follow-up post that seemed to post while I was typing my initial response answers some questions, so you can disregard my questions above.

                  Many times folks come to the forum and post with a problem and their description is "I lost my Internet ...", and we don't know if they lost physical connectivity, their IP address is no longer working, or if they simply lost DNS. All three lead to the same end result, but have vastly different resolutions.

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

                    Not quite sure what you're doing there but it sounds possible you might have an over matching outbound NAT rule and it's translating all traffic to an IP that's invalid where you are moving it to. That is quite a common mistake in HA setups. Is that possible?

                    If it's newer CPU it might support Intel Speed Shift. In that case the P state controls have moved to some new sysctls that are not in the gui yet.

                    Steve

                    J 1 Reply Last reply Reply Quote 0
                    • O
                      otsego
                      last edited by otsego

                      I've hit a similar issue. Upgraded a Netgate 6100 from 22.05 to 23.01. After the upgrade completes there is absolutely no internet connectivity. Unable to ping 1.1.1.1 or 8.8.8.8. I get an IP on my WAN interface (DHCP from ISP), but the route is stated as "down" by pfSense.

                      Reverting back to 22.05 through boot environments and it works immediately.

                      In my case, there is no double NAT, HA or anything like that. Just plain and simple network connection to ISP.

                      J 1 Reply Last reply Reply Quote 0
                      • J
                        jeff3820 @bmeeks
                        last edited by

                        @bmeeks I did try that. I could ping or reach neither...

                        Read above, I have 2 firewalls...main and backup. with 22.05 I could use my backup in a double NAT to the main firewall...useful when doing testing. With 23.01 using identical configuration double NAT just fails. If I hook my backup firewall to the fiber connection directly it works normally. If I downgrade my backup firewall to 22.05 it will work fine when double NATed. Just weird. SAME CONFIGURATION!

                        1 Reply Last reply Reply Quote 0
                        • J
                          jeff3820 @otsego
                          last edited by

                          @otsego Different issue because I was able to get a WAN IP.

                          1 Reply Last reply Reply Quote 0
                          • J
                            jeff3820 @stephenw10
                            last edited by jeff3820

                            @stephenw10 said in 23.01 install results in no internet:

                            Not quite sure what you're doing there but it sounds possible you might have an over matching outbound NAT rule and it's translating all traffic to an IP that's invalid where you are moving it to. That is quite a common mistake in HA setups. Is that possible?

                            The outbound NAT rules are identical between the firewalls.

                            FYI, CPU is an i3-7100U

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

                              Ah OK so not actually an HA pair?

                              So the two devices are configured identically?

                              I'm unsure how you're connecting them in the test configuration. I would expect to see a subnet conflict if it gets a WAN IP in the 192.168.30.0 subnet but also have that on an internal interface.
                              That can certainly prevent routing correctly.

                              Steve

                              J 1 Reply Last reply Reply Quote 0
                              • J
                                jeff3820 @stephenw10
                                last edited by jeff3820

                                @stephenw10 Yes, absolutely identical. Worked with 22.05 though...

                                Fiber internet---Main firewall---VLAN 30---Backup firewall---PC

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

                                  But I am correct in thinking that results in two interfaces in the same subnet?

                                  Try disabling the local interface as a test.

                                  J 1 Reply Last reply Reply Quote 0
                                  • J
                                    jeff3820 @stephenw10
                                    last edited by jeff3820

                                    @stephenw10 said in 23.01 install results in no internet:

                                    But I am correct in thinking that results in two interfaces in the same subnet?
                                    Try disabling the local interface as a test.

                                    That was it! If I disabled the VLAN 30 interface (the backup firewall had a WAN of 192.168.30.105) on the backup firewall everything started to work properly.

                                    Mystery solved!! Thank you so much.

                                    1 Reply Last reply Reply Quote 1
                                    • P
                                      puneet1984
                                      last edited by puneet1984

                                      hello

                                      tried a fresh upgrade..removed old boot env of 23.01, removed ntop package.
                                      upgrade went fine.
                                      but again got the same issue...
                                      -there is net connectivity for 1-2 min after boot and then it goes down.

                                      • CPU speed is trottled

                                      Have wireguard and tailscale installed
                                      no HAproxy/openVPN/pfblocker installed

                                      got some logs

                                      PHP ERROR: Type: 1, File: /usr/local/pkg/avahi/avahi.inc, Line: 76, Message: Uncaught TypeError: Cannot access offset of type string on string in /usr/local/pkg/avahi/avahi.inc:76
Stack trace:
#0 /usr/local/pkg/avahi/avahi.inc(129): avahi_write_config(Array)
#1 /etc/inc/pkg-utils.inc(715) : eval()'d code(1): avahi_sync_config()
#2 /etc/inc/pkg-utils.inc(715): eval()
#3 /etc/rc.start_packages(66): sync_package('Avahi')
#4 {main}
thrown @ 2023-02-22 23:18:17



Crash report begins.  Anonymous machine information:

amd64
14.0-CURRENT
FreeBSD 14.0-CURRENT #0 plus-RELENG_23_01-n256037-6e914874a5e: Fri Feb 10 20:30:29 UTC 2023     root@freebsd:/var/jenkins/workspace/pfSense-Plus-snapshots-23_01-main/obj/amd64/VDZvZksF/var/jenkins/workspace/pfSense-Plus-snapshots-23_01-main/sources/FreeBS

Crash report details:

No PHP errors found.

No FreeBSD crash data found.
			
Intel(R) Core(TM) i3-6100 CPU @ 3.70GHz
Current: 791 MHz, Max: 800 MHz
2 CPUs : 1 package(s) x 2 core(s)

                                      on V22.05

                                      Intel(R) Core(TM) i3-6100 CPU @ 3.70GHz
2 CPUs: 1 package(s) x 2 core(s)
AES-NI CPU Crypto: Yes (active)
QAT Crypto: No
                                      1 Reply Last reply Reply Quote 0
                                      • stephenw10S
                                        stephenw10 Netgate Administrator
                                        last edited by

                                        It looks like you have 3 separate issues there.

                                        A php bug in Avahi.
                                        https://redmine.pfsense.org/issues/14019

                                        A CPU clock speed issue.
                                        Try running sysctl dev.cpu.0 check the reported clock speeds

                                        Some other problem preventing traffic after some time.
                                        You need to determine exactly what's failing there. No route? No DNS? Everything blokcked? Firewall completely unresponsive?

                                        Steve

                                        P 2 Replies Last reply Reply Quote 0
                                        • P
                                          puneet1984 @stephenw10
                                          last edited by

                                          @stephenw10 said in 23.01 install results in no internet:

                                          Some other problem preventing traffic after some time.
                                          You need to determine exactly what's failing there. No route? No DNS? Everything blokcked? Firewall completely unresponsive?

                                          Steve

                                          can you elaborate with what i need to check / commands to run?

                                          1 Reply Last reply Reply Quote 0
                                          • P
                                            puneet1984 @stephenw10
                                            last edited by puneet1984

                                            @stephenw10 said in 23.01 install results in no internet:

                                            It looks like you have 3 separate issues there.

                                            A php bug in Avahi.
                                            https://redmine.pfsense.org/issues/14019

                                            A CPU clock speed issue.
                                            Try running sysctl dev.cpu.0 check the reported clock speeds

                                            Some other problem preventing traffic after some time.
                                            You need to determine exactly what's failing there. No route? No DNS? Everything blokcked? Firewall completely unresponsive?

                                            Steve

                                            i am getting this on my 22.05

                                            dev.cpu.0.freq_levels: 800/51000
dev.cpu.0.freq: 800

                                            why is the CPU throttled??

                                            GUI shows

                                            Intel(R) Core(TM) i3-6100 CPU @ 3.70GHz
2 CPUs: 1 package(s) x 2 core(s)
AES-NI CPU Crypto: Yes (active)
QAT Crypto: No

                                            sysctl -a | grep -i cpu

kern.smp.cpus: 2
kern.smp.maxcpus: 256
CPU: Intel(R) Core(TM) i3-6100 CPU @ 3.70GHz (800.00-MHz K8-class CPU)
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
cpu0: <ACPI CPU> on acpi0
hwpstate_intel0: <Intel Speed Shift> on cpu0
hwpstate_intel1: <Intel Speed Shift> on cpu1
<118>Launching the init system...Updating CPU Microcode...
CPU: Intel(R) Core(TM) i3-6100 CPU @ 3.70GHz (792.00-MHz K8-class CPU)
coretemp0: <CPU On-Die Thermal Sensors> on cpu0
CPU: Intel(R) Core(TM) i3-6100 CPU @ 3.70GHz (792.04-MHz K8-class CPU)
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
cpu0: <ACPI CPU> on acpi0
est0: <Enhanced SpeedStep Frequency Control> on cpu0
<118>Launching the init system...Updating CPU Microcode...
CPU: Intel(R) Core(TM) i3-6100 CPU @ 3.70GHz (792.04-MHz K8-class CPU)
coretemp0: <CPU On-Die Thermal Sensors> on cpu0
kern.ccpu: 0
  <cpu count="2" mask="3,0,0,0">0, 1</cpu>
kern.sched.cpusetsize: 32
kern.pin_pcpu_swi: 0
kern.racct.pcpu_threshold: 1
cpu	HAMMER
device	cpufreq
kern.vt.splash_cpu_duration: 10
kern.vt.splash_cpu_style: 2
kern.vt.splash_ncpu: 0
kern.vt.splash_cpu: 0
vfs.ncpurgeminvnodes: 16
net.inet.tcp.per_cpu_timers: 0
debug.cpufreq.verbose: 0
debug.cpufreq.lowest: 0
debug.acpi.cpu_unordered: 0
kdb.enter.default=textdump set; capture on; show registers ; run lockinfo; show pcpu; bt; ps; alltrace; capture off; textdump dump; reset
hw.model: Intel(R) Core(TM) i3-6100 CPU @ 3.70GHz
hw.ncpu: 2
hw.acpi.cpu.cx_lowest: C1
                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.