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

    fails to get WAN IPv6 address ( was wrong date and time)

    Scheduled Pinned Locked Moved General pfSense Questions
    48 Posts 4 Posters 2.6k 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.
    • L
      lifespeed
      last edited by lifespeed

      So now WAN is back at DHCP6, added don't wait for RA, not "prefix only", although hinting /60 and still set at "track interface" in the LAN. It got the WAN IPv6 this time . . . but will it next time?

      Here is the last bootup log, still has errors related to igb0, the WAN 1Gb Ethernet.

      May 24 14:10:52 	check_reload_status 		Reloading filter
May 24 14:10:52 	php-fpm 	10522 	/rc.newwanipv6: Removing static route for monitor fe80::201:xxxx:xxxx:xxx6 and adding a new route through fe80::201:5cff:fe65:1446%igb0
May 24 14:10:52 	php-fpm 	10522 	/rc.newwanipv6: The command '/usr/local/sbin/dhcpd -6 -user dhcpd -group _dhcp -chroot /var/dhcpd -cf /etc/dhcpdv6.conf -pf /var/run/dhcpdv6.pid ixl2' returned exit code '1', the output was 'Internet Systems Consortium DHCP Server 4.3.6-P1 Copyright 2004-2018 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ /etc/dhcpdv6.conf line 23: partial base64 value left over: 7. secret MCEW4oPUvz7wPqLNRGn6H3; ^ Configuration file errors encountered -- exiting If you think you have received this message due to a bug rather than a configuration issue please read the section on submitting bugs on either our web page at www.isc.org or in the README file before submitting a bug. These pages explain the proper process and the information we find helpful for debugging. exiting.'
May 24 14:10:51 	dhcpleases 		Could not deliver signal HUP to process because its pidfile (/var/run/dnsmasq.pid) does not exist, No such process.
May 24 14:10:51 	dhcpleases 		kqueue error: unknown
May 24 14:10:51 	dhcpleases 		Could not deliver signal HUP to process because its pidfile (/var/run/dnsmasq.pid) does not exist, No such process.
May 24 14:10:51 	dhcpleases 		/etc/hosts changed size from original!
May 24 14:10:50 	php-fpm 	10522 	/rc.newwanipv6: rc.newwanipv6: on (IP address: 2001:558:xxxx:45:5c87:xxxx:xxxx:xxx8) (interface: wan) (real interface: igb0).
May 24 14:10:50 	php-fpm 	10522 	/rc.newwanipv6: rc.newwanipv6: Info: starting on igb0.
May 24 14:10:49 	rtsold 		Received RA specifying route fe80::201:5cff:fe65:1446 for interface wan(igb0)
May 24 14:09:53 	php-fpm 	74050 	/index.php: Successful login for user 'admin' from: 192.168.1.50 (Local Database)
May 24 14:09:45 	php-fpm 	364 	[pfBlockerNG] Starting cron process.
May 24 14:09:45 	php-fpm 	364 	/rc.start_packages: Restarting/Starting all packages.
May 24 14:09:45 	kernel 		done.
May 24 14:09:45 	syslogd 		kernel boot file is /boot/kernel/kernel
May 24 14:09:45 	syslogd 		exiting on signal 15
May 24 14:09:45 	kernel 		done.
May 24 14:09:45 	php-cgi 		rc.bootup: Creating rrd update script
May 24 14:09:44 	php-fpm 	363 	/rc.dyndns.update: Dynamic DNS (pfsense.mydomain.com) There was an error trying to determine the public IP for interface - wan (igb0 ).
May 24 14:09:44 	php-fpm 	363 	/rc.dyndns.update: Dynamic DNS (pfsense.mydomain.com): running get_failover_interface for wan. found igb0
May 24 14:09:44 	php-fpm 	363 	/rc.dyndns.update: Dynamic DNS: updatedns() starting
May 24 14:09:43 	php-fpm 	363 	/rc.dyndns.update: phpDynDNS (@.mydomain.com): No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry.
May 24 14:09:43 	php-fpm 	363 	/rc.dyndns.update: Dynamic Dns (@.mydomain.com): Current WAN IP: 76.126.xxx.xxx Cached IP: 76.126.xxx.xxx
May 24 14:09:43 	php-fpm 	363 	/rc.dyndns.update: Dynamic DNS godaddy (@.mydomain.com): 76.126.xxx.xxx extracted from local system.
May 24 14:09:43 	php-fpm 	363 	/rc.dyndns.update: Dynamic DNS (@.mydomain.com): running get_failover_interface for wan. found igb0
May 24 14:09:43 	php-fpm 	363 	/rc.dyndns.update: Dynamic DNS godaddy (@.mydomain.com): 76.126.xxx.xxx extracted from local system.
May 24 14:09:43 	php-fpm 	363 	/rc.dyndns.update: Dynamic DNS: updatedns() starting
May 24 14:09:43 	kernel 		done
May 24 14:09:43 	kernel 		.done.
May 24 14:09:42 	kernel 		....
May 24 14:09:42 	check_reload_status 		Updating all dyndns
May 24 14:09:42 	dhcpleases 		kqueue error: unknown
May 24 14:09:42 	kernel 		done.
May 24 14:09:42 	kernel 		done.
May 24 14:09:42 	php-cgi 		rc.bootup: NTPD is starting up.
May 24 14:09:42 	kernel 		done.
May 24 14:09:42 	kernel 		done.
May 24 14:09:41 	kernel 		done.
May 24 14:09:41 	kernel 		done.
May 24 14:09:41 	dhcpleases 		Could not deliver signal HUP to process because its pidfile (/var/run/dnsmasq.pid) does not exist, No such file or directory.
May 24 14:09:41 	kernel 		done.
May 24 14:09:41 	php-cgi 		rc.bootup: Gateway, none 'available' for inet6, use the first one configured. 'WAN_DHCP6'
May 24 14:09:41 	php-cgi 		rc.bootup: Default gateway setting Interface WAN_DHCP Gateway as default.
May 24 14:09:40 	kernel 		.done.
May 24 14:09:40 	kernel 		pflog0: promiscuous mode enabled
May 24 14:09:39 	php-cgi 		rc.bootup: The command '/sbin/route delete -host 2620:fe::9' returned exit code '68', the output was 'route: bad address: 2620:fe::9'
May 24 14:09:16 	php-cgi 		rc.bootup: The command '/sbin/route delete -host 2620:fe::fe' returned exit code '68', the output was 'route: bad address: 2620:fe::fe'
May 24 14:08:52 	php-cgi 		rc.bootup: The command '/sbin/route delete -host 2606:4700:4700::1001' returned exit code '68', the output was 'route: bad address: 2606:4700:4700::1001'
May 24 14:08:28 	php-cgi 		rc.bootup: The command '/sbin/route delete -host 2606:4700:4700::1111' returned exit code '68', the output was 'route: bad address: 2606:4700:4700::1111'
May 24 14:08:05 	php-fpm 	364 	/rc.newwanip: The command '/sbin/route delete -host 2620:fe::9' returned exit code '68', the output was 'route: bad address: 2620:fe::9'
May 24 14:07:41 	php-fpm 	364 	/rc.newwanip: The command '/sbin/route delete -host 2620:fe::fe' returned exit code '68', the output was 'route: bad address: 2620:fe::fe'
May 24 14:07:18 	php-fpm 	364 	/rc.newwanip: The command '/sbin/route delete -host 2606:4700:4700::1001' returned exit code '68', the output was 'route: bad address: 2606:4700:4700::1001'
May 24 14:06:54 	php-fpm 	364 	/rc.newwanip: The command '/sbin/route delete -host 2606:4700:4700::1111' returned exit code '68', the output was 'route: bad address: 2606:4700:4700::1111'
May 24 14:06:33 	php-cgi 		rc.bootup: Resyncing OpenVPN instances.
May 24 14:06:33 	kernel 		ixl2: link state changed to UP
May 24 14:06:33 	kernel 		ixl2: Link is up, 10 Gbps Full Duplex, Requested FEC: None, Negotiated FEC: None, Autoneg: False, Flow Control: None
May 24 14:06:33 	check_reload_status 		Linkup starting ixl2
May 24 14:06:33 	php-cgi 		rc.bootup: Starting dhcp6 client for interface wan igb0 in DHCP6 without RA mode
May 24 14:06:31 	php-fpm 	364 	/rc.newwanip: rc.newwanip: on (IP address: 76.126.xxx.xxx) (interface: WAN[wan]) (real interface: igb0).
May 24 14:06:31 	php-fpm 	364 	/rc.newwanip: rc.newwanip: Info: starting on igb0.
May 24 14:06:30 	php-cgi 		rc.bootup: Accept router advertisements on interface igb0
May 24 14:06:30 	php-cgi 		rc.bootup: calling interface_dhcpv6_configure.
May 24 14:06:30 	check_reload_status 		rc.newwanip starting igb0
May 24 14:06:29 	kernel 		igb0: link state changed to UP
May 24 14:06:29 	check_reload_status 		Linkup starting igb0
May 24 14:06:27 	syslogd 		Logging subprocess 7479 (exec /usr/local/sbin/sshguard) exited due to signal 15.
May 24 14:06:27 	sshd 	7285 	Server listening on 0.0.0.0 port 22614.
May 24 14:06:27 	sshd 	7285 	Server listening on :: port 22614.
May 24 14:06:26 	kernel 		aesni0: <AES-CBC,AES-XTS,AES-GCM,AES-ICM> on motherboard
May 24 14:06:26 	kernel 		padlock0: No ACE support.
May 24 14:06:26 	kernel 		TSC: P-state invariant, performance statistics
May 24 14:06:26 	kernel 		VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID,VID,PostIntr
May 24 14:06:26 	kernel 		XSAVE Features=0xf<XSAVEOPT,XSAVEC,XINUSE,XSAVES>
May 24 14:06:26 	kernel 		Structured Extended Features3=0x9c002400<IBPB,STIBP,SSBD>
May 24 14:06:26 	kernel 		Structured Extended Features2=0x8<PKU>
May 24 14:06:26 	kernel 		Structured Extended Features=0xd39ffffb<FSGSBASE,TSCADJ,BMI1,HLE,AVX2,FDPEXC,SMEP,BMI2,ERMS,INVPCID,RTM,PQM,NFPUSG,MPX,PQE,AVX512F,AVX512DQ,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,PROCTRACE,AVX512CD,AVX512BW,AVX512VL>
May 24 14:06:26 	kernel 		AMD Features2=0x121<LAHF,ABM,Prefetch>
May 24 14:06:26 	kernel 		AMD Features=0x2c100800<SYSCALL,NX,Page1GB,RDTSCP,LM>
May 24 14:06:26 	kernel 		Features2=0x7ffefbff<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND>
May 24 14:06:26 	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>
May 24 14:06:26 	kernel 		Origin="GenuineIntel" Id=0x50654 Family=0x6 Model=0x55 Stepping=4
May 24 14:06:26 	kernel 		CPU: Intel(R) Xeon(R) D-2123IT CPU @ 2.20GHz (2194.92-MHz K8-class CPU)
May 24 14:06:26 	kernel 		random: unblocking device.
May 24 14:06:26 	kernel 		Trying to mount root from zfs:zroot/ROOT/default []...
May 24 14:06:26 	kernel 		ses0: SEMB SES Device
May 24 14:06:26 	kernel 		ses0: <AHCI SGPIO Enclosure 1.00 0001> SEMB S-E-S 2.00 device
May 24 14:06:26 	kernel 		ses0 at ahciem0 bus 0 scbus6 target 0 lun 0
May 24 14:06:26 	kernel 		uhub3: 4 ports with 4 removable, self powered
May 24 14:06:26 	kernel 		uhub3: MTT enabled
May 24 14:06:26 	kernel 		uhub3: <vendor 0x05e3 USB2.0 Hub, class 9/0, rev 2.00/32.98, addr 4> on usbus0
May 24 14:06:26 	kernel 		uhub3 numa-domain 0 on uhub2
May 24 14:06:26 	kernel 		ugen0.5: <vendor 0x05e3 USB2.0 Hub> at usbus0
May 24 14:06:26 	kernel 		uhub2: 4 ports with 4 removable, self powered
May 24 14:06:26 	kernel 		uhub2: MTT enabled
May 24 14:06:26 	kernel 		uhub2: <vendor 0x05e3 USB2.0 Hub, class 9/0, rev 2.00/32.98, addr 3> on usbus0
May 24 14:06:26 	kernel 		uhub2 numa-domain 0 on uhub0
May 24 14:06:26 	kernel 		ugen0.4: <vendor 0x05e3 USB2.0 Hub> at usbus0
May 24 14:06:26 	kernel 		kbd2 at ukbd0
May 24 14:06:26 	kernel 		ukbd0: <vendor 0x0557 product 0x2419, class 0/0, rev 1.10/1.00, addr 2> on usbus0
May 24 14:06:26 	kernel 		ukbd0 numa-domain 0 on uhub1
May 24 14:06:26 	kernel 		ugen0.3: <vendor 0x0557 product 0x2419> at usbus0
May 24 14:06:26 	kernel 		uhub1: 4 ports with 3 removable, self powered
May 24 14:06:26 	kernel 		uhub1: <vendor 0x0557 product 0x7000, class 9/0, rev 2.00/0.00, addr 1> on usbus0
May 24 14:06:26 	kernel 		uhub1 numa-domain 0 on uhub0
May 24 14:06:26 	kernel 		ugen0.2: <vendor 0x0557 product 0x7000> at usbus0
May 24 14:06:26 	kernel 		uhub0: 26 ports with 26 removable, self powered
May 24 14:06:26 	kernel 		nvd0: 476940MB (976773168 512 byte sectors)
May 24 14:06:26 	kernel 		nvd0: <Samsung SSD 970 EVO 500GB> NVMe namespace
May 24 14:06:26 	kernel 		uhub0: <0x8086 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0
May 24 14:06:26 	kernel 		ugen0.1: <0x8086 XHCI root HUB> at usbus0
May 24 14:06:26 	kernel 		Timecounters tick every 1.000 msec
May 24 14:06:26 	kernel 		ZFS storage pool version: features support (5000)
May 24 14:06:26 	kernel 		ZFS filesystem version: 5
May 24 14:06:26 	kernel 		est7: <Enhanced SpeedStep Frequency Control> numa-domain 0 on cpu7
May 24 14:06:26 	kernel 		est6: <Enhanced SpeedStep Frequency Control> numa-domain 0 on cpu6
May 24 14:06:26 	kernel 		est5: <Enhanced SpeedStep Frequency Control> numa-domain 0 on cpu5
May 24 14:06:26 	kernel 		est4: <Enhanced SpeedStep Frequency Control> numa-domain 0 on cpu4
May 24 14:06:26 	kernel 		est3: <Enhanced SpeedStep Frequency Control> numa-domain 0 on cpu3
May 24 14:06:26 	kernel 		est2: <Enhanced SpeedStep Frequency Control> numa-domain 0 on cpu2
May 24 14:06:26 	kernel 		est1: <Enhanced SpeedStep Frequency Control> numa-domain 0 on cpu1
May 24 14:06:26 	kernel 		est0: <Enhanced SpeedStep Frequency Control> numa-domain 0 on cpu0
May 24 14:06:26 	kernel 		ppc0: cannot reserve I/O port range
May 24 14:06:26 	kernel 		orm0: <ISA Option ROM> at iomem 0xc0000-0xc7fff on isa0
May 24 14:06:26 	kernel 		uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0
May 24 14:06:26 	kernel 		uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
May 24 14:06:26 	kernel 		pci9: <dasp, performance counters> at device 18.1 (no driver attached)
May 24 14:06:26 	kernel 		pci9: <dasp, performance counters> at device 18.0 (no driver attached)
May 24 14:06:26 	kernel 		ixl3: netmap queues/slots: TX 8/1024, RX 8/1024
May 24 14:06:26 	kernel 		queues is 0xfffffe00018ee000
May 24 14:06:26 	kernel 		ixl3: SR-IOV ready
May 24 14:06:26 	kernel 		ixl3: Ethernet address: 00:25:90:bb:bf:0d
May 24 14:06:26 	kernel 		ixl3: Allocating 8 queues for PF LAN VSI; 8 queues active
May 24 14:06:26 	kernel 		ixl3: Using MSIX interrupts with 9 vectors
May 24 14:06:26 	kernel 		ixl3: PF-ID[3]: VFs 32, MSIX 129, VF MSIX 5, QPs 384, I2C
May 24 14:06:26 	kernel 		ixl3: fw 3.1.57069 api 1.5 nvm 3.33 etid 80001006 oem 1.262.0
May 24 14:06:26 	kernel 		ixl3: using 1024 tx descriptors and 1024 rx descriptors
May 24 14:06:26 	kernel 		ixl3: <Intel(R) Ethernet Connection 700 Series PF Driver, Version - 1.9.9-k> mem 0xf7000000-0xf7ffffff,0xfb000000-0xfb007fff irq 46 at device 0.3 numa-domain 0 on pci12
May 24 14:06:26 	kernel 		ixl2: netmap queues/slots: TX 8/1024, RX 8/1024
May 24 14:06:26 	kernel 		queues is 0xfffffe00017a0000
May 24 14:06:26 	kernel 		ixl2: SR-IOV ready
May 24 14:06:26 	kernel 		ixl2: Ethernet address: 00:25:90:bb:bf:0c
May 24 14:06:26 	kernel 		ixl2: Allocating 8 queues for PF LAN VSI; 8 queues active
May 24 14:06:26 	kernel 		ixl2: Using MSIX interrupts with 9 vectors
May 24 14:06:26 	kernel 		ixl2: PF-ID[2]: VFs 32, MSIX 129, VF MSIX 5, QPs 384, I2C
May 24 14:06:26 	kernel 		ixl2: fw 3.1.57069 api 1.5 nvm 3.33 etid 80001006 oem 1.262.0
May 24 14:06:26 	kernel 		ixl2: using 1024 tx descriptors and 1024 rx descriptors
May 24 14:06:26 	kernel 		ixl2: <Intel(R) Ethernet Connection 700 Series PF Driver, Version - 1.9.9-k> mem 0xf8000000-0xf8ffffff,0xfb008000-0xfb00ffff irq 46 at device 0.2 numa-domain 0 on pci12
May 24 14:06:26 	kernel 		ixl1: netmap queues/slots: TX 8/1024, RX 8/1024
May 24 14:06:26 	kernel 		queues is 0xfffffe0001664000
May 24 14:06:26 	kernel 		ixl1: SR-IOV ready
May 24 14:06:26 	kernel 		ixl1: Ethernet address: 00:25:90:bb:bf:0b
May 24 14:06:26 	kernel 		ixl1: Allocating 8 queues for PF LAN VSI; 8 queues active
May 24 14:06:26 	kernel 		ixl1: Using MSIX interrupts with 9 vectors
May 24 14:06:26 	kernel 		ixl1: PF-ID[1]: VFs 32, MSIX 129, VF MSIX 5, QPs 384, MDIO shared
May 24 14:06:26 	kernel 		ixl1: fw 3.1.57069 api 1.5 nvm 3.33 etid 80001006 oem 1.262.0
May 24 14:06:26 	kernel 		ixl1: using 1024 tx descriptors and 1024 rx descriptors
May 24 14:06:26 	kernel 		ixl1: <Intel(R) Ethernet Connection 700 Series PF Driver, Version - 1.9.9-k> mem 0xf9000000-0xf9ffffff,0xfb010000-0xfb017fff irq 46 at device 0.1 numa-domain 0 on pci12
May 24 14:06:26 	kernel 		ixl0: netmap queues/slots: TX 8/1024, RX 8/1024
May 24 14:06:26 	kernel 		queues is 0xfffffe0001528000
May 24 14:06:26 	kernel 		ixl0: SR-IOV ready
May 24 14:06:26 	kernel 		ixl0: Ethernet address: 00:25:90:bb:bf:0a
May 24 14:06:26 	kernel 		ixl0: Allocating 8 queues for PF LAN VSI; 8 queues active
May 24 14:06:26 	kernel 		ixl0: Using MSIX interrupts with 9 vectors
May 24 14:06:26 	kernel 		ixl0: PF-ID[0]: VFs 32, MSIX 129, VF MSIX 5, QPs 384, MDIO shared
May 24 14:06:26 	kernel 		ixl0: fw 3.1.57069 api 1.5 nvm 3.33 etid 80001006 oem 1.262.0
May 24 14:06:26 	kernel 		ixl0: using 1024 tx descriptors and 1024 rx descriptors
May 24 14:06:26 	kernel 		ixl0: <Intel(R) Ethernet Connection 700 Series PF Driver, Version - 1.9.9-k> mem 0xfa000000-0xfaffffff,0xfb018000-0xfb01ffff irq 46 at device 0.0 numa-domain 0 on pci12
May 24 14:06:26 	kernel 		pci12: <ACPI PCI bus> numa-domain 0 on pcib12
May 24 14:06:26 	kernel 		pcib12: <ACPI PCI-PCI bridge> irq 40 at device 3.0 numa-domain 0 on pci11
May 24 14:06:26 	kernel 		pci11: <ACPI PCI bus> numa-domain 0 on pcib11
May 24 14:06:26 	kernel 		pcib11: <ACPI PCI-PCI bridge> mem 0xfbe00000-0xfbe1ffff irq 48 at device 0.0 numa-domain 0 on pci10
May 24 14:06:26 	kernel 		pci10: <ACPI PCI bus> numa-domain 0 on pcib10
May 24 14:06:26 	kernel 		pcib10: <ACPI PCI-PCI bridge> irq 55 at device 0.0 numa-domain 0 on pci9
May 24 14:06:26 	kernel 		pci9: <ACPI PCI bus> numa-domain 0 on pcib9
May 24 14:06:26 	kernel 		pcib9: _OSC returned error 0x10
May 24 14:06:26 	kernel 		pcib9: <ACPI Host-PCI bridge> numa-domain 0 on acpi0
May 24 14:06:26 	kernel 		igb3: netmap queues/slots: TX 8/1024, RX 8/1024
May 24 14:06:26 	kernel 		igb3: Bound queue 7 to cpu 7
May 24 14:06:26 	kernel 		igb3: Bound queue 6 to cpu 6
May 24 14:06:26 	kernel 		igb3: Bound queue 5 to cpu 5
May 24 14:06:26 	kernel 		igb3: Bound queue 4 to cpu 4
May 24 14:06:26 	kernel 		igb3: Bound queue 3 to cpu 3
May 24 14:06:26 	kernel 		igb3: Bound queue 2 to cpu 2
May 24 14:06:26 	kernel 		igb3: Bound queue 1 to cpu 1
May 24 14:06:26 	kernel 		igb3: Bound queue 0 to cpu 0
May 24 14:06:26 	kernel 		igb3: Ethernet address: 00:25:90:ba:53:67
May 24 14:06:26 	kernel 		igb3: Using MSIX interrupts with 9 vectors
May 24 14:06:26 	kernel 		igb3: <Intel(R) PRO/1000 Network Connection, Version - 2.5.3-k> port 0xb000-0xb01f mem 0xe0d00000-0xe0d1ffff,0xe0d80000-0xe0d83fff irq 45 at device 0.3 numa-domain 0 on pci8
May 24 14:06:26 	kernel 		igb2: netmap queues/slots: TX 8/1024, RX 8/1024
May 24 14:06:26 	kernel 		igb2: Bound queue 7 to cpu 7
May 24 14:06:26 	kernel 		igb2: Bound queue 6 to cpu 6
May 24 14:06:26 	kernel 		igb2: Bound queue 5 to cpu 5
May 24 14:06:26 	kernel 		igb2: Bound queue 4 to cpu 4
May 24 14:06:26 	kernel 		igb2: Bound queue 3 to cpu 3
May 24 14:06:26 	kernel 		igb2: Bound queue 2 to cpu 2
May 24 14:06:26 	kernel 		igb2: Bound queue 1 to cpu 1
May 24 14:06:26 	kernel 		igb2: Bound queue 0 to cpu 0
May 24 14:06:26 	kernel 		igb2: Ethernet address: 00:25:90:ba:53:66
May 24 14:06:26 	kernel 		igb2: Using MSIX interrupts with 9 vectors
May 24 14:06:26 	kernel 		igb2: <Intel(R) PRO/1000 Network Connection, Version - 2.5.3-k> port 0xb020-0xb03f mem 0xe0d20000-0xe0d3ffff,0xe0d84000-0xe0d87fff irq 44 at device 0.2 numa-domain 0 on pci8
May 24 14:06:26 	kernel 		igb1: netmap queues/slots: TX 8/1024, RX 8/1024
May 24 14:06:26 	kernel 		igb1: Bound queue 7 to cpu 7
May 24 14:06:26 	kernel 		igb1: Bound queue 6 to cpu 6
May 24 14:06:26 	kernel 		igb1: Bound queue 5 to cpu 5
May 24 14:06:26 	kernel 		igb1: Bound queue 4 to cpu 4
May 24 14:06:26 	kernel 		igb1: Bound queue 3 to cpu 3
May 24 14:06:26 	kernel 		igb1: Bound queue 2 to cpu 2
May 24 14:06:26 	kernel 		igb1: Bound queue 1 to cpu 1
May 24 14:06:26 	kernel 		igb1: Bound queue 0 to cpu 0
May 24 14:06:26 	kernel 		igb1: Ethernet address: 00:25:90:ba:53:65
May 24 14:06:26 	kernel 		igb1: Using MSIX interrupts with 9 vectors
May 24 14:06:26 	kernel 		igb1: <Intel(R) PRO/1000 Network Connection, Version - 2.5.3-k> port 0xb040-0xb05f mem 0xe0d40000-0xe0d5ffff,0xe0d88000-0xe0d8bfff irq 46 at device 0.1 numa-domain 0 on pci8
May 24 14:06:26 	kernel 		igb0: netmap queues/slots: TX 8/1024, RX 8/1024
May 24 14:06:26 	kernel 		igb0: Bound queue 7 to cpu 7
May 24 14:06:26 	kernel 		igb0: Bound queue 6 to cpu 6
May 24 14:06:26 	kernel 		igb0: Bound queue 5 to cpu 5
May 24 14:06:26 	kernel 		igb0: Bound queue 4 to cpu 4
May 24 14:06:26 	kernel 		igb0: Bound queue 3 to cpu 3
May 24 14:06:26 	kernel 		igb0: Bound queue 2 to cpu 2
May 24 14:06:26 	kernel 		igb0: Bound queue 1 to cpu 1
May 24 14:06:26 	kernel 		igb0: Bound queue 0 to cpu 0
May 24 14:06:26 	kernel 		igb0: Ethernet address: 00:25:90:ba:53:64
May 24 14:06:26 	kernel 		igb0: Using MSIX interrupts with 9 vectors
May 24 14:06:26 	kernel 		igb0: <Intel(R) PRO/1000 Network Connection, Version - 2.5.3-k> port 0xb060-0xb07f mem 0xe0d60000-0xe0d7ffff,0xe0d8c000-0xe0d8ffff irq 43 at device 0.0 numa-domain 0 on pci8
May 24 14:06:26 	kernel 		pci8: <ACPI PCI bus> numa-domain 0 on pcib8
May 24 14:06:26 	kernel 		pcib8: <ACPI PCI-PCI bridge> irq 47 at device 3.0 numa-domain 0 on pci6
May 24 14:06:26 	kernel 		nvme0: <Generic NVMe Device> mem 0xe0e00000-0xe0e03fff irq 42 at device 0.0 numa-domain 0 on pci7
May 24 14:06:26 	kernel 		pci7: <ACPI PCI bus> numa-domain 0 on pcib7
May 24 14:06:26 	kernel 		pcib7: <ACPI PCI-PCI bridge> irq 47 at device 2.0 numa-domain 0 on pci6
May 24 14:06:26 	kernel 		pci6: <ACPI PCI bus> numa-domain 0 on pcib6
May 24 14:06:26 	kernel 		pcib6: _OSC returned error 0x10
May 24 14:06:26 	kernel 		pcib6: <ACPI Host-PCI bridge> numa-domain 0 on acpi0
May 24 14:06:26 	kernel 		pci5: <ACPI PCI bus> numa-domain 0 on pcib5
May 24 14:06:26 	kernel 		pcib5: _OSC returned error 0x10
May 24 14:06:26 	kernel 		pcib5: <ACPI Host-PCI bridge> numa-domain 0 on acpi0
May 24 14:06:26 	kernel 		pci0: <serial bus> at device 31.5 (no driver attached)
May 24 14:06:26 	kernel 		pci0: <memory> at device 31.2 (no driver attached)
May 24 14:06:26 	kernel 		isa0: <ISA bus> numa-domain 0 on isab0
May 24 14:06:26 	kernel 		isab0: <PCI-ISA bridge> at device 31.0 numa-domain 0 on pci0
May 24 14:06:26 	kernel 		pci4: <ACPI PCI bus> numa-domain 0 on pcib4
May 24 14:06:26 	kernel 		pcib4: <ACPI PCI-PCI bridge> irq 16 at device 29.0 numa-domain 0 on pci0
May 24 14:06:26 	kernel 		vgapci0: Boot video device
May 24 14:06:26 	kernel 		vgapci0: <VGA-compatible display> port 0x2000-0x207f mem 0xa9000000-0xa9ffffff,0xaa000000-0xaa01ffff irq 16 at device 0.0 numa-domain 0 on pci3
May 24 14:06:26 	kernel 		pci3: <ACPI PCI bus> numa-domain 0 on pcib3
May 24 14:06:26 	kernel 		pcib3: <ACPI PCI-PCI bridge> irq 16 at device 0.0 numa-domain 0 on pci2
May 24 14:06:26 	kernel 		pci2: <ACPI PCI bus> numa-domain 0 on pcib2
May 24 14:06:26 	kernel 		pcib2: <ACPI PCI-PCI bridge> irq 16 at device 28.4 numa-domain 0 on pci0
May 24 14:06:26 	kernel 		pci1: <ACPI PCI bus> numa-domain 0 on pcib1
May 24 14:06:26 	kernel 		pcib1: <ACPI PCI-PCI bridge> irq 16 at device 28.0 numa-domain 0 on pci0
May 24 14:06:26 	kernel 		pci0: <simple comms> at device 22.4 (no driver attached)
May 24 14:06:26 	kernel 		pci0: <simple comms> at device 22.1 (no driver attached)
May 24 14:06:26 	kernel 		pci0: <simple comms> at device 22.0 (no driver attached)
May 24 14:06:26 	kernel 		usbus0: 5.0Gbps Super Speed USB v3.0
May 24 14:06:26 	kernel 		usbus0 numa-domain 0 on xhci0
May 24 14:06:26 	kernel 		xhci_interrupt: host controller halted
May 24 14:06:26 	kernel 		usbus0: waiting for BIOS to give up control
May 24 14:06:26 	kernel 		xhci0: 32 bytes context size, 64-bit DMA
May 24 14:06:26 	kernel 		xhci0: <Intel Lewisburg USB 3.0 controller> mem 0xaa180000-0xaa18ffff irq 16 at device 20.0 numa-domain 0 on pci0
May 24 14:06:26 	kernel 		ahciem0: <AHCI enclosure management bridge> on ahci0
May 24 14:06:26 	kernel 		ahcich5: <AHCI channel> at channel 5 on ahci0
May 24 14:06:26 	kernel 		ahcich4: <AHCI channel> at channel 4 on ahci0
May 24 14:06:26 	kernel 		ahcich3: <AHCI channel> at channel 3 on ahci0
May 24 14:06:26 	kernel 		ahcich2: <AHCI channel> at channel 2 on ahci0
May 24 14:06:26 	kernel 		ahcich1: <AHCI channel> at channel 1 on ahci0
May 24 14:06:26 	kernel 		ahcich0: <AHCI channel> at channel 0 on ahci0
May 24 14:06:26 	kernel 		ahci0: AHCI v1.31 with 6 6Gbps ports, Port Multiplier not supported
May 24 14:06:26 	kernel 		ahci0: <Intel Lewisburg AHCI SATA controller> port 0x3030-0x3037,0x3020-0x3023,0x3000-0x301f mem 0xaa194000-0xaa195fff,0xaa196000-0xaa1960ff,0xaa100000-0xaa17ffff irq 16 at device 17.5 numa-domain 0 on pci0
May 24 14:06:26 	kernel 		pci0: <unknown> at device 17.1 (no driver attached)
May 24 14:06:26 	kernel 		pci0: <unknown> at device 17.0 (no driver attached)
May 24 14:06:26 	kernel 		pci0: <dasp, performance counters> at device 8.1 (no driver attached)
May 24 14:06:26 	kernel 		pci0: <ACPI PCI bus> numa-domain 0 on pcib0
May 24 14:06:26 	kernel 		pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff numa-domain 0 on acpi0
May 24 14:06:26 	kernel 		acpi_syscontainer0: <System Container> on acpi0
May 24 14:06:26 	kernel 		acpi_timer0: <24-bit timer at 3.579545MHz> port 0x508-0x50b on acpi0
May 24 14:06:26 	kernel 		Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
May 24 14:06:26 	kernel 		device_attach: hpet1 attach returned 12
May 24 14:06:26 	kernel 		hpet1: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
May 24 14:06:26 	kernel 		Event timer "HPET" frequency 24000000 Hz quality 550
May 24 14:06:26 	kernel 		Timecounter "HPET" frequency 24000000 Hz quality 950
May 24 14:06:26 	kernel 		hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
May 24 14:06:26 	kernel 		Event timer "i8254" frequency 1193182 Hz quality 100
May 24 14:06:26 	kernel 		Timecounter "i8254" frequency 1193182 Hz quality 0
May 24 14:06:26 	kernel 		attimer0: <AT timer> port 0x40-0x43,0x50-0x53 irq 0 on acpi0
May 24 14:06:26 	kernel 		Event timer "RTC" frequency 32768 Hz quality 0
May 24 14:06:26 	kernel 		atrtc0: registered as a time-of-day clock, resolution 1.000000s
May 24 14:06:26 	kernel 		atrtc0: <AT realtime clock> port 0x70-0x71,0x74-0x77 irq 8 on acpi0
May 24 14:06:26 	kernel 		cpu7: <ACPI CPU> numa-domain 0 on acpi0
May 24 14:06:26 	kernel 		cpu6: <ACPI CPU> numa-domain 0 on acpi0
May 24 14:06:26 	kernel 		cpu5: <ACPI CPU> numa-domain 0 on acpi0
May 24 14:06:26 	kernel 		cpu4: <ACPI CPU> numa-domain 0 on acpi0
May 24 14:06:26 	kernel 		cpu3: <ACPI CPU> numa-domain 0 on acpi0
May 24 14:06:26 	kernel 		cpu2: <ACPI CPU> numa-domain 0 on acpi0
May 24 14:06:26 	kernel 		cpu1: <ACPI CPU> numa-domain 0 on acpi0
May 24 14:06:26 	kernel 		cpu0: <ACPI CPU> numa-domain 0 on acpi0
May 24 14:06:26 	kernel 		acpi0: Power Button (fixed)
May 24 14:06:26 	kernel 		acpi0: <SUPERM SUPERM> on motherboard
May 24 14:06:26 	kernel 		padlock0: No ACE support.
May 24 14:06:26 	kernel 		cryptosoft0: <software crypto> on motherboard
May 24 14:06:26 	kernel 		nexus0
May 24 14:06:26 	kernel 		random: fast provider: "Intel Secure Key RNG"
May 24 14:06:26 	kernel 		random: registering fast source Intel Secure Key RNG
May 24 14:06:26 	kernel 		module_register_init: MOD_LOAD (vesa, 0xffffffff8120aaa0, 0) error 19
May 24 14:06:26 	kernel 		netmap: loaded module
May 24 14:06:26 	kernel 		kbd1 at kbdmux0
May 24 14:06:26 	kernel 		wlan: mac acl policy registered
May 24 14:06:26 	kernel 		module_register_init: MOD_LOAD (iwi_monitor_fw, 0xffffffff806a85c0, 0) error 1
May 24 14:06:26 	kernel 		iwi_monitor: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
May 24 14:06:26 	kernel 		iwi_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi.LICENSE.
May 24 14:06:26 	kernel 		module_register_init: MOD_LOAD (iwi_ibss_fw, 0xffffffff806a8510, 0) error 1
May 24 14:06:26 	kernel 		iwi_ibss: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
May 24 14:06:26 	kernel 		iwi_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi.LICENSE.
May 24 14:06:26 	kernel 		module_register_init: MOD_LOAD (iwi_bss_fw, 0xffffffff806a8460, 0) error 1
May 24 14:06:26 	kernel 		iwi_bss: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
May 24 14:06:26 	kernel 		iwi_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi.LICENSE.
May 24 14:06:26 	kernel 		module_register_init: MOD_LOAD (ipw_monitor_fw, 0xffffffff80681590, 0) error 1
May 24 14:06:26 	kernel 		ipw_monitor: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
May 24 14:06:26 	kernel 		ipw_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw.LICENSE.
May 24 14:06:26 	kernel 		module_register_init: MOD_LOAD (ipw_ibss_fw, 0xffffffff806814e0, 0) error 1
May 24 14:06:26 	kernel 		ipw_ibss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
May 24 14:06:26 	kernel 		ipw_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw.LICENSE.
May 24 14:06:26 	kernel 		random: entropy device external interface
May 24 14:06:26 	kernel 		module_register_init: MOD_LOAD (ipw_bss_fw, 0xffffffff80681430, 0) error 1
May 24 14:06:26 	kernel 		ipw_bss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
May 24 14:06:26 	kernel 		ipw_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw.LICENSE.
May 24 14:06:26 	kernel 		Timecounter "TSC-low" frequency 1097459592 Hz quality 1000
May 24 14:06:26 	kernel 		SMP: AP CPU #2 Launched!
May 24 14:06:26 	kernel 		SMP: AP CPU #6 Launched!
May 24 14:06:26 	kernel 		SMP: AP CPU #4 Launched!
May 24 14:06:26 	kernel 		SMP: AP CPU #3 Launched!
May 24 14:06:26 	kernel 		SMP: AP CPU #5 Launched!
May 24 14:06:26 	kernel 		SMP: AP CPU #7 Launched!
May 24 14:06:26 	kernel 		SMP: AP CPU #1 Launched!
May 24 14:06:26 	kernel 		ioapic4 <Version 2.0> irqs 48-55 on motherboard
May 24 14:06:26 	kernel 		ioapic3 <Version 2.0> irqs 40-47 on motherboard
May 24 14:06:26 	kernel 		ioapic2 <Version 2.0> irqs 32-39 on motherboard
May 24 14:06:26 	kernel 		ioapic1 <Version 2.0> irqs 24-31 on motherboard
May 24 14:06:26 	kernel 		ioapic0 <Version 2.0> irqs 0-23 on motherboard
May 24 14:06:26 	kernel 		FreeBSD/SMP: 1 package(s) x 4 core(s) x 2 hardware threads
May 24 14:06:26 	kernel 		FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs
May 24 14:06:26 	kernel 		ACPI APIC Table: <SUPERM SMCI--MB>
May 24 14:06:26 	kernel 		Event timer "LAPIC" quality 600
May 24 14:06:26 	kernel 		avail memory = 32890949632 (31367 MB)
May 24 14:06:26 	kernel 		real memory = 34359738368 (32768 MB)
May 24 14:06:26 	kernel 		TSC: P-state invariant, performance statistics
May 24 14:06:26 	kernel 		VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID,VID,PostIntr
May 24 14:06:26 	kernel 		XSAVE Features=0xf<XSAVEOPT,XSAVEC,XINUSE,XSAVES>
May 24 14:06:26 	kernel 		Structured Extended Features3=0x9c002400<IBPB,STIBP,SSBD>
May 24 14:06:26 	kernel 		Structured Extended Features2=0x8<PKU>
May 24 14:06:26 	kernel 		Structured Extended Features=0xd39ffffb<FSGSBASE,TSCADJ,BMI1,HLE,AVX2,FDPEXC,SMEP,BMI2,ERMS,INVPCID,RTM,PQM,NFPUSG,MPX,PQE,AVX512F,AVX512DQ,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,PROCTRACE,AVX512CD,AVX512BW,AVX512VL>
May 24 14:06:26 	kernel 		AMD Features2=0x121<LAHF,ABM,Prefetch>
May 24 14:06:26 	kernel 		AMD Features=0x2c100800<SYSCALL,NX,Page1GB,RDTSCP,LM>
May 24 14:06:26 	kernel 		Features2=0x7ffefbff<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND>
May 24 14:06:26 	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>
May 24 14:06:26 	kernel 		Origin="GenuineIntel" Id=0x50654 Family=0x6 Model=0x55 Stepping=4
May 24 14:06:26 	kernel 		CPU: Intel(R) Xeon(R) D-2123IT CPU @ 2.20GHz (2194.92-MHz K8-class CPU)
May 24 14:06:26 	kernel 		VT(efifb): resolution 1024x768
May 24 14:06:26 	kernel 		FreeBSD clang version 6.0.0 (tags/RELEASE_600/final 326565) (based on LLVM 6.0.0)
May 24 14:06:26 	kernel 		root@buildbot1-nyi.netgate.com:/build/ce-crossbuild-244/obj/amd64/ZfGpH5cd/build/ce-crossbuild-244/pfSense/tmp/FreeBSD-src/sys/pfSense amd64
May 24 14:06:26 	kernel 		FreeBSD 11.2-RELEASE-p10 #9 4a2bfdce133(RELENG_2_4_4): Wed May 15 18:54:42 EDT 2019
May 24 14:06:26 	kernel 		FreeBSD is a registered trademark of The FreeBSD Foundation.
May 24 14:06:26 	kernel 		The Regents of the University of California. All rights reserved.
May 24 14:06:26 	kernel 		Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
May 24 14:06:26 	kernel 		Copyright (c) 1992-2018 The FreeBSD Project.
May 24 14:06:26 	syslogd 		kernel boot file is /boot/kernel/kernel
May 24 14:02:20 	syslogd 		exiting on signal 15
May 24 14:02:20 	shutdown 		power-down by admin:
      1 Reply Last reply Reply Quote 0
      • N
        netblues
        last edited by netblues

        Its difficult to follow many issues at once.
        Since ipv6 follows the principle , of "It was difficult to design it should be difficult to operate" :P and since ntp is still mainly an ipv4 thing, I would suggest disabling ipv6 temporarily.

        The fact that ipv4 was assigned a private ip smells dhcp issues upstream anyway.
        If you get consistent ipv4 addresses among reboots, or plain enable/disable of the interface, then you could move on debugging ipv6.

        Dhcpv4 has been around for ages, and as far as pf is concerned is rock solid.
        I can't say the same for ipv6 though,

        JKnottJ 1 Reply Last reply Reply Quote 0
        • JKnottJ
          JKnott @netblues
          last edited by JKnott

          @netblues said in wrong date and time:

          Since ipv6 follows the principle , of "It was difficult to design it should be difficult to operate" :P and since ntp is still mainly an ipv4 thing, I would suggest disabling ipv6 temporarily.

          Why do some think that if there's a problem, it must be caused by IPv6? NTP is NTP and it makes no difference whether it's on IPv4 or IPv6. Many NTP sites support both IPv4 and IPv6. Take a look at the addresses for the NTP servers I connect to. IPv6 is not difficult. It's different from IPv4 in some ways, but the basic principles remain the same. Disabling IPv6 won't fix anything, as it's not the problem.

          PfSense running on Qotom mini PC
          i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
          UniFi AC-Lite access point

          I haven't lost my mind. It's around here...somewhere...

          1 Reply Last reply Reply Quote 0
          • johnpozJ
            johnpoz LAYER 8 Global Moderator
            last edited by

            With @JKnott on this your time issues have nothing to do with IPv6.. None of the ntp you listed even look to be IPv6..

            Now you could possible blame IPv6 if all you had listed was IPv6 ntp servers, and your IPv6 wasn't working?

            What could be in issue is most of your ntp servers listed are not showing 377 so possible your having issues with ntp or connectivity in general.. But you show a couple at 377..

            And your not actually synced to any of those, but your offset is crazy out of wack.. Set the date time on the machine manually.. So its close, this can speed up getting into sync with ntp source.

            But this really has nothing to do with IPv6.. be it working or not working.

            An intelligent man is sometimes forced to be drunk to spend time with his fools
            If you get confused: Listen to the Music Play
            Please don't Chat/PM me for help, unless mod related
            SG-4860 24.11 | Lab VMs 2.8, 24.11

            N 1 Reply Last reply Reply Quote 0
            • N
              netblues @johnpoz
              last edited by

              @johnpoz Gentlemen, I think you have it wrong. As I said, there are issues with dhcp v4.
              Wan seems to be getting ipv4 rfc1918 address occasionally.
              This needs to be investigated.
              Having to debug two networks is more difficult than one.
              I never said ipv6 is ntp issue related. Its just ntp issues were due to deeper dhcp issues.

              As logs above indicate, after a complete equipment reboot ntp synced fine.

              So we are past any ntp related configuration, and the focus is on dhcp.

              Both v4 and v6. I suggested to take on it, one at a time. As simple as that.

              JKnottJ 1 Reply Last reply Reply Quote 0
              • JKnottJ
                JKnott @netblues
                last edited by

                @netblues said in wrong date and time:

                Wan seems to be getting ipv4 rfc1918 address occasionally.

                This is where Packet Capture can come in handy. See what happens when DHCP requests occur. However, if you're getting RFC 1918 addresses, then something is providing them. PfSense can't do it on it's own.

                Having to debug two networks is more difficult than one.

                What you have to do is see what's happening, such as watching the DHCP process as I mentioned above. If you don't do things like that, to see what's working properly or not, then you won't get very far. And no, two networks is not an issue, if you know what you're doing. However, I agree we should move to IPv6 as soon as possible, though not for the reasons you are imagining.

                Incidentally, back in the late '90s, when I was at IBM, we had IP, NetBIOS and SNA all on the same Token Ring network. I don't recall there being any issues caused by having multiple protocols on the network. Also, back in those days, it was common for IP & IPX to share a network. Networks are designed to support multiple protocols at the same time and mixing them doesn't cause problems. You just have to understand what you have.

                PfSense running on Qotom mini PC
                i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
                UniFi AC-Lite access point

                I haven't lost my mind. It's around here...somewhere...

                N 1 Reply Last reply Reply Quote 0
                • N
                  netblues @JKnott
                  last edited by

                  @JKnott Yes, its quite possible to do everything at once, as you said, if you know what you are doing.
                  Mixing two or more networks doesn't cause problems per se. But clearly I can't see why it is a problem to debug dhcp issues one by one too if it makes the learning curve easier.

                  1 Reply Last reply Reply Quote 1
                  • johnpozJ
                    johnpoz LAYER 8 Global Moderator
                    last edited by johnpoz

                    Well with that I agree... Since IPv6 is a nice to have thing.. There is zero resources other than some p0rn or dark web sort of sites that are only available via IPv6.. There are million s if not billions of users that have no IPv6 - and they are fine ;)

                    So sure if the user is trying to troubleshoot dhcp issue, sure disable IPv6 until such point your IPv4 is stable and you want play with IPv6..

                    Off the top if user is getting rfc1918 sometimes... Could very well be issue when his isp goes offline and his modem hands out rfc1918 address, is it a 192.168.100.x address... This is very common default IP range for cable modems.

                    An intelligent man is sometimes forced to be drunk to spend time with his fools
                    If you get confused: Listen to the Music Play
                    Please don't Chat/PM me for help, unless mod related
                    SG-4860 24.11 | Lab VMs 2.8, 24.11

                    1 Reply Last reply Reply Quote 0
                    • L
                      lifespeed
                      last edited by lifespeed

                      Thanks all for your support. I apologize for the confusing presentation. NTP was problematic, but perhaps when pfSense receives proper external addresses this is not a problem.

                      Here is today's NTP log from the past few hours, I think it's fine. And the date and time are correct on pfSense. So let's say I don't have an NTP problem, but have been having a problem with erratic WAN addresses on pfSense bootup. I have had to reboot multiple times before somehow, mysteriously pfSense gets WAN addresses.

                      NTP logs - fine

                      May 25 13:25:06 	ntpd 	280 	206.55.191.142 14fa 8a sys_peer
May 25 12:59:33 	ntpd 	280 	45.63.54.13 142a 8a sys_peer
May 25 12:06:10 	ntpd 	280 	163.237.218.19 13fa 8a sys_peer
May 25 11:42:54 	ntpd 	280 	206.55.191.142 13ea 8a sys_peer
                      1 Reply Last reply Reply Quote 0
                      • L
                        lifespeed
                        last edited by lifespeed

                        pfSense was powered down, then started from a cold boot in order to demonstrate and try and troubleshoot the failed WAN address at startup issue. The Netgear CM1000 DOCSIS 3.1 modem was left on.

                        The usual IPv4 was displayed by pfSense, but no valid IPv6 was found. Internet access failed.

                        May 25 16:00:12 	php-fpm 	363 	/index.php: Successful login for user 'admin' from: 192.168.1.50 (Local Database)
May 25 15:57:55 	php-fpm 	364 	[pfBlockerNG] Starting cron process.
May 25 15:57:55 	php-fpm 	364 	/rc.start_packages: Restarting/Starting all packages.
May 25 15:57:55 	kernel 		done.
May 25 15:57:54 	kernel 		done.
May 25 15:57:54 	syslogd 		kernel boot file is /boot/kernel/kernel
May 25 15:57:54 	syslogd 		exiting on signal 15
May 25 15:57:54 	php-cgi 		rc.bootup: Creating rrd update script
May 25 15:57:53 	php-fpm 	363 	/rc.dyndns.update: Dynamic DNS (pfsense.mydomain.com) There was an error trying to determine the public IP for interface - wan (igb0 ).
May 25 15:57:53 	php-fpm 	363 	/rc.dyndns.update: Dynamic DNS (pfsense.mydomain.com): running get_failover_interface for wan. found igb0
May 25 15:57:53 	php-fpm 	363 	/rc.dyndns.update: Dynamic DNS: updatedns() starting
May 25 15:57:52 	php-fpm 	363 	/rc.dyndns.update: phpDynDNS (@.mydomain.com): No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry.
May 25 15:57:52 	php-fpm 	363 	/rc.dyndns.update: Dynamic Dns (@.mydomain.com): Current WAN IP: 76.126.xxx.xxx Cached IP: 76.126.xxx.xxx
May 25 15:57:52 	php-fpm 	363 	/rc.dyndns.update: Dynamic DNS godaddy (@.mydomain.com): 76.126.xxx.xxx extracted from local system.
May 25 15:57:52 	php-fpm 	363 	/rc.dyndns.update: Dynamic DNS (@.mydomain.com): running get_failover_interface for wan. found igb0
May 25 15:57:52 	php-fpm 	363 	/rc.dyndns.update: Dynamic DNS godaddy (@.mydomain.com): 76.126.xxx.xxx extracted from local system.
May 25 15:57:52 	php-fpm 	363 	/rc.dyndns.update: Dynamic DNS: updatedns() starting
May 25 15:57:52 	kernel 		done
May 25 15:57:52 	kernel 		.done.
May 25 15:57:51 	kernel 		..
May 25 15:57:51 	kernel 		..
May 25 15:57:51 	check_reload_status 		Updating all dyndns
May 25 15:57:51 	dhcpleases 		kqueue error: unknown
May 25 15:57:51 	kernel 		done.
May 25 15:57:51 	kernel 		done.
May 25 15:57:51 	php-cgi 		rc.bootup: NTPD is starting up.
May 25 15:57:51 	kernel 		done.
May 25 15:57:50 	kernel 		done.
May 25 15:57:50 	kernel 		done.
May 25 15:57:50 	dhcpleases 		Could not deliver signal HUP to process because its pidfile (/var/run/dnsmasq.pid) does not exist, No such file or directory.
May 25 15:57:50 	kernel 		done.
May 25 15:57:50 	php-cgi 		rc.bootup: Gateway, none 'available' for inet6, use the first one configured. 'WAN_DHCP6'
May 25 15:57:50 	php-cgi 		rc.bootup: Default gateway setting Interface WAN_DHCP Gateway as default.
May 25 15:57:49 	kernel 		.done.
May 25 15:57:49 	kernel 		..
May 25 15:57:49 	kernel 		pflog0: promiscuous mode enabled
May 25 15:57:49 	php-cgi 		rc.bootup: The command '/sbin/route delete -host 2620:fe::9' returned exit code '68', the output was 'route: bad address: 2620:fe::9'
May 25 15:57:25 	php-cgi 		rc.bootup: The command '/sbin/route delete -host 2620:fe::fe' returned exit code '68', the output was 'route: bad address: 2620:fe::fe'
May 25 15:57:01 	php-cgi 		rc.bootup: The command '/sbin/route delete -host 2606:4700:4700::1001' returned exit code '68', the output was 'route: bad address: 2606:4700:4700::1001'
May 25 15:56:38 	php-cgi 		rc.bootup: The command '/sbin/route delete -host 2606:4700:4700::1111' returned exit code '68', the output was 'route: bad address: 2606:4700:4700::1111'
May 25 15:56:14 	php-fpm 	364 	/rc.newwanip: The command '/sbin/route delete -host 2620:fe::9' returned exit code '68', the output was 'route: bad address: 2620:fe::9'
May 25 15:55:50 	php-fpm 	364 	/rc.newwanip: The command '/sbin/route delete -host 2620:fe::fe' returned exit code '68', the output was 'route: bad address: 2620:fe::fe'
May 25 15:55:27 	php-fpm 	364 	/rc.newwanip: The command '/sbin/route delete -host 2606:4700:4700::1001' returned exit code '68', the output was 'route: bad address: 2606:4700:4700::1001'
May 25 15:55:03 	php-fpm 	364 	/rc.newwanip: The command '/sbin/route delete -host 2606:4700:4700::1111' returned exit code '68', the output was 'route: bad address: 2606:4700:4700::1111'
May 25 15:54:42 	php-cgi 		rc.bootup: Resyncing OpenVPN instances.
May 25 15:54:42 	kernel 		ixl2: link state changed to UP
May 25 15:54:42 	kernel 		ixl2: Link is up, 10 Gbps Full Duplex, Requested FEC: None, Negotiated FEC: None, Autoneg: False, Flow Control: None
May 25 15:54:42 	check_reload_status 		Linkup starting ixl2
May 25 15:54:41 	php-cgi 		rc.bootup: Starting dhcp6 client for interface wan igb0 in DHCP6 without RA mode
May 25 15:54:39 	php-fpm 	364 	/rc.newwanip: rc.newwanip: on (IP address: 76.126.xxx.xxx) (interface: WAN[wan]) (real interface: igb0).
May 25 15:54:39 	php-fpm 	364 	/rc.newwanip: rc.newwanip: Info: starting on igb0.
May 25 15:54:38 	php-cgi 		rc.bootup: Accept router advertisements on interface igb0
May 25 15:54:38 	php-cgi 		rc.bootup: calling interface_dhcpv6_configure.
May 25 15:54:38 	check_reload_status 		rc.newwanip starting igb0
May 25 15:54:38 	kernel 		igb0: link state changed to UP
May 25 15:54:38 	check_reload_status 		Linkup starting igb0
May 25 15:54:35 	syslogd 		Logging subprocess 6021 (exec /usr/local/sbin/sshguard) exited due to signal 15.
May 25 15:54:35 	sshd 	5925 	Server listening on 0.0.0.0 port 22614.
May 25 15:54:35 	sshd 	5925 	Server listening on :: port 22614.
May 25 15:54:34 	kernel 		aesni0: <AES-CBC,AES-XTS,AES-GCM,AES-ICM> on motherboard
May 25 15:54:34 	kernel 		padlock0: No ACE support.
May 25 15:54:34 	kernel 		TSC: P-state invariant, performance statistics
May 25 15:54:34 	kernel 		VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID,VID,PostIntr
May 25 15:54:34 	kernel 		XSAVE Features=0xf<XSAVEOPT,XSAVEC,XINUSE,XSAVES>
May 25 15:54:34 	kernel 		Structured Extended Features3=0x9c002400<IBPB,STIBP,SSBD>
May 25 15:54:34 	kernel 		Structured Extended Features2=0x8<PKU>
May 25 15:54:34 	kernel 		Structured Extended Features=0xd39ffffb<FSGSBASE,TSCADJ,BMI1,HLE,AVX2,FDPEXC,SMEP,BMI2,ERMS,INVPCID,RTM,PQM,NFPUSG,MPX,PQE,AVX512F,AVX512DQ,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,PROCTRACE,AVX512CD,AVX512BW,AVX512VL>
May 25 15:54:34 	kernel 		AMD Features2=0x121<LAHF,ABM,Prefetch>
May 25 15:54:34 	kernel 		AMD Features=0x2c100800<SYSCALL,NX,Page1GB,RDTSCP,LM>
May 25 15:54:34 	kernel 		Features2=0x7ffefbff<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND>
May 25 15:54:34 	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>
May 25 15:54:34 	kernel 		Origin="GenuineIntel" Id=0x50654 Family=0x6 Model=0x55 Stepping=4
May 25 15:54:34 	kernel 		CPU: Intel(R) Xeon(R) D-2123IT CPU @ 2.20GHz (2194.90-MHz K8-class CPU)
May 25 15:54:34 	kernel 		random: unblocking device.
May 25 15:54:34 	kernel 		Trying to mount root from zfs:zroot/ROOT/default []...
May 25 15:54:34 	kernel 		ses0: SEMB SES Device
May 25 15:54:34 	kernel 		ses0: <AHCI SGPIO Enclosure 1.00 0001> SEMB S-E-S 2.00 device
May 25 15:54:34 	kernel 		ses0 at ahciem0 bus 0 scbus6 target 0 lun 0
May 25 15:54:34 	kernel 		uhub3: 4 ports with 4 removable, self powered
May 25 15:54:34 	kernel 		uhub3: MTT enabled
May 25 15:54:34 	kernel 		uhub3: <vendor 0x05e3 USB2.0 Hub, class 9/0, rev 2.00/32.98, addr 4> on usbus0
May 25 15:54:34 	kernel 		uhub3 numa-domain 0 on uhub2
May 25 15:54:34 	kernel 		ugen0.5: <vendor 0x05e3 USB2.0 Hub> at usbus0
May 25 15:54:34 	kernel 		uhub2: 4 ports with 4 removable, self powered
May 25 15:54:34 	kernel 		uhub2: MTT enabled
May 25 15:54:34 	kernel 		uhub2: <vendor 0x05e3 USB2.0 Hub, class 9/0, rev 2.00/32.98, addr 3> on usbus0
May 25 15:54:34 	kernel 		uhub2 numa-domain 0 on uhub0
May 25 15:54:34 	kernel 		ugen0.4: <vendor 0x05e3 USB2.0 Hub> at usbus0
May 25 15:54:34 	kernel 		kbd2 at ukbd0
May 25 15:54:34 	kernel 		ukbd0: <vendor 0x0557 product 0x2419, class 0/0, rev 1.10/1.00, addr 2> on usbus0
May 25 15:54:34 	kernel 		ukbd0 numa-domain 0 on uhub1
May 25 15:54:34 	kernel 		ugen0.3: <vendor 0x0557 product 0x2419> at usbus0
May 25 15:54:34 	kernel 		uhub1: 4 ports with 3 removable, self powered
May 25 15:54:34 	kernel 		uhub1: <vendor 0x0557 product 0x7000, class 9/0, rev 2.00/0.00, addr 1> on usbus0
May 25 15:54:34 	kernel 		uhub1 numa-domain 0 on uhub0
May 25 15:54:34 	kernel 		ugen0.2: <vendor 0x0557 product 0x7000> at usbus0
May 25 15:54:34 	kernel 		uhub0: 26 ports with 26 removable, self powered
May 25 15:54:34 	kernel 		nvd0: 476940MB (976773168 512 byte sectors)
May 25 15:54:34 	kernel 		nvd0: <Samsung SSD 970 EVO 500GB> NVMe namespace
May 25 15:54:34 	kernel 		uhub0: <0x8086 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0
May 25 15:54:34 	kernel 		ugen0.1: <0x8086 XHCI root HUB> at usbus0
May 25 15:54:34 	kernel 		Timecounters tick every 1.000 msec
May 25 15:54:34 	kernel 		ZFS storage pool version: features support (5000)
May 25 15:54:34 	kernel 		ZFS filesystem version: 5
May 25 15:54:34 	kernel 		est7: <Enhanced SpeedStep Frequency Control> numa-domain 0 on cpu7
May 25 15:54:34 	kernel 		est6: <Enhanced SpeedStep Frequency Control> numa-domain 0 on cpu6
May 25 15:54:34 	kernel 		est5: <Enhanced SpeedStep Frequency Control> numa-domain 0 on cpu5
May 25 15:54:34 	kernel 		est4: <Enhanced SpeedStep Frequency Control> numa-domain 0 on cpu4
May 25 15:54:34 	kernel 		est3: <Enhanced SpeedStep Frequency Control> numa-domain 0 on cpu3
May 25 15:54:34 	kernel 		est2: <Enhanced SpeedStep Frequency Control> numa-domain 0 on cpu2
May 25 15:54:34 	kernel 		est1: <Enhanced SpeedStep Frequency Control> numa-domain 0 on cpu1
May 25 15:54:34 	kernel 		est0: <Enhanced SpeedStep Frequency Control> numa-domain 0 on cpu0
May 25 15:54:34 	kernel 		ppc0: cannot reserve I/O port range
May 25 15:54:34 	kernel 		orm0: <ISA Option ROM> at iomem 0xc0000-0xc7fff on isa0
May 25 15:54:34 	kernel 		uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0
May 25 15:54:34 	kernel 		uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
May 25 15:54:34 	kernel 		pci9: <dasp, performance counters> at device 18.1 (no driver attached)
May 25 15:54:34 	kernel 		pci9: <dasp, performance counters> at device 18.0 (no driver attached)
May 25 15:54:34 	kernel 		ixl3: netmap queues/slots: TX 8/1024, RX 8/1024
May 25 15:54:34 	kernel 		queues is 0xfffffe0001902000
May 25 15:54:34 	kernel 		ixl3: SR-IOV ready
May 25 15:54:34 	kernel 		ixl3: Ethernet address: 00:25:90:bb:bf:0d
May 25 15:54:34 	kernel 		ixl3: Allocating 8 queues for PF LAN VSI; 8 queues active
May 25 15:54:34 	kernel 		ixl3: Using MSIX interrupts with 9 vectors
May 25 15:54:34 	kernel 		ixl3: PF-ID[3]: VFs 32, MSIX 129, VF MSIX 5, QPs 384, I2C
May 25 15:54:34 	kernel 		ixl3: fw 3.1.57069 api 1.5 nvm 3.33 etid 80001006 oem 1.262.0
May 25 15:54:34 	kernel 		ixl3: using 1024 tx descriptors and 1024 rx descriptors
May 25 15:54:34 	kernel 		ixl3: <Intel(R) Ethernet Connection 700 Series PF Driver, Version - 1.9.9-k> mem 0xf7000000-0xf7ffffff,0xfb000000-0xfb007fff irq 46 at device 0.3 numa-domain 0 on pci12
May 25 15:54:34 	kernel 		ixl2: netmap queues/slots: TX 8/1024, RX 8/1024
May 25 15:54:34 	kernel 		queues is 0xfffffe00017b4000
May 25 15:54:34 	kernel 		ixl2: SR-IOV ready
May 25 15:54:34 	kernel 		ixl2: Ethernet address: 00:25:90:bb:bf:0c
May 25 15:54:34 	kernel 		ixl2: Allocating 8 queues for PF LAN VSI; 8 queues active
May 25 15:54:34 	kernel 		ixl2: Using MSIX interrupts with 9 vectors
May 25 15:54:34 	kernel 		ixl2: PF-ID[2]: VFs 32, MSIX 129, VF MSIX 5, QPs 384, I2C
May 25 15:54:34 	kernel 		ixl2: fw 3.1.57069 api 1.5 nvm 3.33 etid 80001006 oem 1.262.0
May 25 15:54:34 	kernel 		ixl2: using 1024 tx descriptors and 1024 rx descriptors
May 25 15:54:34 	kernel 		ixl2: <Intel(R) Ethernet Connection 700 Series PF Driver, Version - 1.9.9-k> mem 0xf8000000-0xf8ffffff,0xfb008000-0xfb00ffff irq 46 at device 0.2 numa-domain 0 on pci12
May 25 15:54:34 	kernel 		ixl1: netmap queues/slots: TX 8/1024, RX 8/1024
May 25 15:54:34 	kernel 		queues is 0xfffffe0001678000
May 25 15:54:34 	kernel 		ixl1: SR-IOV ready
May 25 15:54:34 	kernel 		ixl1: Ethernet address: 00:25:90:bb:bf:0b
May 25 15:54:34 	kernel 		ixl1: Allocating 8 queues for PF LAN VSI; 8 queues active
May 25 15:54:34 	kernel 		ixl1: Using MSIX interrupts with 9 vectors
May 25 15:54:34 	kernel 		ixl1: PF-ID[1]: VFs 32, MSIX 129, VF MSIX 5, QPs 384, MDIO shared
May 25 15:54:34 	kernel 		ixl1: fw 3.1.57069 api 1.5 nvm 3.33 etid 80001006 oem 1.262.0
May 25 15:54:34 	kernel 		ixl1: using 1024 tx descriptors and 1024 rx descriptors
May 25 15:54:34 	kernel 		ixl1: <Intel(R) Ethernet Connection 700 Series PF Driver, Version - 1.9.9-k> mem 0xf9000000-0xf9ffffff,0xfb010000-0xfb017fff irq 46 at device 0.1 numa-domain 0 on pci12
May 25 15:54:34 	kernel 		ixl0: netmap queues/slots: TX 8/1024, RX 8/1024
May 25 15:54:34 	kernel 		queues is 0xfffffe000153c000
May 25 15:54:34 	kernel 		ixl0: SR-IOV ready
May 25 15:54:34 	kernel 		ixl0: Ethernet address: 00:25:90:bb:bf:0a
May 25 15:54:34 	kernel 		ixl0: Allocating 8 queues for PF LAN VSI; 8 queues active
May 25 15:54:34 	kernel 		ixl0: Using MSIX interrupts with 9 vectors
May 25 15:54:34 	kernel 		ixl0: PF-ID[0]: VFs 32, MSIX 129, VF MSIX 5, QPs 384, MDIO shared
May 25 15:54:34 	kernel 		ixl0: fw 3.1.57069 api 1.5 nvm 3.33 etid 80001006 oem 1.262.0
May 25 15:54:34 	kernel 		ixl0: using 1024 tx descriptors and 1024 rx descriptors
May 25 15:54:34 	kernel 		ixl0: <Intel(R) Ethernet Connection 700 Series PF Driver, Version - 1.9.9-k> mem 0xfa000000-0xfaffffff,0xfb018000-0xfb01ffff irq 46 at device 0.0 numa-domain 0 on pci12
May 25 15:54:34 	kernel 		pci12: <ACPI PCI bus> numa-domain 0 on pcib12
May 25 15:54:34 	kernel 		pcib12: <ACPI PCI-PCI bridge> irq 40 at device 3.0 numa-domain 0 on pci11
May 25 15:54:34 	kernel 		pci11: <ACPI PCI bus> numa-domain 0 on pcib11
May 25 15:54:34 	kernel 		pcib11: <ACPI PCI-PCI bridge> mem 0xfbe00000-0xfbe1ffff irq 48 at device 0.0 numa-domain 0 on pci10
May 25 15:54:34 	kernel 		pci10: <ACPI PCI bus> numa-domain 0 on pcib10
May 25 15:54:34 	kernel 		pcib10: <ACPI PCI-PCI bridge> irq 55 at device 0.0 numa-domain 0 on pci9
May 25 15:54:34 	kernel 		pci9: <ACPI PCI bus> numa-domain 0 on pcib9
May 25 15:54:34 	kernel 		pcib9: _OSC returned error 0x10
May 25 15:54:34 	kernel 		pcib9: <ACPI Host-PCI bridge> numa-domain 0 on acpi0
May 25 15:54:34 	kernel 		igb3: netmap queues/slots: TX 8/1024, RX 8/1024
May 25 15:54:34 	kernel 		igb3: Bound queue 7 to cpu 7
May 25 15:54:34 	kernel 		igb3: Bound queue 6 to cpu 6
May 25 15:54:34 	kernel 		igb3: Bound queue 5 to cpu 5
May 25 15:54:34 	kernel 		igb3: Bound queue 4 to cpu 4
May 25 15:54:34 	kernel 		igb3: Bound queue 3 to cpu 3
May 25 15:54:34 	kernel 		igb3: Bound queue 2 to cpu 2
May 25 15:54:34 	kernel 		igb3: Bound queue 1 to cpu 1
May 25 15:54:34 	kernel 		igb3: Bound queue 0 to cpu 0
May 25 15:54:34 	kernel 		igb3: Ethernet address: 00:25:90:ba:53:67
May 25 15:54:34 	kernel 		igb3: Using MSIX interrupts with 9 vectors
May 25 15:54:34 	kernel 		igb3: <Intel(R) PRO/1000 Network Connection, Version - 2.5.3-k> port 0xb000-0xb01f mem 0xe0d00000-0xe0d1ffff,0xe0d80000-0xe0d83fff irq 45 at device 0.3 numa-domain 0 on pci8
May 25 15:54:34 	kernel 		igb2: netmap queues/slots: TX 8/1024, RX 8/1024
May 25 15:54:34 	kernel 		igb2: Bound queue 7 to cpu 7
May 25 15:54:34 	kernel 		igb2: Bound queue 6 to cpu 6
May 25 15:54:34 	kernel 		igb2: Bound queue 5 to cpu 5
May 25 15:54:34 	kernel 		igb2: Bound queue 4 to cpu 4
May 25 15:54:34 	kernel 		igb2: Bound queue 3 to cpu 3
May 25 15:54:34 	kernel 		igb2: Bound queue 2 to cpu 2
May 25 15:54:34 	kernel 		igb2: Bound queue 1 to cpu 1
May 25 15:54:34 	kernel 		igb2: Bound queue 0 to cpu 0
May 25 15:54:34 	kernel 		igb2: Ethernet address: 00:25:90:ba:53:66
May 25 15:54:34 	kernel 		igb2: Using MSIX interrupts with 9 vectors
May 25 15:54:34 	kernel 		igb2: <Intel(R) PRO/1000 Network Connection, Version - 2.5.3-k> port 0xb020-0xb03f mem 0xe0d20000-0xe0d3ffff,0xe0d84000-0xe0d87fff irq 44 at device 0.2 numa-domain 0 on pci8
May 25 15:54:34 	kernel 		igb1: netmap queues/slots: TX 8/1024, RX 8/1024
May 25 15:54:34 	kernel 		igb1: Bound queue 7 to cpu 7
May 25 15:54:34 	kernel 		igb1: Bound queue 6 to cpu 6
May 25 15:54:34 	kernel 		igb1: Bound queue 5 to cpu 5
May 25 15:54:34 	kernel 		igb1: Bound queue 4 to cpu 4
May 25 15:54:34 	kernel 		igb1: Bound queue 3 to cpu 3
May 25 15:54:34 	kernel 		igb1: Bound queue 2 to cpu 2
May 25 15:54:34 	kernel 		igb1: Bound queue 1 to cpu 1
May 25 15:54:34 	kernel 		igb1: Bound queue 0 to cpu 0
May 25 15:54:34 	kernel 		igb1: Ethernet address: 00:25:90:ba:53:65
May 25 15:54:34 	kernel 		igb1: Using MSIX interrupts with 9 vectors
May 25 15:54:34 	kernel 		igb1: <Intel(R) PRO/1000 Network Connection, Version - 2.5.3-k> port 0xb040-0xb05f mem 0xe0d40000-0xe0d5ffff,0xe0d88000-0xe0d8bfff irq 46 at device 0.1 numa-domain 0 on pci8
May 25 15:54:34 	kernel 		igb0: netmap queues/slots: TX 8/1024, RX 8/1024
May 25 15:54:34 	kernel 		igb0: Bound queue 7 to cpu 7
May 25 15:54:34 	kernel 		igb0: Bound queue 6 to cpu 6
May 25 15:54:34 	kernel 		igb0: Bound queue 5 to cpu 5
May 25 15:54:34 	kernel 		igb0: Bound queue 4 to cpu 4
May 25 15:54:34 	kernel 		igb0: Bound queue 3 to cpu 3
May 25 15:54:34 	kernel 		igb0: Bound queue 2 to cpu 2
May 25 15:54:34 	kernel 		igb0: Bound queue 1 to cpu 1
May 25 15:54:34 	kernel 		igb0: Bound queue 0 to cpu 0
May 25 15:54:34 	kernel 		igb0: Ethernet address: 00:25:90:ba:53:64
May 25 15:54:34 	kernel 		igb0: Using MSIX interrupts with 9 vectors
May 25 15:54:34 	kernel 		igb0: <Intel(R) PRO/1000 Network Connection, Version - 2.5.3-k> port 0xb060-0xb07f mem 0xe0d60000-0xe0d7ffff,0xe0d8c000-0xe0d8ffff irq 43 at device 0.0 numa-domain 0 on pci8
May 25 15:54:34 	kernel 		pci8: <ACPI PCI bus> numa-domain 0 on pcib8
May 25 15:54:34 	kernel 		pcib8: <ACPI PCI-PCI bridge> irq 47 at device 3.0 numa-domain 0 on pci6
May 25 15:54:34 	kernel 		nvme0: <Generic NVMe Device> mem 0xe0e00000-0xe0e03fff irq 42 at device 0.0 numa-domain 0 on pci7
May 25 15:54:34 	kernel 		pci7: <ACPI PCI bus> numa-domain 0 on pcib7
May 25 15:54:34 	kernel 		pcib7: <ACPI PCI-PCI bridge> irq 47 at device 2.0 numa-domain 0 on pci6
May 25 15:54:34 	kernel 		pci6: <ACPI PCI bus> numa-domain 0 on pcib6
May 25 15:54:34 	kernel 		pcib6: _OSC returned error 0x10
May 25 15:54:34 	kernel 		pcib6: <ACPI Host-PCI bridge> numa-domain 0 on acpi0
May 25 15:54:34 	kernel 		pci5: <ACPI PCI bus> numa-domain 0 on pcib5
May 25 15:54:34 	kernel 		pcib5: _OSC returned error 0x10
May 25 15:54:34 	kernel 		pcib5: <ACPI Host-PCI bridge> numa-domain 0 on acpi0
May 25 15:54:34 	kernel 		pci0: <serial bus> at device 31.5 (no driver attached)
May 25 15:54:34 	kernel 		pci0: <memory> at device 31.2 (no driver attached)
May 25 15:54:34 	kernel 		isa0: <ISA bus> numa-domain 0 on isab0
May 25 15:54:34 	kernel 		isab0: <PCI-ISA bridge> at device 31.0 numa-domain 0 on pci0
May 25 15:54:34 	kernel 		pci4: <ACPI PCI bus> numa-domain 0 on pcib4
May 25 15:54:34 	kernel 		pcib4: <ACPI PCI-PCI bridge> irq 16 at device 29.0 numa-domain 0 on pci0
May 25 15:54:34 	kernel 		vgapci0: Boot video device
May 25 15:54:34 	kernel 		vgapci0: <VGA-compatible display> port 0x2000-0x207f mem 0xa9000000-0xa9ffffff,0xaa000000-0xaa01ffff irq 16 at device 0.0 numa-domain 0 on pci3
May 25 15:54:34 	kernel 		pci3: <ACPI PCI bus> numa-domain 0 on pcib3
May 25 15:54:34 	kernel 		pcib3: <ACPI PCI-PCI bridge> irq 16 at device 0.0 numa-domain 0 on pci2
May 25 15:54:34 	kernel 		pci2: <ACPI PCI bus> numa-domain 0 on pcib2
May 25 15:54:34 	kernel 		pcib2: <ACPI PCI-PCI bridge> irq 16 at device 28.4 numa-domain 0 on pci0
May 25 15:54:34 	kernel 		pci1: <ACPI PCI bus> numa-domain 0 on pcib1
May 25 15:54:34 	kernel 		pcib1: <ACPI PCI-PCI bridge> irq 16 at device 28.0 numa-domain 0 on pci0
May 25 15:54:34 	kernel 		pci0: <simple comms> at device 22.4 (no driver attached)
May 25 15:54:34 	kernel 		pci0: <simple comms> at device 22.1 (no driver attached)
May 25 15:54:34 	kernel 		pci0: <simple comms> at device 22.0 (no driver attached)
May 25 15:54:34 	kernel 		usbus0: 5.0Gbps Super Speed USB v3.0
May 25 15:54:34 	kernel 		usbus0 numa-domain 0 on xhci0
May 25 15:54:34 	kernel 		xhci_interrupt: host controller halted
May 25 15:54:34 	kernel 		usbus0: waiting for BIOS to give up control
May 25 15:54:34 	kernel 		xhci0: 32 bytes context size, 64-bit DMA
May 25 15:54:34 	kernel 		xhci0: <Intel Lewisburg USB 3.0 controller> mem 0xaa180000-0xaa18ffff irq 16 at device 20.0 numa-domain 0 on pci0
May 25 15:54:34 	kernel 		ahciem0: <AHCI enclosure management bridge> on ahci0
May 25 15:54:34 	kernel 		ahcich5: <AHCI channel> at channel 5 on ahci0
May 25 15:54:34 	kernel 		ahcich4: <AHCI channel> at channel 4 on ahci0
May 25 15:54:34 	kernel 		ahcich3: <AHCI channel> at channel 3 on ahci0
May 25 15:54:34 	kernel 		ahcich2: <AHCI channel> at channel 2 on ahci0
May 25 15:54:34 	kernel 		ahcich1: <AHCI channel> at channel 1 on ahci0
May 25 15:54:34 	kernel 		ahcich0: <AHCI channel> at channel 0 on ahci0
May 25 15:54:34 	kernel 		ahci0: AHCI v1.31 with 6 6Gbps ports, Port Multiplier not supported
May 25 15:54:34 	kernel 		ahci0: <Intel Lewisburg AHCI SATA controller> port 0x3030-0x3037,0x3020-0x3023,0x3000-0x301f mem 0xaa194000-0xaa195fff,0xaa196000-0xaa1960ff,0xaa100000-0xaa17ffff irq 16 at device 17.5 numa-domain 0 on pci0
May 25 15:54:34 	kernel 		pci0: <unknown> at device 17.1 (no driver attached)
May 25 15:54:34 	kernel 		pci0: <unknown> at device 17.0 (no driver attached)
May 25 15:54:34 	kernel 		pci0: <dasp, performance counters> at device 8.1 (no driver attached)
May 25 15:54:34 	kernel 		pci0: <ACPI PCI bus> numa-domain 0 on pcib0
May 25 15:54:34 	kernel 		pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff numa-domain 0 on acpi0
May 25 15:54:34 	kernel 		acpi_syscontainer0: <System Container> on acpi0
May 25 15:54:34 	kernel 		acpi_timer0: <24-bit timer at 3.579545MHz> port 0x508-0x50b on acpi0
May 25 15:54:34 	kernel 		Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
May 25 15:54:34 	kernel 		device_attach: hpet1 attach returned 12
May 25 15:54:34 	kernel 		hpet1: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
May 25 15:54:34 	kernel 		Event timer "HPET" frequency 24000000 Hz quality 550
May 25 15:54:34 	kernel 		Timecounter "HPET" frequency 24000000 Hz quality 950
May 25 15:54:34 	kernel 		hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
May 25 15:54:34 	kernel 		Event timer "i8254" frequency 1193182 Hz quality 100
May 25 15:54:34 	kernel 		Timecounter "i8254" frequency 1193182 Hz quality 0
May 25 15:54:34 	kernel 		attimer0: <AT timer> port 0x40-0x43,0x50-0x53 irq 0 on acpi0
May 25 15:54:34 	kernel 		Event timer "RTC" frequency 32768 Hz quality 0
May 25 15:54:34 	kernel 		atrtc0: registered as a time-of-day clock, resolution 1.000000s
May 25 15:54:34 	kernel 		atrtc0: <AT realtime clock> port 0x70-0x71,0x74-0x77 irq 8 on acpi0
May 25 15:54:34 	kernel 		cpu7: <ACPI CPU> numa-domain 0 on acpi0
May 25 15:54:34 	kernel 		cpu6: <ACPI CPU> numa-domain 0 on acpi0
May 25 15:54:34 	kernel 		cpu5: <ACPI CPU> numa-domain 0 on acpi0
May 25 15:54:34 	kernel 		cpu4: <ACPI CPU> numa-domain 0 on acpi0
May 25 15:54:34 	kernel 		cpu3: <ACPI CPU> numa-domain 0 on acpi0
May 25 15:54:34 	kernel 		cpu2: <ACPI CPU> numa-domain 0 on acpi0
May 25 15:54:34 	kernel 		cpu1: <ACPI CPU> numa-domain 0 on acpi0
May 25 15:54:34 	kernel 		cpu0: <ACPI CPU> numa-domain 0 on acpi0
May 25 15:54:34 	kernel 		acpi0: Power Button (fixed)
May 25 15:54:34 	kernel 		acpi0: <SUPERM SUPERM> on motherboard
May 25 15:54:34 	kernel 		padlock0: No ACE support.
May 25 15:54:34 	kernel 		cryptosoft0: <software crypto> on motherboard
May 25 15:54:34 	kernel 		nexus0
May 25 15:54:34 	kernel 		random: fast provider: "Intel Secure Key RNG"
May 25 15:54:34 	kernel 		random: registering fast source Intel Secure Key RNG
May 25 15:54:34 	kernel 		module_register_init: MOD_LOAD (vesa, 0xffffffff8120aaa0, 0) error 19
May 25 15:54:34 	kernel 		netmap: loaded module
May 25 15:54:34 	kernel 		kbd1 at kbdmux0
May 25 15:54:34 	kernel 		wlan: mac acl policy registered
May 25 15:54:34 	kernel 		module_register_init: MOD_LOAD (iwi_monitor_fw, 0xffffffff806a85c0, 0) error 1
May 25 15:54:34 	kernel 		iwi_monitor: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
May 25 15:54:34 	kernel 		iwi_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi.LICENSE.
May 25 15:54:34 	kernel 		module_register_init: MOD_LOAD (iwi_ibss_fw, 0xffffffff806a8510, 0) error 1
May 25 15:54:34 	kernel 		iwi_ibss: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
May 25 15:54:34 	kernel 		iwi_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi.LICENSE.
May 25 15:54:34 	kernel 		module_register_init: MOD_LOAD (iwi_bss_fw, 0xffffffff806a8460, 0) error 1
May 25 15:54:34 	kernel 		iwi_bss: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
May 25 15:54:34 	kernel 		iwi_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi.LICENSE.
May 25 15:54:34 	kernel 		module_register_init: MOD_LOAD (ipw_monitor_fw, 0xffffffff80681590, 0) error 1
May 25 15:54:34 	kernel 		ipw_monitor: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
May 25 15:54:34 	kernel 		ipw_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw.LICENSE.
May 25 15:54:34 	kernel 		module_register_init: MOD_LOAD (ipw_ibss_fw, 0xffffffff806814e0, 0) error 1
May 25 15:54:34 	kernel 		ipw_ibss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
May 25 15:54:34 	kernel 		ipw_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw.LICENSE.
May 25 15:54:34 	kernel 		random: entropy device external interface
May 25 15:54:34 	kernel 		module_register_init: MOD_LOAD (ipw_bss_fw, 0xffffffff80681430, 0) error 1
May 25 15:54:34 	kernel 		ipw_bss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
May 25 15:54:34 	kernel 		ipw_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw.LICENSE.
May 25 15:54:34 	kernel 		Timecounter "TSC-low" frequency 1097452199 Hz quality 1000
May 25 15:54:34 	kernel 		SMP: AP CPU #3 Launched!
May 25 15:54:34 	kernel 		SMP: AP CPU #7 Launched!
May 25 15:54:34 	kernel 		SMP: AP CPU #5 Launched!
May 25 15:54:34 	kernel 		SMP: AP CPU #2 Launched!
May 25 15:54:34 	kernel 		SMP: AP CPU #4 Launched!
May 25 15:54:34 	kernel 		SMP: AP CPU #6 Launched!
May 25 15:54:34 	kernel 		SMP: AP CPU #1 Launched!
May 25 15:54:34 	kernel 		ioapic4 <Version 2.0> irqs 48-55 on motherboard
May 25 15:54:34 	kernel 		ioapic3 <Version 2.0> irqs 40-47 on motherboard
May 25 15:54:34 	kernel 		ioapic2 <Version 2.0> irqs 32-39 on motherboard
May 25 15:54:34 	kernel 		ioapic1 <Version 2.0> irqs 24-31 on motherboard
May 25 15:54:34 	kernel 		ioapic0 <Version 2.0> irqs 0-23 on motherboard
May 25 15:54:34 	kernel 		FreeBSD/SMP: 1 package(s) x 4 core(s) x 2 hardware threads
May 25 15:54:34 	kernel 		FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs
May 25 15:54:34 	kernel 		ACPI APIC Table: <SUPERM SMCI--MB>
May 25 15:54:34 	kernel 		Event timer "LAPIC" quality 600
May 25 15:54:34 	kernel 		avail memory = 32890949632 (31367 MB)
May 25 15:54:34 	kernel 		real memory = 34359738368 (32768 MB)
May 25 15:54:34 	kernel 		TSC: P-state invariant, performance statistics
May 25 15:54:34 	kernel 		VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID,VID,PostIntr
May 25 15:54:34 	kernel 		XSAVE Features=0xf<XSAVEOPT,XSAVEC,XINUSE,XSAVES>
May 25 15:54:34 	kernel 		Structured Extended Features3=0x9c002400<IBPB,STIBP,SSBD>
May 25 15:54:34 	kernel 		Structured Extended Features2=0x8<PKU>
May 25 15:54:34 	kernel 		Structured Extended Features=0xd39ffffb<FSGSBASE,TSCADJ,BMI1,HLE,AVX2,FDPEXC,SMEP,BMI2,ERMS,INVPCID,RTM,PQM,NFPUSG,MPX,PQE,AVX512F,AVX512DQ,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,PROCTRACE,AVX512CD,AVX512BW,AVX512VL>
May 25 15:54:34 	kernel 		AMD Features2=0x121<LAHF,ABM,Prefetch>
May 25 15:54:34 	kernel 		AMD Features=0x2c100800<SYSCALL,NX,Page1GB,RDTSCP,LM>
May 25 15:54:34 	kernel 		Features2=0x7ffefbff<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND>
May 25 15:54:34 	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>
May 25 15:54:34 	kernel 		Origin="GenuineIntel" Id=0x50654 Family=0x6 Model=0x55 Stepping=4
May 25 15:54:34 	kernel 		CPU: Intel(R) Xeon(R) D-2123IT CPU @ 2.20GHz (2194.90-MHz K8-class CPU)
May 25 15:54:34 	kernel 		VT(efifb): resolution 1024x768
May 25 15:54:34 	kernel 		FreeBSD clang version 6.0.0 (tags/RELEASE_600/final 326565) (based on LLVM 6.0.0)
May 25 15:54:34 	kernel 		root@buildbot1-nyi.netgate.com:/build/ce-crossbuild-244/obj/amd64/ZfGpH5cd/build/ce-crossbuild-244/pfSense/tmp/FreeBSD-src/sys/pfSense amd64
May 25 15:54:34 	kernel 		FreeBSD 11.2-RELEASE-p10 #9 4a2bfdce133(RELENG_2_4_4): Wed May 15 18:54:42 EDT 2019
May 25 15:54:34 	kernel 		FreeBSD is a registered trademark of The FreeBSD Foundation.
May 25 15:54:34 	kernel 		The Regents of the University of California. All rights reserved.
May 25 15:54:34 	kernel 		Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
May 25 15:54:34 	kernel 		Copyright (c) 1992-2018 The FreeBSD Project.
May 25 15:54:34 	syslogd 		kernel boot file is /boot/kernel/kernel
May 25 15:50:59 	syslogd 		exiting on signal 15
May 25 15:50:59 	shutdown 		power-down by admin:
                        1 Reply Last reply Reply Quote 0
                        • L
                          lifespeed
                          last edited by

                          Then pfSense was restarted, no powerdown. I don't know that restart vs. power down makes a difference. For whatever reason, it sometimes appears as though the second reboot is the charm, but not always. Whatever is failing, I would like to get to the root of the problem.

                          Here is a successful reboot, with IPv4 and IPv6 valid, as well as internet access. Also, I don't know if this is significant but my external WAN is:
                          2001:558:6045:45:xxxx:xxxx:xxxx:xxx8

                          While pfSense on the LAN is:
                          2601:646:8c00:xxxx:xxxx:xxxx:xxxx:xxxc

                          Are there any clues where to look from this second, successful reboot?

                          May 25 16:00:12 	php-fpm 	363 	/index.php: Successful login for user 'admin' from: 192.168.1.50 (Local Database)
May 25 15:57:55 	php-fpm 	364 	[pfBlockerNG] Starting cron process.
May 25 15:57:55 	php-fpm 	364 	/rc.start_packages: Restarting/Starting all packages.
May 25 15:57:55 	kernel 		done.
May 25 15:57:54 	kernel 		done.
May 25 15:57:54 	syslogd 		kernel boot file is /boot/kernel/kernel
May 25 15:57:54 	syslogd 		exiting on signal 15
May 25 15:57:54 	php-cgi 		rc.bootup: Creating rrd update script
May 25 15:57:53 	php-fpm 	363 	/rc.dyndns.update: Dynamic DNS (pfsense.mydomain.com) There was an error trying to determine the public IP for interface - wan (igb0 ).
May 25 15:57:53 	php-fpm 	363 	/rc.dyndns.update: Dynamic DNS (pfsense.mydomain.com): running get_failover_interface for wan. found igb0
May 25 15:57:53 	php-fpm 	363 	/rc.dyndns.update: Dynamic DNS: updatedns() starting
May 25 15:57:52 	php-fpm 	363 	/rc.dyndns.update: phpDynDNS (@.mydomain.com): No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry.
May 25 15:57:52 	php-fpm 	363 	/rc.dyndns.update: Dynamic Dns (@.mydomain.com): Current WAN IP: 76.126.xxx.xxx Cached IP: 76.126.xxx.xxx
May 25 15:57:52 	php-fpm 	363 	/rc.dyndns.update: Dynamic DNS godaddy (@.mydomain.com): 76.126.xxx.xxx extracted from local system.
May 25 15:57:52 	php-fpm 	363 	/rc.dyndns.update: Dynamic DNS (@.mydomain.com): running get_failover_interface for wan. found igb0
May 25 15:57:52 	php-fpm 	363 	/rc.dyndns.update: Dynamic DNS godaddy (@.mydomain.com): 76.126.xxx.xxx extracted from local system.
May 25 15:57:52 	php-fpm 	363 	/rc.dyndns.update: Dynamic DNS: updatedns() starting
May 25 15:57:52 	kernel 		done
May 25 15:57:52 	kernel 		.done.
May 25 15:57:51 	kernel 		..
May 25 15:57:51 	kernel 		..
May 25 15:57:51 	check_reload_status 		Updating all dyndns
May 25 15:57:51 	dhcpleases 		kqueue error: unknown
May 25 15:57:51 	kernel 		done.
May 25 15:57:51 	kernel 		done.
May 25 15:57:51 	php-cgi 		rc.bootup: NTPD is starting up.
May 25 15:57:51 	kernel 		done.
May 25 15:57:50 	kernel 		done.
May 25 15:57:50 	kernel 		done.
May 25 15:57:50 	dhcpleases 		Could not deliver signal HUP to process because its pidfile (/var/run/dnsmasq.pid) does not exist, No such file or directory.
May 25 15:57:50 	kernel 		done.
May 25 15:57:50 	php-cgi 		rc.bootup: Gateway, none 'available' for inet6, use the first one configured. 'WAN_DHCP6'
May 25 15:57:50 	php-cgi 		rc.bootup: Default gateway setting Interface WAN_DHCP Gateway as default.
May 25 15:57:49 	kernel 		.done.
May 25 15:57:49 	kernel 		..
May 25 15:57:49 	kernel 		pflog0: promiscuous mode enabled
May 25 15:57:49 	php-cgi 		rc.bootup: The command '/sbin/route delete -host 2620:fe::9' returned exit code '68', the output was 'route: bad address: 2620:fe::9'
May 25 15:57:25 	php-cgi 		rc.bootup: The command '/sbin/route delete -host 2620:fe::fe' returned exit code '68', the output was 'route: bad address: 2620:fe::fe'
May 25 15:57:01 	php-cgi 		rc.bootup: The command '/sbin/route delete -host 2606:4700:4700::1001' returned exit code '68', the output was 'route: bad address: 2606:4700:4700::1001'
May 25 15:56:38 	php-cgi 		rc.bootup: The command '/sbin/route delete -host 2606:4700:4700::1111' returned exit code '68', the output was 'route: bad address: 2606:4700:4700::1111'
May 25 15:56:14 	php-fpm 	364 	/rc.newwanip: The command '/sbin/route delete -host 2620:fe::9' returned exit code '68', the output was 'route: bad address: 2620:fe::9'
May 25 15:55:50 	php-fpm 	364 	/rc.newwanip: The command '/sbin/route delete -host 2620:fe::fe' returned exit code '68', the output was 'route: bad address: 2620:fe::fe'
May 25 15:55:27 	php-fpm 	364 	/rc.newwanip: The command '/sbin/route delete -host 2606:4700:4700::1001' returned exit code '68', the output was 'route: bad address: 2606:4700:4700::1001'
May 25 15:55:03 	php-fpm 	364 	/rc.newwanip: The command '/sbin/route delete -host 2606:4700:4700::1111' returned exit code '68', the output was 'route: bad address: 2606:4700:4700::1111'
May 25 15:54:42 	php-cgi 		rc.bootup: Resyncing OpenVPN instances.
May 25 15:54:42 	kernel 		ixl2: link state changed to UP
May 25 15:54:42 	kernel 		ixl2: Link is up, 10 Gbps Full Duplex, Requested FEC: None, Negotiated FEC: None, Autoneg: False, Flow Control: None
May 25 15:54:42 	check_reload_status 		Linkup starting ixl2
May 25 15:54:41 	php-cgi 		rc.bootup: Starting dhcp6 client for interface wan igb0 in DHCP6 without RA mode
May 25 15:54:39 	php-fpm 	364 	/rc.newwanip: rc.newwanip: on (IP address: 76.126.xxx.xxx) (interface: WAN[wan]) (real interface: igb0).
May 25 15:54:39 	php-fpm 	364 	/rc.newwanip: rc.newwanip: Info: starting on igb0.
May 25 15:54:38 	php-cgi 		rc.bootup: Accept router advertisements on interface igb0
May 25 15:54:38 	php-cgi 		rc.bootup: calling interface_dhcpv6_configure.
May 25 15:54:38 	check_reload_status 		rc.newwanip starting igb0
May 25 15:54:38 	kernel 		igb0: link state changed to UP
May 25 15:54:38 	check_reload_status 		Linkup starting igb0
May 25 15:54:35 	syslogd 		Logging subprocess 6021 (exec /usr/local/sbin/sshguard) exited due to signal 15.
May 25 15:54:35 	sshd 	5925 	Server listening on 0.0.0.0 port 22614.
May 25 15:54:35 	sshd 	5925 	Server listening on :: port 22614.
May 25 15:54:34 	kernel 		aesni0: <AES-CBC,AES-XTS,AES-GCM,AES-ICM> on motherboard
May 25 15:54:34 	kernel 		padlock0: No ACE support.
May 25 15:54:34 	kernel 		TSC: P-state invariant, performance statistics
May 25 15:54:34 	kernel 		VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID,VID,PostIntr
May 25 15:54:34 	kernel 		XSAVE Features=0xf<XSAVEOPT,XSAVEC,XINUSE,XSAVES>
May 25 15:54:34 	kernel 		Structured Extended Features3=0x9c002400<IBPB,STIBP,SSBD>
May 25 15:54:34 	kernel 		Structured Extended Features2=0x8<PKU>
May 25 15:54:34 	kernel 		Structured Extended Features=0xd39ffffb<FSGSBASE,TSCADJ,BMI1,HLE,AVX2,FDPEXC,SMEP,BMI2,ERMS,INVPCID,RTM,PQM,NFPUSG,MPX,PQE,AVX512F,AVX512DQ,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,PROCTRACE,AVX512CD,AVX512BW,AVX512VL>
May 25 15:54:34 	kernel 		AMD Features2=0x121<LAHF,ABM,Prefetch>
May 25 15:54:34 	kernel 		AMD Features=0x2c100800<SYSCALL,NX,Page1GB,RDTSCP,LM>
May 25 15:54:34 	kernel 		Features2=0x7ffefbff<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND>
May 25 15:54:34 	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>
May 25 15:54:34 	kernel 		Origin="GenuineIntel" Id=0x50654 Family=0x6 Model=0x55 Stepping=4
May 25 15:54:34 	kernel 		CPU: Intel(R) Xeon(R) D-2123IT CPU @ 2.20GHz (2194.90-MHz K8-class CPU)
May 25 15:54:34 	kernel 		random: unblocking device.
May 25 15:54:34 	kernel 		Trying to mount root from zfs:zroot/ROOT/default []...
May 25 15:54:34 	kernel 		ses0: SEMB SES Device
May 25 15:54:34 	kernel 		ses0: <AHCI SGPIO Enclosure 1.00 0001> SEMB S-E-S 2.00 device
May 25 15:54:34 	kernel 		ses0 at ahciem0 bus 0 scbus6 target 0 lun 0
May 25 15:54:34 	kernel 		uhub3: 4 ports with 4 removable, self powered
May 25 15:54:34 	kernel 		uhub3: MTT enabled
May 25 15:54:34 	kernel 		uhub3: <vendor 0x05e3 USB2.0 Hub, class 9/0, rev 2.00/32.98, addr 4> on usbus0
May 25 15:54:34 	kernel 		uhub3 numa-domain 0 on uhub2
May 25 15:54:34 	kernel 		ugen0.5: <vendor 0x05e3 USB2.0 Hub> at usbus0
May 25 15:54:34 	kernel 		uhub2: 4 ports with 4 removable, self powered
May 25 15:54:34 	kernel 		uhub2: MTT enabled
May 25 15:54:34 	kernel 		uhub2: <vendor 0x05e3 USB2.0 Hub, class 9/0, rev 2.00/32.98, addr 3> on usbus0
May 25 15:54:34 	kernel 		uhub2 numa-domain 0 on uhub0
May 25 15:54:34 	kernel 		ugen0.4: <vendor 0x05e3 USB2.0 Hub> at usbus0
May 25 15:54:34 	kernel 		kbd2 at ukbd0
May 25 15:54:34 	kernel 		ukbd0: <vendor 0x0557 product 0x2419, class 0/0, rev 1.10/1.00, addr 2> on usbus0
May 25 15:54:34 	kernel 		ukbd0 numa-domain 0 on uhub1
May 25 15:54:34 	kernel 		ugen0.3: <vendor 0x0557 product 0x2419> at usbus0
May 25 15:54:34 	kernel 		uhub1: 4 ports with 3 removable, self powered
May 25 15:54:34 	kernel 		uhub1: <vendor 0x0557 product 0x7000, class 9/0, rev 2.00/0.00, addr 1> on usbus0
May 25 15:54:34 	kernel 		uhub1 numa-domain 0 on uhub0
May 25 15:54:34 	kernel 		ugen0.2: <vendor 0x0557 product 0x7000> at usbus0
May 25 15:54:34 	kernel 		uhub0: 26 ports with 26 removable, self powered
May 25 15:54:34 	kernel 		nvd0: 476940MB (976773168 512 byte sectors)
May 25 15:54:34 	kernel 		nvd0: <Samsung SSD 970 EVO 500GB> NVMe namespace
May 25 15:54:34 	kernel 		uhub0: <0x8086 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0
May 25 15:54:34 	kernel 		ugen0.1: <0x8086 XHCI root HUB> at usbus0
May 25 15:54:34 	kernel 		Timecounters tick every 1.000 msec
May 25 15:54:34 	kernel 		ZFS storage pool version: features support (5000)
May 25 15:54:34 	kernel 		ZFS filesystem version: 5
May 25 15:54:34 	kernel 		est7: <Enhanced SpeedStep Frequency Control> numa-domain 0 on cpu7
May 25 15:54:34 	kernel 		est6: <Enhanced SpeedStep Frequency Control> numa-domain 0 on cpu6
May 25 15:54:34 	kernel 		est5: <Enhanced SpeedStep Frequency Control> numa-domain 0 on cpu5
May 25 15:54:34 	kernel 		est4: <Enhanced SpeedStep Frequency Control> numa-domain 0 on cpu4
May 25 15:54:34 	kernel 		est3: <Enhanced SpeedStep Frequency Control> numa-domain 0 on cpu3
May 25 15:54:34 	kernel 		est2: <Enhanced SpeedStep Frequency Control> numa-domain 0 on cpu2
May 25 15:54:34 	kernel 		est1: <Enhanced SpeedStep Frequency Control> numa-domain 0 on cpu1
May 25 15:54:34 	kernel 		est0: <Enhanced SpeedStep Frequency Control> numa-domain 0 on cpu0
May 25 15:54:34 	kernel 		ppc0: cannot reserve I/O port range
May 25 15:54:34 	kernel 		orm0: <ISA Option ROM> at iomem 0xc0000-0xc7fff on isa0
May 25 15:54:34 	kernel 		uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0
May 25 15:54:34 	kernel 		uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
May 25 15:54:34 	kernel 		pci9: <dasp, performance counters> at device 18.1 (no driver attached)
May 25 15:54:34 	kernel 		pci9: <dasp, performance counters> at device 18.0 (no driver attached)
May 25 15:54:34 	kernel 		ixl3: netmap queues/slots: TX 8/1024, RX 8/1024
May 25 15:54:34 	kernel 		queues is 0xfffffe0001902000
May 25 15:54:34 	kernel 		ixl3: SR-IOV ready
May 25 15:54:34 	kernel 		ixl3: Ethernet address: 00:25:90:bb:bf:0d
May 25 15:54:34 	kernel 		ixl3: Allocating 8 queues for PF LAN VSI; 8 queues active
May 25 15:54:34 	kernel 		ixl3: Using MSIX interrupts with 9 vectors
May 25 15:54:34 	kernel 		ixl3: PF-ID[3]: VFs 32, MSIX 129, VF MSIX 5, QPs 384, I2C
May 25 15:54:34 	kernel 		ixl3: fw 3.1.57069 api 1.5 nvm 3.33 etid 80001006 oem 1.262.0
May 25 15:54:34 	kernel 		ixl3: using 1024 tx descriptors and 1024 rx descriptors
May 25 15:54:34 	kernel 		ixl3: <Intel(R) Ethernet Connection 700 Series PF Driver, Version - 1.9.9-k> mem 0xf7000000-0xf7ffffff,0xfb000000-0xfb007fff irq 46 at device 0.3 numa-domain 0 on pci12
May 25 15:54:34 	kernel 		ixl2: netmap queues/slots: TX 8/1024, RX 8/1024
May 25 15:54:34 	kernel 		queues is 0xfffffe00017b4000
May 25 15:54:34 	kernel 		ixl2: SR-IOV ready
May 25 15:54:34 	kernel 		ixl2: Ethernet address: 00:25:90:bb:bf:0c
May 25 15:54:34 	kernel 		ixl2: Allocating 8 queues for PF LAN VSI; 8 queues active
May 25 15:54:34 	kernel 		ixl2: Using MSIX interrupts with 9 vectors
May 25 15:54:34 	kernel 		ixl2: PF-ID[2]: VFs 32, MSIX 129, VF MSIX 5, QPs 384, I2C
May 25 15:54:34 	kernel 		ixl2: fw 3.1.57069 api 1.5 nvm 3.33 etid 80001006 oem 1.262.0
May 25 15:54:34 	kernel 		ixl2: using 1024 tx descriptors and 1024 rx descriptors
May 25 15:54:34 	kernel 		ixl2: <Intel(R) Ethernet Connection 700 Series PF Driver, Version - 1.9.9-k> mem 0xf8000000-0xf8ffffff,0xfb008000-0xfb00ffff irq 46 at device 0.2 numa-domain 0 on pci12
May 25 15:54:34 	kernel 		ixl1: netmap queues/slots: TX 8/1024, RX 8/1024
May 25 15:54:34 	kernel 		queues is 0xfffffe0001678000
May 25 15:54:34 	kernel 		ixl1: SR-IOV ready
May 25 15:54:34 	kernel 		ixl1: Ethernet address: 00:25:90:bb:bf:0b
May 25 15:54:34 	kernel 		ixl1: Allocating 8 queues for PF LAN VSI; 8 queues active
May 25 15:54:34 	kernel 		ixl1: Using MSIX interrupts with 9 vectors
May 25 15:54:34 	kernel 		ixl1: PF-ID[1]: VFs 32, MSIX 129, VF MSIX 5, QPs 384, MDIO shared
May 25 15:54:34 	kernel 		ixl1: fw 3.1.57069 api 1.5 nvm 3.33 etid 80001006 oem 1.262.0
May 25 15:54:34 	kernel 		ixl1: using 1024 tx descriptors and 1024 rx descriptors
May 25 15:54:34 	kernel 		ixl1: <Intel(R) Ethernet Connection 700 Series PF Driver, Version - 1.9.9-k> mem 0xf9000000-0xf9ffffff,0xfb010000-0xfb017fff irq 46 at device 0.1 numa-domain 0 on pci12
May 25 15:54:34 	kernel 		ixl0: netmap queues/slots: TX 8/1024, RX 8/1024
May 25 15:54:34 	kernel 		queues is 0xfffffe000153c000
May 25 15:54:34 	kernel 		ixl0: SR-IOV ready
May 25 15:54:34 	kernel 		ixl0: Ethernet address: 00:25:90:bb:bf:0a
May 25 15:54:34 	kernel 		ixl0: Allocating 8 queues for PF LAN VSI; 8 queues active
May 25 15:54:34 	kernel 		ixl0: Using MSIX interrupts with 9 vectors
May 25 15:54:34 	kernel 		ixl0: PF-ID[0]: VFs 32, MSIX 129, VF MSIX 5, QPs 384, MDIO shared
May 25 15:54:34 	kernel 		ixl0: fw 3.1.57069 api 1.5 nvm 3.33 etid 80001006 oem 1.262.0
May 25 15:54:34 	kernel 		ixl0: using 1024 tx descriptors and 1024 rx descriptors
May 25 15:54:34 	kernel 		ixl0: <Intel(R) Ethernet Connection 700 Series PF Driver, Version - 1.9.9-k> mem 0xfa000000-0xfaffffff,0xfb018000-0xfb01ffff irq 46 at device 0.0 numa-domain 0 on pci12
May 25 15:54:34 	kernel 		pci12: <ACPI PCI bus> numa-domain 0 on pcib12
May 25 15:54:34 	kernel 		pcib12: <ACPI PCI-PCI bridge> irq 40 at device 3.0 numa-domain 0 on pci11
May 25 15:54:34 	kernel 		pci11: <ACPI PCI bus> numa-domain 0 on pcib11
May 25 15:54:34 	kernel 		pcib11: <ACPI PCI-PCI bridge> mem 0xfbe00000-0xfbe1ffff irq 48 at device 0.0 numa-domain 0 on pci10
May 25 15:54:34 	kernel 		pci10: <ACPI PCI bus> numa-domain 0 on pcib10
May 25 15:54:34 	kernel 		pcib10: <ACPI PCI-PCI bridge> irq 55 at device 0.0 numa-domain 0 on pci9
May 25 15:54:34 	kernel 		pci9: <ACPI PCI bus> numa-domain 0 on pcib9
May 25 15:54:34 	kernel 		pcib9: _OSC returned error 0x10
May 25 15:54:34 	kernel 		pcib9: <ACPI Host-PCI bridge> numa-domain 0 on acpi0
May 25 15:54:34 	kernel 		igb3: netmap queues/slots: TX 8/1024, RX 8/1024
May 25 15:54:34 	kernel 		igb3: Bound queue 7 to cpu 7
May 25 15:54:34 	kernel 		igb3: Bound queue 6 to cpu 6
May 25 15:54:34 	kernel 		igb3: Bound queue 5 to cpu 5
May 25 15:54:34 	kernel 		igb3: Bound queue 4 to cpu 4
May 25 15:54:34 	kernel 		igb3: Bound queue 3 to cpu 3
May 25 15:54:34 	kernel 		igb3: Bound queue 2 to cpu 2
May 25 15:54:34 	kernel 		igb3: Bound queue 1 to cpu 1
May 25 15:54:34 	kernel 		igb3: Bound queue 0 to cpu 0
May 25 15:54:34 	kernel 		igb3: Ethernet address: 00:25:90:ba:53:67
May 25 15:54:34 	kernel 		igb3: Using MSIX interrupts with 9 vectors
May 25 15:54:34 	kernel 		igb3: <Intel(R) PRO/1000 Network Connection, Version - 2.5.3-k> port 0xb000-0xb01f mem 0xe0d00000-0xe0d1ffff,0xe0d80000-0xe0d83fff irq 45 at device 0.3 numa-domain 0 on pci8
May 25 15:54:34 	kernel 		igb2: netmap queues/slots: TX 8/1024, RX 8/1024
May 25 15:54:34 	kernel 		igb2: Bound queue 7 to cpu 7
May 25 15:54:34 	kernel 		igb2: Bound queue 6 to cpu 6
May 25 15:54:34 	kernel 		igb2: Bound queue 5 to cpu 5
May 25 15:54:34 	kernel 		igb2: Bound queue 4 to cpu 4
May 25 15:54:34 	kernel 		igb2: Bound queue 3 to cpu 3
May 25 15:54:34 	kernel 		igb2: Bound queue 2 to cpu 2
May 25 15:54:34 	kernel 		igb2: Bound queue 1 to cpu 1
May 25 15:54:34 	kernel 		igb2: Bound queue 0 to cpu 0
May 25 15:54:34 	kernel 		igb2: Ethernet address: 00:25:90:ba:53:66
May 25 15:54:34 	kernel 		igb2: Using MSIX interrupts with 9 vectors
May 25 15:54:34 	kernel 		igb2: <Intel(R) PRO/1000 Network Connection, Version - 2.5.3-k> port 0xb020-0xb03f mem 0xe0d20000-0xe0d3ffff,0xe0d84000-0xe0d87fff irq 44 at device 0.2 numa-domain 0 on pci8
May 25 15:54:34 	kernel 		igb1: netmap queues/slots: TX 8/1024, RX 8/1024
May 25 15:54:34 	kernel 		igb1: Bound queue 7 to cpu 7
May 25 15:54:34 	kernel 		igb1: Bound queue 6 to cpu 6
May 25 15:54:34 	kernel 		igb1: Bound queue 5 to cpu 5
May 25 15:54:34 	kernel 		igb1: Bound queue 4 to cpu 4
May 25 15:54:34 	kernel 		igb1: Bound queue 3 to cpu 3
May 25 15:54:34 	kernel 		igb1: Bound queue 2 to cpu 2
May 25 15:54:34 	kernel 		igb1: Bound queue 1 to cpu 1
May 25 15:54:34 	kernel 		igb1: Bound queue 0 to cpu 0
May 25 15:54:34 	kernel 		igb1: Ethernet address: 00:25:90:ba:53:65
May 25 15:54:34 	kernel 		igb1: Using MSIX interrupts with 9 vectors
May 25 15:54:34 	kernel 		igb1: <Intel(R) PRO/1000 Network Connection, Version - 2.5.3-k> port 0xb040-0xb05f mem 0xe0d40000-0xe0d5ffff,0xe0d88000-0xe0d8bfff irq 46 at device 0.1 numa-domain 0 on pci8
May 25 15:54:34 	kernel 		igb0: netmap queues/slots: TX 8/1024, RX 8/1024
May 25 15:54:34 	kernel 		igb0: Bound queue 7 to cpu 7
May 25 15:54:34 	kernel 		igb0: Bound queue 6 to cpu 6
May 25 15:54:34 	kernel 		igb0: Bound queue 5 to cpu 5
May 25 15:54:34 	kernel 		igb0: Bound queue 4 to cpu 4
May 25 15:54:34 	kernel 		igb0: Bound queue 3 to cpu 3
May 25 15:54:34 	kernel 		igb0: Bound queue 2 to cpu 2
May 25 15:54:34 	kernel 		igb0: Bound queue 1 to cpu 1
May 25 15:54:34 	kernel 		igb0: Bound queue 0 to cpu 0
May 25 15:54:34 	kernel 		igb0: Ethernet address: 00:25:90:ba:53:64
May 25 15:54:34 	kernel 		igb0: Using MSIX interrupts with 9 vectors
May 25 15:54:34 	kernel 		igb0: <Intel(R) PRO/1000 Network Connection, Version - 2.5.3-k> port 0xb060-0xb07f mem 0xe0d60000-0xe0d7ffff,0xe0d8c000-0xe0d8ffff irq 43 at device 0.0 numa-domain 0 on pci8
May 25 15:54:34 	kernel 		pci8: <ACPI PCI bus> numa-domain 0 on pcib8
May 25 15:54:34 	kernel 		pcib8: <ACPI PCI-PCI bridge> irq 47 at device 3.0 numa-domain 0 on pci6
May 25 15:54:34 	kernel 		nvme0: <Generic NVMe Device> mem 0xe0e00000-0xe0e03fff irq 42 at device 0.0 numa-domain 0 on pci7
May 25 15:54:34 	kernel 		pci7: <ACPI PCI bus> numa-domain 0 on pcib7
May 25 15:54:34 	kernel 		pcib7: <ACPI PCI-PCI bridge> irq 47 at device 2.0 numa-domain 0 on pci6
May 25 15:54:34 	kernel 		pci6: <ACPI PCI bus> numa-domain 0 on pcib6
May 25 15:54:34 	kernel 		pcib6: _OSC returned error 0x10
May 25 15:54:34 	kernel 		pcib6: <ACPI Host-PCI bridge> numa-domain 0 on acpi0
May 25 15:54:34 	kernel 		pci5: <ACPI PCI bus> numa-domain 0 on pcib5
May 25 15:54:34 	kernel 		pcib5: _OSC returned error 0x10
May 25 15:54:34 	kernel 		pcib5: <ACPI Host-PCI bridge> numa-domain 0 on acpi0
May 25 15:54:34 	kernel 		pci0: <serial bus> at device 31.5 (no driver attached)
May 25 15:54:34 	kernel 		pci0: <memory> at device 31.2 (no driver attached)
May 25 15:54:34 	kernel 		isa0: <ISA bus> numa-domain 0 on isab0
May 25 15:54:34 	kernel 		isab0: <PCI-ISA bridge> at device 31.0 numa-domain 0 on pci0
May 25 15:54:34 	kernel 		pci4: <ACPI PCI bus> numa-domain 0 on pcib4
May 25 15:54:34 	kernel 		pcib4: <ACPI PCI-PCI bridge> irq 16 at device 29.0 numa-domain 0 on pci0
May 25 15:54:34 	kernel 		vgapci0: Boot video device
May 25 15:54:34 	kernel 		vgapci0: <VGA-compatible display> port 0x2000-0x207f mem 0xa9000000-0xa9ffffff,0xaa000000-0xaa01ffff irq 16 at device 0.0 numa-domain 0 on pci3
May 25 15:54:34 	kernel 		pci3: <ACPI PCI bus> numa-domain 0 on pcib3
May 25 15:54:34 	kernel 		pcib3: <ACPI PCI-PCI bridge> irq 16 at device 0.0 numa-domain 0 on pci2
May 25 15:54:34 	kernel 		pci2: <ACPI PCI bus> numa-domain 0 on pcib2
May 25 15:54:34 	kernel 		pcib2: <ACPI PCI-PCI bridge> irq 16 at device 28.4 numa-domain 0 on pci0
May 25 15:54:34 	kernel 		pci1: <ACPI PCI bus> numa-domain 0 on pcib1
May 25 15:54:34 	kernel 		pcib1: <ACPI PCI-PCI bridge> irq 16 at device 28.0 numa-domain 0 on pci0
May 25 15:54:34 	kernel 		pci0: <simple comms> at device 22.4 (no driver attached)
May 25 15:54:34 	kernel 		pci0: <simple comms> at device 22.1 (no driver attached)
May 25 15:54:34 	kernel 		pci0: <simple comms> at device 22.0 (no driver attached)
May 25 15:54:34 	kernel 		usbus0: 5.0Gbps Super Speed USB v3.0
May 25 15:54:34 	kernel 		usbus0 numa-domain 0 on xhci0
May 25 15:54:34 	kernel 		xhci_interrupt: host controller halted
May 25 15:54:34 	kernel 		usbus0: waiting for BIOS to give up control
May 25 15:54:34 	kernel 		xhci0: 32 bytes context size, 64-bit DMA
May 25 15:54:34 	kernel 		xhci0: <Intel Lewisburg USB 3.0 controller> mem 0xaa180000-0xaa18ffff irq 16 at device 20.0 numa-domain 0 on pci0
May 25 15:54:34 	kernel 		ahciem0: <AHCI enclosure management bridge> on ahci0
May 25 15:54:34 	kernel 		ahcich5: <AHCI channel> at channel 5 on ahci0
May 25 15:54:34 	kernel 		ahcich4: <AHCI channel> at channel 4 on ahci0
May 25 15:54:34 	kernel 		ahcich3: <AHCI channel> at channel 3 on ahci0
May 25 15:54:34 	kernel 		ahcich2: <AHCI channel> at channel 2 on ahci0
May 25 15:54:34 	kernel 		ahcich1: <AHCI channel> at channel 1 on ahci0
May 25 15:54:34 	kernel 		ahcich0: <AHCI channel> at channel 0 on ahci0
May 25 15:54:34 	kernel 		ahci0: AHCI v1.31 with 6 6Gbps ports, Port Multiplier not supported
May 25 15:54:34 	kernel 		ahci0: <Intel Lewisburg AHCI SATA controller> port 0x3030-0x3037,0x3020-0x3023,0x3000-0x301f mem 0xaa194000-0xaa195fff,0xaa196000-0xaa1960ff,0xaa100000-0xaa17ffff irq 16 at device 17.5 numa-domain 0 on pci0
May 25 15:54:34 	kernel 		pci0: <unknown> at device 17.1 (no driver attached)
May 25 15:54:34 	kernel 		pci0: <unknown> at device 17.0 (no driver attached)
May 25 15:54:34 	kernel 		pci0: <dasp, performance counters> at device 8.1 (no driver attached)
May 25 15:54:34 	kernel 		pci0: <ACPI PCI bus> numa-domain 0 on pcib0
May 25 15:54:34 	kernel 		pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff numa-domain 0 on acpi0
May 25 15:54:34 	kernel 		acpi_syscontainer0: <System Container> on acpi0
May 25 15:54:34 	kernel 		acpi_timer0: <24-bit timer at 3.579545MHz> port 0x508-0x50b on acpi0
May 25 15:54:34 	kernel 		Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
May 25 15:54:34 	kernel 		device_attach: hpet1 attach returned 12
May 25 15:54:34 	kernel 		hpet1: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
May 25 15:54:34 	kernel 		Event timer "HPET" frequency 24000000 Hz quality 550
May 25 15:54:34 	kernel 		Timecounter "HPET" frequency 24000000 Hz quality 950
May 25 15:54:34 	kernel 		hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
May 25 15:54:34 	kernel 		Event timer "i8254" frequency 1193182 Hz quality 100
May 25 15:54:34 	kernel 		Timecounter "i8254" frequency 1193182 Hz quality 0
May 25 15:54:34 	kernel 		attimer0: <AT timer> port 0x40-0x43,0x50-0x53 irq 0 on acpi0
May 25 15:54:34 	kernel 		Event timer "RTC" frequency 32768 Hz quality 0
May 25 15:54:34 	kernel 		atrtc0: registered as a time-of-day clock, resolution 1.000000s
May 25 15:54:34 	kernel 		atrtc0: <AT realtime clock> port 0x70-0x71,0x74-0x77 irq 8 on acpi0
May 25 15:54:34 	kernel 		cpu7: <ACPI CPU> numa-domain 0 on acpi0
May 25 15:54:34 	kernel 		cpu6: <ACPI CPU> numa-domain 0 on acpi0
May 25 15:54:34 	kernel 		cpu5: <ACPI CPU> numa-domain 0 on acpi0
May 25 15:54:34 	kernel 		cpu4: <ACPI CPU> numa-domain 0 on acpi0
May 25 15:54:34 	kernel 		cpu3: <ACPI CPU> numa-domain 0 on acpi0
May 25 15:54:34 	kernel 		cpu2: <ACPI CPU> numa-domain 0 on acpi0
May 25 15:54:34 	kernel 		cpu1: <ACPI CPU> numa-domain 0 on acpi0
May 25 15:54:34 	kernel 		cpu0: <ACPI CPU> numa-domain 0 on acpi0
May 25 15:54:34 	kernel 		acpi0: Power Button (fixed)
May 25 15:54:34 	kernel 		acpi0: <SUPERM SUPERM> on motherboard
May 25 15:54:34 	kernel 		padlock0: No ACE support.
May 25 15:54:34 	kernel 		cryptosoft0: <software crypto> on motherboard
May 25 15:54:34 	kernel 		nexus0
May 25 15:54:34 	kernel 		random: fast provider: "Intel Secure Key RNG"
May 25 15:54:34 	kernel 		random: registering fast source Intel Secure Key RNG
May 25 15:54:34 	kernel 		module_register_init: MOD_LOAD (vesa, 0xffffffff8120aaa0, 0) error 19
May 25 15:54:34 	kernel 		netmap: loaded module
May 25 15:54:34 	kernel 		kbd1 at kbdmux0
May 25 15:54:34 	kernel 		wlan: mac acl policy registered
May 25 15:54:34 	kernel 		module_register_init: MOD_LOAD (iwi_monitor_fw, 0xffffffff806a85c0, 0) error 1
May 25 15:54:34 	kernel 		iwi_monitor: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
May 25 15:54:34 	kernel 		iwi_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi.LICENSE.
May 25 15:54:34 	kernel 		module_register_init: MOD_LOAD (iwi_ibss_fw, 0xffffffff806a8510, 0) error 1
May 25 15:54:34 	kernel 		iwi_ibss: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
May 25 15:54:34 	kernel 		iwi_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi.LICENSE.
May 25 15:54:34 	kernel 		module_register_init: MOD_LOAD (iwi_bss_fw, 0xffffffff806a8460, 0) error 1
May 25 15:54:34 	kernel 		iwi_bss: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
May 25 15:54:34 	kernel 		iwi_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi.LICENSE.
May 25 15:54:34 	kernel 		module_register_init: MOD_LOAD (ipw_monitor_fw, 0xffffffff80681590, 0) error 1
May 25 15:54:34 	kernel 		ipw_monitor: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
May 25 15:54:34 	kernel 		ipw_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw.LICENSE.
May 25 15:54:34 	kernel 		module_register_init: MOD_LOAD (ipw_ibss_fw, 0xffffffff806814e0, 0) error 1
May 25 15:54:34 	kernel 		ipw_ibss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
May 25 15:54:34 	kernel 		ipw_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw.LICENSE.
May 25 15:54:34 	kernel 		random: entropy device external interface
May 25 15:54:34 	kernel 		module_register_init: MOD_LOAD (ipw_bss_fw, 0xffffffff80681430, 0) error 1
May 25 15:54:34 	kernel 		ipw_bss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
May 25 15:54:34 	kernel 		ipw_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw.LICENSE.
May 25 15:54:34 	kernel 		Timecounter "TSC-low" frequency 1097452199 Hz quality 1000
May 25 15:54:34 	kernel 		SMP: AP CPU #3 Launched!
May 25 15:54:34 	kernel 		SMP: AP CPU #7 Launched!
May 25 15:54:34 	kernel 		SMP: AP CPU #5 Launched!
May 25 15:54:34 	kernel 		SMP: AP CPU #2 Launched!
May 25 15:54:34 	kernel 		SMP: AP CPU #4 Launched!
May 25 15:54:34 	kernel 		SMP: AP CPU #6 Launched!
May 25 15:54:34 	kernel 		SMP: AP CPU #1 Launched!
May 25 15:54:34 	kernel 		ioapic4 <Version 2.0> irqs 48-55 on motherboard
May 25 15:54:34 	kernel 		ioapic3 <Version 2.0> irqs 40-47 on motherboard
May 25 15:54:34 	kernel 		ioapic2 <Version 2.0> irqs 32-39 on motherboard
May 25 15:54:34 	kernel 		ioapic1 <Version 2.0> irqs 24-31 on motherboard
May 25 15:54:34 	kernel 		ioapic0 <Version 2.0> irqs 0-23 on motherboard
May 25 15:54:34 	kernel 		FreeBSD/SMP: 1 package(s) x 4 core(s) x 2 hardware threads
May 25 15:54:34 	kernel 		FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs
May 25 15:54:34 	kernel 		ACPI APIC Table: <SUPERM SMCI--MB>
May 25 15:54:34 	kernel 		Event timer "LAPIC" quality 600
May 25 15:54:34 	kernel 		avail memory = 32890949632 (31367 MB)
May 25 15:54:34 	kernel 		real memory = 34359738368 (32768 MB)
May 25 15:54:34 	kernel 		TSC: P-state invariant, performance statistics
May 25 15:54:34 	kernel 		VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID,VID,PostIntr
May 25 15:54:34 	kernel 		XSAVE Features=0xf<XSAVEOPT,XSAVEC,XINUSE,XSAVES>
May 25 15:54:34 	kernel 		Structured Extended Features3=0x9c002400<IBPB,STIBP,SSBD>
May 25 15:54:34 	kernel 		Structured Extended Features2=0x8<PKU>
May 25 15:54:34 	kernel 		Structured Extended Features=0xd39ffffb<FSGSBASE,TSCADJ,BMI1,HLE,AVX2,FDPEXC,SMEP,BMI2,ERMS,INVPCID,RTM,PQM,NFPUSG,MPX,PQE,AVX512F,AVX512DQ,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,PROCTRACE,AVX512CD,AVX512BW,AVX512VL>
May 25 15:54:34 	kernel 		AMD Features2=0x121<LAHF,ABM,Prefetch>
May 25 15:54:34 	kernel 		AMD Features=0x2c100800<SYSCALL,NX,Page1GB,RDTSCP,LM>
May 25 15:54:34 	kernel 		Features2=0x7ffefbff<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND>
May 25 15:54:34 	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>
May 25 15:54:34 	kernel 		Origin="GenuineIntel" Id=0x50654 Family=0x6 Model=0x55 Stepping=4
May 25 15:54:34 	kernel 		CPU: Intel(R) Xeon(R) D-2123IT CPU @ 2.20GHz (2194.90-MHz K8-class CPU)
May 25 15:54:34 	kernel 		VT(efifb): resolution 1024x768
May 25 15:54:34 	kernel 		FreeBSD clang version 6.0.0 (tags/RELEASE_600/final 326565) (based on LLVM 6.0.0)
May 25 15:54:34 	kernel 		root@buildbot1-nyi.netgate.com:/build/ce-crossbuild-244/obj/amd64/ZfGpH5cd/build/ce-crossbuild-244/pfSense/tmp/FreeBSD-src/sys/pfSense amd64
May 25 15:54:34 	kernel 		FreeBSD 11.2-RELEASE-p10 #9 4a2bfdce133(RELENG_2_4_4): Wed May 15 18:54:42 EDT 2019
May 25 15:54:34 	kernel 		FreeBSD is a registered trademark of The FreeBSD Foundation.
May 25 15:54:34 	kernel 		The Regents of the University of California. All rights reserved.
May 25 15:54:34 	kernel 		Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
May 25 15:54:34 	kernel 		Copyright (c) 1992-2018 The FreeBSD Project.
May 25 15:54:34 	syslogd 		kernel boot file is /boot/kernel/kernel
May 25 15:50:59 	syslogd 		exiting on signal 15
May 25 15:50:59 	shutdown 		power-down by admin:
                          1 Reply Last reply Reply Quote 0
                          • L
                            lifespeed
                            last edited by lifespeed

                            I see at the very end (top) of the successful WAN IPv6 log file, there is this line. The failed log apparently doesn't receive an RA? Isn't that Comcast and the modem's doing? I have WAN interface "Do not wait for a RA" checked, although it doesn't seem to behave any differently when it is not checked.

                            ay 25 16:14:21 	rtsold 		Received RA specifying route fe80::201:xxx:xxx:xxx6 for interface wan(igb0)
                            JKnottJ 1 Reply Last reply Reply Quote 0
                            • JKnottJ
                              JKnott @lifespeed
                              last edited by

                              @lifespeed

                              It appears as though IPv6 is working. However, there is actually no need for a "WAN" address, though one may be provided. With IPv6, link local addresses are often used for routing, as shown in your example above. You normally want RAs, as that provides the address of the ISPs gateway. It could also provide other info, such as DNS address.

                              PfSense running on Qotom mini PC
                              i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
                              UniFi AC-Lite access point

                              I haven't lost my mind. It's around here...somewhere...

                              L 1 Reply Last reply Reply Quote 0
                              • L
                                lifespeed @JKnott
                                last edited by lifespeed

                                @JKnott said in fails to get WAN IPv6 address ( was wrong date and time):

                                @lifespeed

                                It appears as though IPv6 is working. However, there is actually no need for a "WAN" address, though one may be provided. With IPv6, link local addresses are often used for routing, as shown in your example above. You normally want RAs, as that provides the address of the ISPs gateway. It could also provide other info, such as DNS address.

                                In the log where pfSense fails to get an IPv6 address there is no RA shown in the log. I must have IPv6 for my server behind pfSense, and yes it is device-generated from the LAN IPv6 address.

                                If pfSense doesn't get an IPv6, my LAN and devices on it don't get an IPv6 either.

                                It seems to me this is a problem, especially since nothing works in this state. It seems as though you're telling me everything is fine. Which it is, in the second log. But not the first, which is what happens half the time I reboot.

                                My LAN and pfSense must have globally-routable addresses.

                                JKnottJ 1 Reply Last reply Reply Quote 0
                                • JKnottJ
                                  JKnott @lifespeed
                                  last edited by

                                  @lifespeed

                                  No, my point was you don't need a public WAN address, as link local addresses are frequently used for routing. You mentioned not waiting RAs. I don't have that checked. I believe it's normal to not to. As for a WAN address, if it's a /128, you can be sure it's not used for routing. On my system, my WAN address is a /128 and I also have a /64 link local address, which is used for routing. So yes, you can have routeable LAN addresses, without a routeable WAN address. In fact, one of the options with pfSense is to request only a prefix.

                                  PfSense running on Qotom mini PC
                                  i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
                                  UniFi AC-Lite access point

                                  I haven't lost my mind. It's around here...somewhere...

                                  L 1 Reply Last reply Reply Quote 0
                                  • L
                                    lifespeed @JKnott
                                    last edited by

                                    @JKnott said in fails to get WAN IPv6 address ( was wrong date and time):

                                    @lifespeed

                                    No, my point was you don't need a public WAN address, as link local addresses are frequently used for routing. You mentioned not waiting RAs. I don't have that checked. I believe it's normal to not to. As for a WAN address, if it's a /128, you can be sure it's not used for routing. On my system, my WAN address is a /128 and I also have a /64 link local address, which is used for routing. So yes, you can have routeable LAN addresses, without a routeable WAN address. In fact, one of the options with pfSense is to request only a prefix.

                                    I have tried to "request prefix only", this doesn't work. If I do so I get a locally-routable address for pfSense beginning with FE80, which is a fail.

                                    JKnottJ 1 Reply Last reply Reply Quote 0
                                    • JKnottJ
                                      JKnott @lifespeed
                                      last edited by

                                      @lifespeed

                                      So, don't select that. I don't know what you've done, but sometimes it's best to start from scratch, in case you did something you shouldn't have. Perhaps there's someone else here, who can help you with Comcast. My experience is with Rogers, where IPv6 works well.

                                      PfSense running on Qotom mini PC
                                      i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
                                      UniFi AC-Lite access point

                                      I haven't lost my mind. It's around here...somewhere...

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