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



  • I see the wrong date and time everywhere, it's behind three days and the time error isn't due to UMT time. I have the NTP servers set to:

    pool.ntp.org 0.pfsense.pool.ntp.org

    What is going on?

    Edit: the title of this post is updated to reflect the root of the problem, failed IPv6 WAN address, and internet connectivity. Please skip to this post for logs showing failure and success.

    May 16 16:08:21 	php-fpm 	363 	/services_dhcp.php: 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 16 16:08:19 	dhcpleases 		Could not deliver signal HUP to process because its pidfile (/var/run/dnsmasq.pid) does not exist, No such process.
    May 16 16:08:19 	dhcpleases 		/etc/hosts changed size from original!
    May 16 16:08:18 	check_reload_status 		Syncing firewall
    May 16 16:05:55 	check_reload_status 		Reloading filter
    May 16 16:05:55 	php-fpm 	363 	/system.php: NTPD is starting up.
    


  • @lifespeed try ntpq -p on cli.. what does it say?



  • Does this show pfSense not reaching the two NTP servers listed?

         remote           refid      st t when poll reach   delay   offset  jitter
    ==============================================================================
     pool.ntp.org    .POOL.          16 p    -   64    0    0.000    0.000   0.000
     0.pfsense.pool. .POOL.          16 p    -   64    0    0.000    0.000   0.000
     ntp18.doctor.co 50.205.244.28    2 u   13   64  377   32.772  3119953 233177.
     173.0.48.220 (1 43.77.130.254    2 u   13   64  177   15.977  3119953 242990.
     LAX.CALTICK.NET 98.152.165.38    2 u    6   64  377    9.058  3120007 233509.
     www-ntp-org.nss 163.237.218.19   2 u   11   64  177   48.878  3119969 216499.
     tick.srs1.ntfo. 206.55.64.77     3 u    4   64  177    6.201  3120023 217997.
     ntp1.wiktel.com .PPS.            1 u   12   64   77   37.059  3119961 197102.
     ntp2.wiktel.com .GPS.            1 u    6   64   77   37.150  3120007 200672.
     time.cloudflare 10.4.0.166       3 u   11   64   77   10.648  3119968 196423.
     puppet.kenyonra .PHC0.           1 u    8   64   37    9.086  3119992 167410.
     66.85.78.80     172.16.23.153    2 u    4   64   17   43.065  3120023 134910.
     time.airgapped. 216.218.254.202  2 u    6   64   17   44.081  3120007 136793.
     69.10.161.7     195.205.216.85   3 u    5   64    7   13.168  3120014 95259.6
     vps5.ctyme.com  216.218.254.202  2 u    6   64    7    5.124  3120007 94638.9
     12.167.151.1    66.85.78.80      3 u    6   64    7   44.555  3120007 93908.8
     clock.nyc.he.ne .CDMA.           1 u    2   64    3   40.558  3120038 49260.9
     216.126.233.109 128.227.205.3    2 u    3   64    3   53.616  3120030 46951.5
    
    


  • Well it means it contacts the pool, gets the various ntp servers but it seems that no traffic on port 123 occurs. There should be one star and a few + and - in front of the names. Certainly you don't need to create any rules on your wan interface.
    Looks like a connectivity issue.
    Most probably something blocks ntp traffic upstream.



  • @netblues said in wrong date and time:

    Most probably something blocks ntp traffic upstream.

    If that were the case wouldn't my devices on the network have problems with NTP as well? I just checked the time on my Windows 10 PC, and the time is exactly the same as my mobile phone.



  • Is the "clock unsynchronized" error below the symptom, not the problem? ixl2 is LAN, igb0 is WAN.

    
    May 17 07:02:11 	ntpd 	42225 	Soliciting pool server 173.255.215.209
    May 17 07:02:10 	ntpd 	42225 	Soliciting pool server 64.22.253.155
    May 17 07:02:10 	ntpd 	42225 	Soliciting pool server 138.236.128.112
    May 17 07:02:09 	ntpd 	42225 	Soliciting pool server 207.192.69.118
    May 17 07:02:09 	ntpd 	42225 	Soliciting pool server 162.159.200.1
    May 17 07:02:08 	ntpd 	42225 	Soliciting pool server 199.102.46.78
    May 17 07:02:08 	ntpd 	42225 	Soliciting pool server 45.33.84.208
    May 17 07:02:07 	ntpd 	42225 	Soliciting pool server 50.116.52.97
    May 17 07:02:06 	ntpd 	42225 	kernel reports TIME_ERROR: 0x4041: Clock Unsynchronized
    May 17 07:02:06 	ntpd 	42225 	kernel reports TIME_ERROR: 0x4041: Clock Unsynchronized
    May 17 07:02:06 	ntpd 	42225 	Listening on routing socket on fd #31 for interface updates
    May 17 07:02:06 	ntpd 	42225 	Listen normally on 10 lo0 127.0.0.1:123
    May 17 07:02:06 	ntpd 	42225 	Listen normally on 9 lo0 [fe80::1%10]:123
    May 17 07:02:06 	ntpd 	42225 	Listen normally on 8 lo0 [::1]:123
    May 17 07:02:06 	ntpd 	42225 	Listen normally on 7 ixl2 [fe80::1:1%7]:123
    May 17 07:02:06 	ntpd 	42225 	Listen normally on 6 ixl2 [2601:646:xxxx:xxxx:225:90ff:febb:xxxx]:123
    May 17 07:02:06 	ntpd 	42225 	Listen normally on 5 ixl2 192.168.1.1:123
    May 17 07:02:06 	ntpd 	42225 	Listen normally on 4 igb0 [2001:xxx:6045:45:xxxx:6b5c:xxxx:xxx]:123
    May 17 07:02:06 	ntpd 	42225 	Listen normally on 3 igb0 76.126.xxx.xxx:123
    May 17 07:02:06 	ntpd 	42225 	Listen normally on 2 igb0 [fe80::225:90ff:feba:5364%1]:123
    May 17 07:02:06 	ntpd 	42225 	Listen and drop on 1 v4wildcard 0.0.0.0:123
    May 17 07:02:06 	ntpd 	42225 	Listen and drop on 0 v6wildcard [::]:123
    May 17 07:02:06 	ntpd 	42225 	gps base set to 2019-04-28 (week 2051)
    May 17 07:02:06 	ntpd 	42225 	basedate set to 2019-04-28
    May 17 07:02:06 	ntpd 	42225 	proto: precision = 0.047 usec (-24)
    May 17 07:02:06 	ntpd 	42060 	Command line: /usr/local/sbin/ntpd -g -c /var/etc/ntpd.conf -p /var/run/ntpd.pid
    May 17 07:02:06 	ntpd 	42060 	ntpd 4.2.8p13@1.3847-o Fri May 10 20:05:13 UTC 2019 (1): Starting
    May 17 07:02:06 	ntpd 	35185 	64.22.253.155 local addr 76.1xx.xxx.72 -> <null> 
    


  • @lifespeed said in wrong date and time:

    @netblues said in wrong date and time:

    Most probably something blocks ntp traffic upstream.

    If that were the case wouldn't my devices on the network have problems with NTP as well? I just checked the time on my Windows 10 PC, and the time is exactly the same as my mobile phone.

    Seems so..
    Have a look at states, filter on port 123 and see if you get anything
    Sync doesnt occur all the time
    You should also see ntp traffic from your lan.
    8107467b-57f1-4d56-9cb7-cf7aae2409ee-image.png

    This is the wan port syncing pf



  • @netblues said in wrong date and time:

    Have a look at states, filter on port 123 and see if you get anything

    Is this what you mean, firewall logs filtered by port? My external IP is 76.126.xxx.xxx. Do I need to allow inbound from WAN on port 123 to my external IP for pFsense? I'm using dual stack v4 and v6.

     	May 17 07:03:47 	WAN 	Default deny rule IPv4 (1000000103) 	156.96.155.246:57873		76.126.xxx.xxx:123		UDP
    	May 17 07:00:54 	WAN 	Default deny rule IPv4 (1000000103) 	51.159.59.122:55133		76.126.xxx.xxx:123		UDP
    	May 17 07:00:02 	WAN 	Default deny rule IPv4 (1000000103) 	45.13.93.82:44178		76.126.xxx.xxx::8123		TCP:S
    	May 17 06:54:04 	WAN 	Default deny rule IPv4 (1000000103) 	5.182.210.95:59074		76.126.xxx.xxx:123		UDP
    	May 17 06:53:53 	WAN 	Default deny rule IPv4 (1000000103) 	194.180.224.123:33839		76.126.xxx.xxx:123		UDP
    	May 17 06:38:00 	WAN 	Default deny rule IPv4 (1000000103) 	80.82.65.190:47382		76.126.xxx.xxx:123		TCP:S
    	May 17 06:26:19 	WAN 	Default deny rule IPv4 (1000000103) 	167.172.49.247:48318		76.126.xxx.xxx:12336		TCP:S
    	May 17 06:06:38 	WAN 	Default deny rule IPv4 (1000000103) 	5.182.210.95:39736		76.126.xxx.xxx:123		UDP 
    


  • @lifespeed Well, logs have much more noise, but could do.
    States is realtime

    6f66828e-add8-421b-851a-43f1f8d97996-image.png

    However you have to refresh a bit to spot it. Sync doesn't occur all the time.
    Now judging from the logs seems that something blocks port 123.
    Having said that, on a simple pf installation, with only ping allowed on wan and everything allowed on the lan, ntp doesn't need anything special to function.

    As a test, try allowing incoming on wan on 123 and see if it works.
    If it does, then the problem has to be investigated on firewall rules.



  • I don't know what you mean by "filter on states". I allowed WAN with a destination of port 123, no change.

    At one time I had VLANs setup, but gave up as they seemed beyond my limited abilities. Is it possible I have somehow assigned NTP to a VLAN that no longer exists? I see the NTP server has both WAN and LAN listed, but is that relevant? I'm not trying to run an NTP server on my network.

    f63693f5-aa70-4d3c-a4ea-e5ce4ebdb160-image.png



  • @lifespeed go to web interface, diagnostics states, and use 123 as a filter and see what you get. See my picture attached. :)

    Well, as it says, if you have nothing selected on ntp, it will listen on all interfaces.
    And a server and a client is essentially the same thing here.

    I doubt vlans have anything to do with that.
    Please verify that you are able to ping from cli most if not all of the ip's that appear on ntpq -p too.

    If still all is well and no ntp works, a packet capture on the wan , on udp 123 is the next thing (diagnostics, packet capture)



  • I ran a packet capture on the WAN, port 123, not promiscuous, and got nothing after I stopped the capture and pressed "view capture". I ran ntpq -p from CLI during the packet capture.

    Thanks for all your help this far. I can't help but think I have deleted or changed a default setting that has borked NTP. But it would seem the default allow all outgoing would work.

    Here are my LAN rules, outgoing is allowed.
    7f4551c0-4d91-46e4-a03f-2320ff340efb-image.png



  • I can ping the NTP servers from CLI.



  • Lan rules is ok, certainly not an issue.
    How about outbound nat?
    (if you can ping, most probably no issues there too)
    Do you still getting logs with 123 denied? With an allow rule on wan you must be able to capture that traffic no matter what.

    This is what capture looks
    fb8af119-aa3a-4195-b9d7-10f96bf4520f-image.png



  • I enabled WAN port 123 again, and packet captured while running

    ntpq -p
    

    from the command line. Even with WAN rule set there doesn't seem to be any action on packet capture.
    49c9277b-9006-4922-8689-3cf56af3541e-image.png

    Here's outbound NAT, it may show an automatic rule vestige of my failed VLAN attempt. 192.168.2.0 I think is a leftover VLAN, while my LAN is 192.168.1.0.
    0cf19445-1f41-421e-8b21-ec1712c81b1d-image.png

    I am not seeing any port 123 blocks in the firewall logs. States shows port 123 activity.
    f761fa11-38e9-4a57-8f71-b582aa4eacce-image.png



  • Well, since you see states, with 76 bytes on your wan, then you are getting ntp packets..
    So no firewall is blocking anything. You should be able to capture them too.
    Try it via the web interface, diagnostics packet capture.

    What is status/ntp say and what is in status/system logs/ntp ?
    Also enable all logging options in services/ntp
    I guess you have tried rebooting, as a last resort.



  • @netblues

    it worked this time, packet capture that is

    10:06:52.522715 IP 76.126.xxx.xxx.123 > 4.53.160.75.123: UDP, length 48
    10:06:52.554326 IP 4.53.160.75.123 > 76.126.xxx.xxx.123: UDP, length 48
    10:06:53.523242 IP 76.126.xxx.xxx.123 > 185.215.224.214.123: UDP, length 48
    10:06:53.523260 IP 76.126.xxx.xxx.123 > 192.81.135.252.123: UDP, length 48
    10:06:53.532481 IP 192.81.135.252.123 > 76.126.xxx.xxx.123: UDP, length 48
    10:06:53.534081 IP 185.215.224.214.123 > 76.126.xxx.xxx.123: UDP, length 48
    10:06:54.523411 IP 76.126.xxx.xxx.123 > 50.212.98.107.123: UDP, length 48
    10:06:54.580536 IP 50.212.98.107.123 > 76.126.xxx.xxx.123: UDP, length 48
    10:06:55.523635 IP 76.126.xxx.xxx.123 > 192.81.135.252.123: UDP, length 48
    10:06:55.533074 IP 192.81.135.252.123 > 76.126.xxx.xxx.123: UDP, length 48
    10:06:56.527876 IP 76.126.xxx.xxx.123 > 4.53.160.75.123: UDP, length 48
    10:06:56.527882 IP 76.126.xxx.xxx.123 > 209.50.63.74.123: UDP, length 48
    10:06:56.527887 IP 76.126.xxx.xxx.123 > 45.63.54.13.123: UDP, length 48
    10:06:56.533229 IP 209.50.63.74.123 > 76.126.xxx.xxx.123: UDP, length 48
    10:06:56.539392 IP 45.63.54.13.123 > 76.126.xxx.xxx.123: UDP, length 48
    10:06:56.556456 IP 4.53.160.75.123 > 76.126.xxx.xxx.123: UDP, length 48
    10:06:57.526188 IP 76.126.xxx.xxx.123 > 192.81.135.252.123: UDP, length 48
    10:06:57.526195 IP 76.126.xxx.xxx.123 > 44.190.6.254.123: UDP, length 48
    10:06:57.531438 IP 44.190.6.254.123 > 76.126.xxx.xxx.123: UDP, length 48
    10:06:57.531588 IP 192.81.135.252.123 > 76.126.xxx.xxx.123: UDP, length 48
    10:06:58.524430 IP 76.126.xxx.xxx.123 > 4.53.160.75.123: UDP, length 48
    10:06:58.556095 IP 4.53.160.75.123 > 76.126.xxx.xxx.123: UDP, length 48
    10:06:59.522822 IP 76.126.xxx.xxx.123 > 192.81.135.252.123: UDP, length 48
    10:06:59.522833 IP 76.126.xxx.xxx.123 > 159.203.158.197.123: UDP, length 48
    10:06:59.529147 IP 192.81.135.252.123 > 76.126.xxx.xxx.123: UDP, length 48
    10:06:59.571784 IP 159.203.158.197.123 > 76.126.xxx.xxx.123: UDP, length 48
    10:07:00.522475 IP 76.126.xxx.xxx.123 > 4.53.160.75.123: UDP, length 48
    10:07:00.551285 IP 4.53.160.75.123 > 76.126.xxx.xxx.123: UDP, length 48
    10:07:01.524139 IP 76.126.xxx.xxx.123 > 192.81.135.252.123: UDP, length 48
    10:07:01.524151 IP 76.126.xxx.xxx.123 > 162.159.200.1.123: UDP, length 48
    10:07:01.533563 IP 162.159.200.1.123 > 76.126.xxx.xxx.123: UDP, length 48
    10:07:01.533960 IP 192.81.135.252.123 > 76.126.xxx.xxx.123: UDP, length 48
    10:07:02.527698 IP 76.126.xxx.xxx.123 > 4.53.160.75.123: UDP, length 48
    10:07:02.556506 IP 4.53.160.75.123 > 76.126.xxx.xxx.123: UDP, length 48
    10:07:03.530844 IP 76.126.xxx.xxx.123 > 192.81.135.252.123: UDP, length 48
    10:07:03.536242 IP 192.81.135.252.123 > 76.126.xxx.xxx.123: UDP, length 48
    10:07:04.528000 IP 76.126.xxx.xxx.123 > 4.53.160.75.123: UDP, length 48
    10:07:04.528013 IP 76.126.xxx.xxx.123 > 72.87.88.203.123: UDP, length 48
    10:07:04.556810 IP 4.53.160.75.123 > 76.126.xxx.xxx.123: UDP, length 48
    10:07:04.574781 IP 72.87.88.203.123 > 76.126.xxx.xxx.123: UDP, length 48
    10:07:05.530521 IP 76.126.xxx.xxx.123 > 192.81.135.252.123: UDP, length 48
    10:07:05.536805 IP 192.81.135.252.123 > 76.126.xxx.xxx.123: UDP, length 48
    10:07:06.523536 IP 76.126.xxx.xxx.123 > 4.53.160.75.123: UDP, length 48
    10:07:06.552973 IP 4.53.160.75.123 > 76.126.xxx.xxx.123: UDP, length 48
    10:07:07.523388 IP 76.126.xxx.xxx.123 > 66.228.58.20.123: UDP, length 48
    10:07:07.563108 IP 66.228.58.20.123 > 76.126.xxx.xxx.123: UDP, length 48
    10:07:08.525179 IP 76.126.xxx.xxx.123 > 45.76.244.193.123: UDP, length 48
    10:07:08.525183 IP 76.126.xxx.xxx.123 > 104.194.8.227.123: UDP, length 48
    10:07:08.538954 IP 104.194.8.227.123 > 76.126.xxx.xxx.123: UDP, length 48
    10:07:08.542720 IP 45.76.244.193.123 > 76.126.xxx.xxx.123: UDP, length 48
    

    NTP status is still bad

    Network Time Protocol Status
    Pool Placeholder 	pool.ntp.org 	.POOL. 	16 	p 	- 	64 	0 	0.000 	0.000 	0.000
    Pool Placeholder 	0.pfsense.pool. 	.POOL. 	16 	p 	- 	64 	0 	0.000 	0.000 	0.000
    Unreach/Pending 	45.76.244.193 	216.239.35.0 	2 	u 	8 	64 	377 	18.508 	3894306 	232734.
    Unreach/Pending 	198.60.22.240 	.XMIS. 	1 	u 	6 	64 	377 	14.489 	3894322 	232993.
    Unreach/Pending 	66.228.58.20 	198.72.72.10 	3 	u 	12 	64 	377 	33.938 	3894276 	230345.
    Unreach/Pending 	50.212.98.107 	209.50.63.74 	3 	u 	22 	64 	377 	58.577 	3894199 	228598.
    Unreach/Pending 	159.203.158.197 	128.59.0.245 	2 	u 	20 	64 	377 	50.835 	3894214 	228293.
    Unreach/Pending 	208.67.72.43 	152.2.133.55 	2 	u 	4 	64 	377 	47.912 	3894337 	229180.
    Unreach/Pending 	104.236.116.147 	128.59.0.245 	2 	u 	3 	64 	377 	45.172 	3894345 	231712.
    Unreach/Pending 	68.233.45.146 	132.163.96.1 	2 	u 	5 	64 	271 	46.219 	3894330 	303620.
    Unreach/Pending 	162.159.200.1 	10.4.0.166 	3 	u 	17 	64 	77 	8.466 	3894237 	196053.
    Unreach/Pending 	45.63.54.13 	98.152.165.38 	2 	u 	20 	64 	37 	11.729 	3894214 	170106.
    Unreach/Pending 	185.215.224.214 	164.67.62.194 	2 	u 	20 	64 	37 	12.150 	3894214 	171169.
    Unreach/Pending 	44.190.6.254 	127.67.113.92 	2 	u 	23 	64 	37 	5.146 	3894191 	166467.
    Unreach/Pending 	209.50.63.74 	198.60.22.240 	2 	u 	22 	64 	37 	6.787 	3894198 	168655.
    Unreach/Pending 	4.53.160.75 	142.66.101.13 	2 	u 	22 	64 	17 	29.953 	3894199 	133965.
    Unreach/Pending 	192.81.135.252 	.PHC0. 	1 	u 	20 	64 	17 	8.279 	3894214 	136273.
    Unreach/Pending 	163.237.218.19 	.GPS. 	1 	u 	23 	64 	7 	31.696 	3894191 	92463.5
    Unreach/Pending 	72.5.72.15 	216.218.254.202 	2 	u 	37 	64 	3 	14.127 	3894083 	49288.6
    Unreach/Pending 	69.10.161.7 	195.205.216.85 	3 	u 	28 	64 	1 	13.803 	3894152 	5098.69
    
    


  • Isn't the outbound NAT table auto rules a bit suspicious with the extra subnet?



  • @netblues said in wrong date and time:

    Well, since you see states, with 76 bytes on your wan, then you are getting ntp packets..

    Doesn't states show I'm sending NTP, not receiving?



  • @lifespeed 76/76 means 76 send 76 received... so you are receiving
    No, nat is not suspicius.. Move the tab to manual, delete everything and rehit auto.
    (i suppose you don't have any manual entries)
    it should create new ones without the stale vlan.

    And in your capture there are packets traveling both ways too.

    Post the ntp log from system logs, and restart ntp service



  • Here are the NTP logs, it don't know why it isn't working. Rebooting modem and router now.

    Advanced Log Filter
    Last 1000 NTP Log Entries. (Maximum 1000)
    May 18 19:53:12 	ntpd 	59428 	184.105.182.15 local addr 76.126.123.72 -> <null>
    May 18 19:53:12 	ntpd 	59428 	184.105.182.15 0012 82 demobilize assoc 13354
    May 18 19:53:12 	ntpd 	59428 	184.105.182.15 1015 85 restart timeout
    May 18 19:53:05 	ntpd 	59428 	72.14.183.239 local addr 76.126.123.72 -> <null>
    May 18 19:53:05 	ntpd 	59428 	72.14.183.239 0012 82 demobilize assoc 13353
    May 18 19:53:05 	ntpd 	59428 	72.14.183.239 1015 85 restart timeout
    May 18 19:52:31 	ntpd 	59428 	162.159.200.1 0014 84 reachable
    May 18 19:52:30 	ntpd 	59428 	50.205.244.114 0014 84 reachable
    May 18 19:52:28 	ntpd 	59428 	193.29.63.150 0014 84 reachable
    May 18 19:52:28 	ntpd 	59428 	66.85.78.80 0014 84 reachable
    May 18 19:52:27 	ntpd 	59428 	50.205.244.114 0011 81 mobilize assoc 13370
    May 18 19:52:27 	ntpd 	59428 	Soliciting pool server 50.205.244.114
    May 18 19:52:26 	ntpd 	59428 	162.159.200.1 0011 81 mobilize assoc 13369
    May 18 19:52:26 	ntpd 	59428 	Soliciting pool server 162.159.200.1
    May 18 19:52:25 	ntpd 	59428 	66.85.78.80 0011 81 mobilize assoc 13368
    May 18 19:52:25 	ntpd 	59428 	Soliciting pool server 66.85.78.80
    May 18 19:52:24 	ntpd 	59428 	193.29.63.150 0011 81 mobilize assoc 13367
    May 18 19:52:24 	ntpd 	59428 	Soliciting pool server 193.29.63.150
    May 18 19:52:00 	ntpd 	59428 	108.61.73.244 local addr 76.126.123.72 -> <null>
    May 18 19:52:00 	ntpd 	59428 	108.61.73.244 0012 82 demobilize assoc 13352
    May 18 19:52:00 	ntpd 	59428 	108.61.73.244 1015 85 restart timeout 
    


  • The first time I rebooted it didn't successfully pull WAN addresses. This has been an ongoing problem I haven't been able to get to the bottom of. I think something is not right. The second time I rebooted pfSense got IPv4 and IPv6 addresses. The pfSense time is correct, and logs indicate correct NTP function from the command line below:

    [2.4.4-RELEASE][admin@pfSense.****.com]/root: ntpq -p
         remote           refid      st t when poll reach   delay   offset  jitter
    ==============================================================================
     pool.ntp.org    .POOL.          16 p    -   64    0    0.000    0.000   0.000
     0.pfsense.pool. .POOL.          16 p    -   64    0    0.000    0.000   0.000
    *darwin.kenyonra 127.67.113.92    2 u   34   64   17   10.082   -2.230   1.710
    -138.68.46.177 ( 75.229.16.214    2 u    2   64   17    9.987    1.013   0.939
    +time.nullrouten 132.163.97.1     2 u   39   64    7    9.044   -3.925   1.900
    -199.102.46.78 ( .GPS.            1 u   35   64   17   61.247   -5.941   1.874
    -propjet.latt.ne 44.24.199.34     3 u    5   64   17    8.257   -1.943   1.932
    -ntp.backplanedn 152.2.133.52     2 u    2   64   37   73.067    2.159   3.191
    +srcf-ntp.stanfo 171.64.7.67      2 u    -   64   37    9.630   -3.785   3.360
    -four10.gac.edu  216.218.254.202  2 u    7   64   17   57.639   -2.478   2.003
    
    


  • And here is after I disabled the unneeded WAN port 123 access rule.

    [2.4.4-RELEASE][admin@pfSense.****.com]/root: ntpq -p
         remote           refid      st t when poll reach   delay   offset  jitter
    ==============================================================================
     pool.ntp.org    .POOL.          16 p    -   64    0    0.000    0.000   0.000
     0.pfsense.pool. .POOL.          16 p    -   64    0    0.000    0.000   0.000
    +darwin.kenyonra 127.67.113.92    2 u   39   64  377   10.082   -2.230   2.741
    -138.68.46.177 ( 75.229.16.214    2 u    6   64  377   10.215    1.595   1.244
    +time.nullrouten 132.163.97.1     2 u   40   64  177    9.150   -0.587   2.268
    -199.102.46.78 ( .GPS.            1 u   37   64  377   61.484   -4.489   1.951
    +propjet.latt.ne 44.24.199.34     3 u   13   64  377    8.634   -2.014   1.266
    -ntp.backplanedn 152.2.133.52     2 u    6   64  377   73.025    3.572   2.601
    *srcf-ntp.stanfo 171.64.7.67      2 u    4   64  377    9.997   -1.991   2.168
    -four10.gac.edu  216.218.254.202  2 u   10   64  377   57.894   -4.448   2.532
    
    


  • I've got a problem with this booting and pulling WAN addresses, maybe the time zone was a manifestation of the problem.

    Trimmed system logs for the appropriate times below. Any help identifying where to look for this unreliable behavior at startup, I would be most grateful.

    May 18 19:56:22 - power down and back on. This is not successful, doesn't get an address.

    May 23 16:04:55 - power down and back on, successfully gets WAN addresses.

    The log is attached as plain text.
    logs failed WAN address then successful sanitized.txt



  • What is THAT???

    May 23 16:04:39 pfSense php-fpm[82541]: /rc.newwanip: pfSense package system has detected an IP change or dynamic WAN reconnection - 76.126.xxx.xxx -> 192.168.100.10 - Restarting packages.

    Please post your wan interface configuration. Is it dhcp? Where did this 192.168.100.10 come from?
    Also describe your wan setup



  • @netblues

    LOL, thanks for sticking with me and sorry about the huge log, I tried to keep it down to the relevant events. Something is wrong, maybe the NTP time was just a symptom of problems elsewhere.

    pfSense WAN is Intel 1Gb Ethernet -> Netgear CM1000 cable modem -> Comcast, while the LAN is 10Gb SFP+ -> Ubiquiti US-16-XG switch

    Good catch on the 192.168.100.10 traffic. 76.126.xxx.xxx is pfSense WAN, 192.168.100.1 is the web GUI for the cable modem, so my guess it is the cable modem.



  • Do I need an "allow all" rule for the cable modem WAN? I don't recall any specific WAN configuration other than telling pfSense ixl2 physical interface, and IPv6 prefix delegation.



  • 0611924c-f65b-4dc8-bcdf-3e77ffeeaa1c-image.png
    bf45fe00-d313-480c-b3fd-f784160edb0b-image.png
    5f0f7c22-9f32-4cef-8249-35f7520e44ba-image.png
    0289fcdc-0bc8-471a-bd6f-2d2fe15e2fb4-image.png



  • I see I don't have prefix delegation on the WAN side checked. Even though I'm using it in the LAN. I've been over this setup before though, probably there is a reason it is unchecked. Will give this a try.

    0f680205-1e84-4222-af84-faf09e6d7ccc-image.png



  • Seemed to boot fine, but now pfSense has an internal-only IPv6!
    873f6029-8e13-4ac9-8e07-9dd2dfa21988-image.png

    The log seems much less busy, but there are still some errors at:
    May 24 13:13:44

    May 24 13:13:20 	rtsold 		Received RA specifying route fe80::201:5cff:fe65:1446 for interface wan(igb0)
    
    May 24 13:15:46 	php-fpm 	94357 	/index.php: Successful login for user 'admin' from: 2601:646:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx (Local Database)
    May 24 13:14:18 	login 		login on ttyv0 as root
    May 24 13:13:52 	check_reload_status 		Reloading filter
    May 24 13:13:52 	php-fpm 	94357 	/rc.newwanipv6: Removing static route for monitor fe80::201:5cff:fe65:1446 and adding a new route through fe80::201:5cff:fe65:1446%igb0
    May 24 13:13:52 	php-fpm 	94357 	/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 13:13:50 	dhcpleases 		Could not deliver signal HUP to process because its pidfile (/var/run/dnsmasq.pid) does not exist, No such process.
    May 24 13:13:50 	dhcpleases 		kqueue error: unknown
    May 24 13:13:50 	dhcpleases 		Could not deliver signal HUP to process because its pidfile (/var/run/dnsmasq.pid) does not exist, No such process.
    May 24 13:13:50 	dhcpleases 		/etc/hosts changed size from original!
    May 24 13:13:49 	php-fpm 	94357 	/rc.newwanipv6: rc.newwanipv6: on (IP address: fe80::225:90ff:feba:5364%igb0) (interface: wan) (real interface: igb0).
    May 24 13:13:49 	php-fpm 	94357 	/rc.newwanipv6: rc.newwanipv6: Info: starting on igb0.
    May 24 13:13:46 	php-fpm 	364 	[pfBlockerNG] Starting cron process.
    May 24 13:13:46 	php-fpm 	364 	/rc.start_packages: Restarting/Starting all packages.
    May 24 13:13:46 	kernel 		done.
    May 24 13:13:46 	syslogd 		kernel boot file is /boot/kernel/kernel
    May 24 13:13:46 	syslogd 		exiting on signal 15
    May 24 13:13:46 	kernel 		done.
    May 24 13:13:46 	php-cgi 		rc.bootup: Creating rrd update script
    May 24 13:13:45 	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 13:13:45 	php-fpm 	363 	/rc.dyndns.update: Dynamic DNS (pfsense.mydomain.com): running get_failover_interface for wan. found igb0
    May 24 13:13:45 	php-fpm 	363 	/rc.dyndns.update: Dynamic DNS: updatedns() starting
    May 24 13:13:44 	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 13:13:44 	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 13:13:44 	php-fpm 	363 	/rc.dyndns.update: Dynamic DNS godaddy (@.mydomain.com): 76.126.xxx.xxx extracted from local system.
    May 24 13:13:44 	php-fpm 	363 	/rc.dyndns.update: Dynamic DNS (@.mydomain.com): running get_failover_interface for wan. found igb0
    May 24 13:13:44 	php-fpm 	363 	/rc.dyndns.update: Dynamic DNS godaddy (@.mydomain.com): 76.126.xxx.xxx extracted from local system.
    May 24 13:13:44 	php-fpm 	363 	/rc.dyndns.update: Dynamic DNS: updatedns() starting
    May 24 13:13:44 	kernel 		done
    May 24 13:13:44 	kernel 		.done.
    May 24 13:13:43 	kernel 		..
    May 24 13:13:43 	kernel 		..
    May 24 13:13:43 	check_reload_status 		Updating all dyndns
    May 24 13:13:43 	kernel 		done.
    May 24 13:13:43 	kernel 		done.
    May 24 13:13:43 	php-cgi 		rc.bootup: NTPD is starting up.
    May 24 13:13:43 	kernel 		done.
    May 24 13:13:43 	kernel 		done.
    May 24 13:13:42 	kernel 		done.
    May 24 13:13:41 	kernel 		done.
    May 24 13:13: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 13:13:41 	php-cgi 		rc.bootup: Default gateway setting Interface WAN_DHCP Gateway as default.
    May 24 13:13:41 	kernel 		done.
    May 24 13:13:41 	kernel 		.done.
    May 24 13:13:41 	php-cgi 		rc.bootup: Removing static route for monitor fe80::201:5cff:fe65:1446 and adding a new route through fe80::201:5cff:fe65:1446%igb0
    May 24 13:13:40 	kernel 		....
    May 24 13:13:40 	kernel 		pflog0: promiscuous mode enabled
    May 24 13:13:40 	php-fpm 	364 	/rc.newwanip: Removing static route for monitor fe80::201:5cff:fe65:1446 and adding a new route through fe80::201:5cff:fe65:1446%igb0
    May 24 13:13:39 	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 13:13:20 	rtsold 		Starting dhcp6 client for interface wan(igb0)
    May 24 13:13:20 	rtsold 		Received RA specifying route fe80::201:5cff:fe65:1446 for interface wan(igb0)
    May 24 13:13:17 	php-cgi 		rc.bootup: Resyncing OpenVPN instances.
    May 24 13:13:17 	kernel 		ixl2: link state changed to UP
    May 24 13:13:17 	kernel 		ixl2: Link is up, 10 Gbps Full Duplex, Requested FEC: None, Negotiated FEC: None, Autoneg: False, Flow Control: None
    May 24 13:13:17 	check_reload_status 		Linkup starting ixl2
    May 24 13:13:16 	php-fpm 	364 	/rc.newwanip: rc.newwanip: on (IP address: 76.126.xxx.xxx) (interface: WAN[wan]) (real interface: igb0).
    May 24 13:13:16 	php-fpm 	364 	/rc.newwanip: rc.newwanip: Info: starting on igb0.
    May 24 13:13:15 	php-cgi 		rc.bootup: Starting rtsold process
    May 24 13:13:15 	php-cgi 		rc.bootup: Accept router advertisements on interface igb0
    May 24 13:13:15 	php-cgi 		rc.bootup: calling interface_dhcpv6_configure.
    May 24 13:13:15 	check_reload_status 		rc.newwanip starting igb0
    May 24 13:13:14 	kernel 		igb0: link state changed to UP
    May 24 13:13:14 	check_reload_status 		Linkup starting igb0
    May 24 13:13:12 	syslogd 		Logging subprocess 6907 (exec /usr/local/sbin/sshguard) exited due to signal 15.
    May 24 13:13:12 	sshd 	6677 	Server listening on 0.0.0.0 port 22614.
    May 24 13:13:12 	sshd 	6677 	Server listening on :: port 22614.
    May 24 13:13:10 	kernel 		aesni0: <AES-CBC,AES-XTS,AES-GCM,AES-ICM> on motherboard
    May 24 13:13:10 	kernel 		padlock0: No ACE support.
    May 24 13:13:10 	kernel 		TSC: P-state invariant, performance statistics
    May 24 13:13:10 	kernel 		VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID,VID,PostIntr
    May 24 13:13:10 	kernel 		XSAVE Features=0xf<XSAVEOPT,XSAVEC,XINUSE,XSAVES>
    May 24 13:13:10 	kernel 		Structured Extended Features3=0x9c002400<IBPB,STIBP,SSBD>
    May 24 13:13:10 	kernel 		Structured Extended Features2=0x8<PKU>
    May 24 13:13:10 	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 13:13:10 	kernel 		AMD Features2=0x121<LAHF,ABM,Prefetch>
    May 24 13:13:10 	kernel 		AMD Features=0x2c100800<SYSCALL,NX,Page1GB,RDTSCP,LM>
    May 24 13:13:10 	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 13:13:10 	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 13:13:10 	kernel 		Origin="GenuineIntel" Id=0x50654 Family=0x6 Model=0x55 Stepping=4
    May 24 13:13:10 	kernel 		CPU: Intel(R) Xeon(R) D-2123IT CPU @ 2.20GHz (2194.92-MHz K8-class CPU)
    May 24 13:13:10 	kernel 		random: unblocking device.
    May 24 13:13:10 	kernel 		Trying to mount root from zfs:zroot/ROOT/default []...
    May 24 13:13:10 	kernel 		ses0: SEMB SES Device
    May 24 13:13:10 	kernel 		ses0: <AHCI SGPIO Enclosure 1.00 0001> SEMB S-E-S 2.00 device
    May 24 13:13:10 	kernel 		ses0 at ahciem0 bus 0 scbus6 target 0 lun 0
    May 24 13:13:10 	kernel 		uhub3: 4 ports with 4 removable, self powered
    May 24 13:13:10 	kernel 		uhub3: MTT enabled
    May 24 13:13:10 	kernel 		uhub3: <vendor 0x05e3 USB2.0 Hub, class 9/0, rev 2.00/32.98, addr 4> on usbus0
    May 24 13:13:10 	kernel 		uhub3 numa-domain 0 on uhub2
    May 24 13:13:10 	kernel 		ugen0.5: <vendor 0x05e3 USB2.0 Hub> at usbus0
    May 24 13:13:10 	kernel 		uhub2: 4 ports with 4 removable, self powered
    May 24 13:13:10 	kernel 		uhub2: MTT enabled
    May 24 13:13:10 	kernel 		uhub2: <vendor 0x05e3 USB2.0 Hub, class 9/0, rev 2.00/32.98, addr 3> on usbus0
    May 24 13:13:10 	kernel 		uhub2 numa-domain 0 on uhub0
    May 24 13:13:10 	kernel 		ugen0.4: <vendor 0x05e3 USB2.0 Hub> at usbus0
    May 24 13:13:10 	kernel 		kbd2 at ukbd0
    May 24 13:13:10 	kernel 		ukbd0: <vendor 0x0557 product 0x2419, class 0/0, rev 1.10/1.00, addr 2> on usbus0
    May 24 13:13:10 	kernel 		ukbd0 numa-domain 0 on uhub1
    May 24 13:13:10 	kernel 		ugen0.3: <vendor 0x0557 product 0x2419> at usbus0
    May 24 13:13:10 	kernel 		uhub1: 4 ports with 3 removable, self powered
    May 24 13:13:10 	kernel 		uhub1: <vendor 0x0557 product 0x7000, class 9/0, rev 2.00/0.00, addr 1> on usbus0
    May 24 13:13:10 	kernel 		uhub1 numa-domain 0 on uhub0
    May 24 13:13:10 	kernel 		ugen0.2: <vendor 0x0557 product 0x7000> at usbus0
    May 24 13:13:10 	kernel 		uhub0: 26 ports with 26 removable, self powered
    May 24 13:13:10 	kernel 		nvd0: 476940MB (976773168 512 byte sectors)
    May 24 13:13:10 	kernel 		nvd0: <Samsung SSD 970 EVO 500GB> NVMe namespace
    May 24 13:13:10 	kernel 		uhub0: <0x8086 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0
    May 24 13:13:10 	kernel 		ugen0.1: <0x8086 XHCI root HUB> at usbus0
    May 24 13:13:10 	kernel 		Timecounters tick every 1.000 msec
    May 24 13:13:10 	kernel 		ZFS storage pool version: features support (5000)
    May 24 13:13:10 	kernel 		ZFS filesystem version: 5
    May 24 13:13:10 	kernel 		est7: <Enhanced SpeedStep Frequency Control> numa-domain 0 on cpu7
    May 24 13:13:10 	kernel 		est6: <Enhanced SpeedStep Frequency Control> numa-domain 0 on cpu6
    May 24 13:13:10 	kernel 		est5: <Enhanced SpeedStep Frequency Control> numa-domain 0 on cpu5
    May 24 13:13:10 	kernel 		est4: <Enhanced SpeedStep Frequency Control> numa-domain 0 on cpu4
    May 24 13:13:10 	kernel 		est3: <Enhanced SpeedStep Frequency Control> numa-domain 0 on cpu3
    May 24 13:13:10 	kernel 		est2: <Enhanced SpeedStep Frequency Control> numa-domain 0 on cpu2
    May 24 13:13:10 	kernel 		est1: <Enhanced SpeedStep Frequency Control> numa-domain 0 on cpu1
    May 24 13:13:10 	kernel 		est0: <Enhanced SpeedStep Frequency Control> numa-domain 0 on cpu0
    May 24 13:13:10 	kernel 		ppc0: cannot reserve I/O port range
    May 24 13:13:10 	kernel 		orm0: <ISA Option ROM> at iomem 0xc0000-0xc7fff on isa0
    May 24 13:13:10 	kernel 		uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0
    May 24 13:13:10 	kernel 		uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
    May 24 13:13:10 	kernel 		pci9: <dasp, performance counters> at device 18.1 (no driver attached)
    May 24 13:13:10 	kernel 		pci9: <dasp, performance counters> at device 18.0 (no driver attached)
    May 24 13:13:10 	kernel 		ixl3: netmap queues/slots: TX 8/1024, RX 8/1024
    May 24 13:13:10 	kernel 		queues is 0xfffffe00018ee000
    May 24 13:13:10 	kernel 		ixl3: SR-IOV ready
    May 24 13:13:10 	kernel 		ixl3: Ethernet address: 00:25:90:bb:bf:0d
    May 24 13:13:10 	kernel 		ixl3: Allocating 8 queues for PF LAN VSI; 8 queues active
    May 24 13:13:10 	kernel 		ixl3: Using MSIX interrupts with 9 vectors
    May 24 13:13:10 	kernel 		ixl3: PF-ID[3]: VFs 32, MSIX 129, VF MSIX 5, QPs 384, I2C
    May 24 13:13:10 	kernel 		ixl3: fw 3.1.57069 api 1.5 nvm 3.33 etid 80001006 oem 1.262.0
    May 24 13:13:10 	kernel 		ixl3: using 1024 tx descriptors and 1024 rx descriptors
    May 24 13:13:10 	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 13:13:10 	kernel 		ixl2: netmap queues/slots: TX 8/1024, RX 8/1024
    May 24 13:13:10 	kernel 		queues is 0xfffffe00017a0000
    May 24 13:13:10 	kernel 		ixl2: SR-IOV ready
    May 24 13:13:10 	kernel 		ixl2: Ethernet address: 00:25:90:bb:bf:0c
    May 24 13:13:10 	kernel 		ixl2: Allocating 8 queues for PF LAN VSI; 8 queues active
    May 24 13:13:10 	kernel 		ixl2: Using MSIX interrupts with 9 vectors
    May 24 13:13:10 	kernel 		ixl2: PF-ID[2]: VFs 32, MSIX 129, VF MSIX 5, QPs 384, I2C
    May 24 13:13:10 	kernel 		ixl2: fw 3.1.57069 api 1.5 nvm 3.33 etid 80001006 oem 1.262.0
    May 24 13:13:10 	kernel 		ixl2: using 1024 tx descriptors and 1024 rx descriptors
    May 24 13:13:10 	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 13:13:10 	kernel 		ixl1: netmap queues/slots: TX 8/1024, RX 8/1024
    May 24 13:13:10 	kernel 		queues is 0xfffffe0001664000
    May 24 13:13:10 	kernel 		ixl1: SR-IOV ready
    May 24 13:13:10 	kernel 		ixl1: Ethernet address: 00:25:90:bb:bf:0b
    May 24 13:13:10 	kernel 		ixl1: Allocating 8 queues for PF LAN VSI; 8 queues active
    May 24 13:13:10 	kernel 		ixl1: Using MSIX interrupts with 9 vectors
    May 24 13:13:10 	kernel 		ixl1: PF-ID[1]: VFs 32, MSIX 129, VF MSIX 5, QPs 384, MDIO shared
    May 24 13:13:10 	kernel 		ixl1: fw 3.1.57069 api 1.5 nvm 3.33 etid 80001006 oem 1.262.0
    May 24 13:13:10 	kernel 		ixl1: using 1024 tx descriptors and 1024 rx descriptors
    May 24 13:13:10 	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 13:13:10 	kernel 		ixl0: netmap queues/slots: TX 8/1024, RX 8/1024
    May 24 13:13:10 	kernel 		queues is 0xfffffe0001528000
    May 24 13:13:10 	kernel 		ixl0: SR-IOV ready
    May 24 13:13:10 	kernel 		ixl0: Ethernet address: 00:25:90:bb:bf:0a
    May 24 13:13:10 	kernel 		ixl0: Allocating 8 queues for PF LAN VSI; 8 queues active
    May 24 13:13:10 	kernel 		ixl0: Using MSIX interrupts with 9 vectors
    May 24 13:13:10 	kernel 		ixl0: PF-ID[0]: VFs 32, MSIX 129, VF MSIX 5, QPs 384, MDIO shared
    May 24 13:13:10 	kernel 		ixl0: fw 3.1.57069 api 1.5 nvm 3.33 etid 80001006 oem 1.262.0
    May 24 13:13:10 	kernel 		ixl0: using 1024 tx descriptors and 1024 rx descriptors
    May 24 13:13:10 	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 13:13:10 	kernel 		pci12: <ACPI PCI bus> numa-domain 0 on pcib12
    May 24 13:13:10 	kernel 		pcib12: <ACPI PCI-PCI bridge> irq 40 at device 3.0 numa-domain 0 on pci11
    May 24 13:13:10 	kernel 		pci11: <ACPI PCI bus> numa-domain 0 on pcib11
    May 24 13:13:10 	kernel 		pcib11: <ACPI PCI-PCI bridge> mem 0xfbe00000-0xfbe1ffff irq 48 at device 0.0 numa-domain 0 on pci10
    May 24 13:13:10 	kernel 		pci10: <ACPI PCI bus> numa-domain 0 on pcib10
    May 24 13:13:10 	kernel 		pcib10: <ACPI PCI-PCI bridge> irq 55 at device 0.0 numa-domain 0 on pci9
    May 24 13:13:10 	kernel 		pci9: <ACPI PCI bus> numa-domain 0 on pcib9
    May 24 13:13:10 	kernel 		pcib9: _OSC returned error 0x10
    May 24 13:13:10 	kernel 		pcib9: <ACPI Host-PCI bridge> numa-domain 0 on acpi0
    May 24 13:13:10 	kernel 		igb3: netmap queues/slots: TX 8/1024, RX 8/1024
    May 24 13:13:10 	kernel 		igb3: Bound queue 7 to cpu 7
    May 24 13:13:10 	kernel 		igb3: Bound queue 6 to cpu 6
    May 24 13:13:10 	kernel 		igb3: Bound queue 5 to cpu 5
    May 24 13:13:10 	kernel 		igb3: Bound queue 4 to cpu 4
    May 24 13:13:10 	kernel 		igb3: Bound queue 3 to cpu 3
    May 24 13:13:10 	kernel 		igb3: Bound queue 2 to cpu 2
    May 24 13:13:10 	kernel 		igb3: Bound queue 1 to cpu 1
    May 24 13:13:10 	kernel 		igb3: Bound queue 0 to cpu 0
    May 24 13:13:10 	kernel 		igb3: Ethernet address: 00:25:90:ba:53:67
    May 24 13:13:10 	kernel 		igb3: Using MSIX interrupts with 9 vectors
    May 24 13:13:10 	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 13:13:10 	kernel 		igb2: netmap queues/slots: TX 8/1024, RX 8/1024
    May 24 13:13:10 	kernel 		igb2: Bound queue 7 to cpu 7
    May 24 13:13:10 	kernel 		igb2: Bound queue 6 to cpu 6
    May 24 13:13:10 	kernel 		igb2: Bound queue 5 to cpu 5
    May 24 13:13:10 	kernel 		igb2: Bound queue 4 to cpu 4
    May 24 13:13:10 	kernel 		igb2: Bound queue 3 to cpu 3
    May 24 13:13:10 	kernel 		igb2: Bound queue 2 to cpu 2
    May 24 13:13:10 	kernel 		igb2: Bound queue 1 to cpu 1
    May 24 13:13:10 	kernel 		igb2: Bound queue 0 to cpu 0
    May 24 13:13:10 	kernel 		igb2: Ethernet address: 00:25:90:ba:53:66
    May 24 13:13:10 	kernel 		igb2: Using MSIX interrupts with 9 vectors
    May 24 13:13:10 	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 13:13:10 	kernel 		igb1: netmap queues/slots: TX 8/1024, RX 8/1024
    May 24 13:13:10 	kernel 		igb1: Bound queue 7 to cpu 7
    May 24 13:13:10 	kernel 		igb1: Bound queue 6 to cpu 6
    May 24 13:13:10 	kernel 		igb1: Bound queue 5 to cpu 5
    May 24 13:13:10 	kernel 		igb1: Bound queue 4 to cpu 4
    May 24 13:13:10 	kernel 		igb1: Bound queue 3 to cpu 3
    May 24 13:13:10 	kernel 		igb1: Bound queue 2 to cpu 2
    May 24 13:13:10 	kernel 		igb1: Bound queue 1 to cpu 1
    May 24 13:13:10 	kernel 		igb1: Bound queue 0 to cpu 0
    May 24 13:13:10 	kernel 		igb1: Ethernet address: 00:25:90:ba:53:65
    May 24 13:13:10 	kernel 		igb1: Using MSIX interrupts with 9 vectors
    May 24 13:13:10 	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 13:13:10 	kernel 		igb0: netmap queues/slots: TX 8/1024, RX 8/1024
    May 24 13:13:10 	kernel 		igb0: Bound queue 7 to cpu 7
    May 24 13:13:10 	kernel 		igb0: Bound queue 6 to cpu 6
    May 24 13:13:10 	kernel 		igb0: Bound queue 5 to cpu 5
    May 24 13:13:10 	kernel 		igb0: Bound queue 4 to cpu 4
    May 24 13:13:10 	kernel 		igb0: Bound queue 3 to cpu 3
    May 24 13:13:10 	kernel 		igb0: Bound queue 2 to cpu 2
    May 24 13:13:10 	kernel 		igb0: Bound queue 1 to cpu 1
    May 24 13:13:10 	kernel 		igb0: Bound queue 0 to cpu 0
    May 24 13:13:10 	kernel 		igb0: Ethernet address: 00:25:90:ba:53:64
    May 24 13:13:10 	kernel 		igb0: Using MSIX interrupts with 9 vectors
    May 24 13:13:10 	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 13:13:10 	kernel 		pci8: <ACPI PCI bus> numa-domain 0 on pcib8
    May 24 13:13:10 	kernel 		pcib8: <ACPI PCI-PCI bridge> irq 47 at device 3.0 numa-domain 0 on pci6
    May 24 13:13:10 	kernel 		nvme0: <Generic NVMe Device> mem 0xe0e00000-0xe0e03fff irq 42 at device 0.0 numa-domain 0 on pci7
    May 24 13:13:10 	kernel 		pci7: <ACPI PCI bus> numa-domain 0 on pcib7
    May 24 13:13:10 	kernel 		pcib7: <ACPI PCI-PCI bridge> irq 47 at device 2.0 numa-domain 0 on pci6
    May 24 13:13:10 	kernel 		pci6: <ACPI PCI bus> numa-domain 0 on pcib6
    May 24 13:13:10 	kernel 		pcib6: _OSC returned error 0x10
    May 24 13:13:10 	kernel 		pcib6: <ACPI Host-PCI bridge> numa-domain 0 on acpi0
    May 24 13:13:10 	kernel 		pci5: <ACPI PCI bus> numa-domain 0 on pcib5
    May 24 13:13:10 	kernel 		pcib5: _OSC returned error 0x10
    May 24 13:13:10 	kernel 		pcib5: <ACPI Host-PCI bridge> numa-domain 0 on acpi0
    May 24 13:13:10 	kernel 		pci0: <serial bus> at device 31.5 (no driver attached)
    May 24 13:13:10 	kernel 		pci0: <memory> at device 31.2 (no driver attached)
    May 24 13:13:10 	kernel 		isa0: <ISA bus> numa-domain 0 on isab0
    May 24 13:13:10 	kernel 		isab0: <PCI-ISA bridge> at device 31.0 numa-domain 0 on pci0
    May 24 13:13:10 	kernel 		pci4: <ACPI PCI bus> numa-domain 0 on pcib4
    May 24 13:13:10 	kernel 		pcib4: <ACPI PCI-PCI bridge> irq 16 at device 29.0 numa-domain 0 on pci0
    May 24 13:13:10 	kernel 		vgapci0: Boot video device
    May 24 13:13:10 	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 13:13:10 	kernel 		pci3: <ACPI PCI bus> numa-domain 0 on pcib3
    May 24 13:13:10 	kernel 		pcib3: <ACPI PCI-PCI bridge> irq 16 at device 0.0 numa-domain 0 on pci2
    May 24 13:13:10 	kernel 		pci2: <ACPI PCI bus> numa-domain 0 on pcib2
    May 24 13:13:10 	kernel 		pcib2: <ACPI PCI-PCI bridge> irq 16 at device 28.4 numa-domain 0 on pci0
    May 24 13:13:10 	kernel 		pci1: <ACPI PCI bus> numa-domain 0 on pcib1
    May 24 13:13:10 	kernel 		pcib1: <ACPI PCI-PCI bridge> irq 16 at device 28.0 numa-domain 0 on pci0
    May 24 13:13:10 	kernel 		pci0: <simple comms> at device 22.4 (no driver attached)
    May 24 13:13:10 	kernel 		pci0: <simple comms> at device 22.1 (no driver attached)
    May 24 13:13:10 	kernel 		pci0: <simple comms> at device 22.0 (no driver attached)
    May 24 13:13:10 	kernel 		usbus0: 5.0Gbps Super Speed USB v3.0
    May 24 13:13:10 	kernel 		usbus0 numa-domain 0 on xhci0
    May 24 13:13:10 	kernel 		xhci_interrupt: host controller halted
    May 24 13:13:10 	kernel 		usbus0: waiting for BIOS to give up control
    May 24 13:13:10 	kernel 		xhci0: 32 bytes context size, 64-bit DMA
    May 24 13:13:10 	kernel 		xhci0: <Intel Lewisburg USB 3.0 controller> mem 0xaa180000-0xaa18ffff irq 16 at device 20.0 numa-domain 0 on pci0
    May 24 13:13:10 	kernel 		ahciem0: <AHCI enclosure management bridge> on ahci0
    May 24 13:13:10 	kernel 		ahcich5: <AHCI channel> at channel 5 on ahci0
    May 24 13:13:10 	kernel 		ahcich4: <AHCI channel> at channel 4 on ahci0
    May 24 13:13:10 	kernel 		ahcich3: <AHCI channel> at channel 3 on ahci0
    May 24 13:13:10 	kernel 		ahcich2: <AHCI channel> at channel 2 on ahci0
    May 24 13:13:10 	kernel 		ahcich1: <AHCI channel> at channel 1 on ahci0
    May 24 13:13:10 	kernel 		ahcich0: <AHCI channel> at channel 0 on ahci0
    May 24 13:13:10 	kernel 		ahci0: AHCI v1.31 with 6 6Gbps ports, Port Multiplier not supported
    May 24 13:13:10 	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 13:13:10 	kernel 		pci0: <unknown> at device 17.1 (no driver attached)
    May 24 13:13:10 	kernel 		pci0: <unknown> at device 17.0 (no driver attached)
    May 24 13:13:10 	kernel 		pci0: <dasp, performance counters> at device 8.1 (no driver attached)
    May 24 13:13:10 	kernel 		pci0: <ACPI PCI bus> numa-domain 0 on pcib0
    May 24 13:13:10 	kernel 		pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff numa-domain 0 on acpi0
    May 24 13:13:10 	kernel 		acpi_syscontainer0: <System Container> on acpi0
    May 24 13:13:10 	kernel 		acpi_timer0: <24-bit timer at 3.579545MHz> port 0x508-0x50b on acpi0
    May 24 13:13:10 	kernel 		Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
    May 24 13:13:10 	kernel 		device_attach: hpet1 attach returned 12
    May 24 13:13:10 	kernel 		hpet1: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
    May 24 13:13:10 	kernel 		Event timer "HPET" frequency 24000000 Hz quality 550
    May 24 13:13:10 	kernel 		Timecounter "HPET" frequency 24000000 Hz quality 950
    May 24 13:13:10 	kernel 		hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
    May 24 13:13:10 	kernel 		Event timer "i8254" frequency 1193182 Hz quality 100
    May 24 13:13:10 	kernel 		Timecounter "i8254" frequency 1193182 Hz quality 0
    May 24 13:13:10 	kernel 		attimer0: <AT timer> port 0x40-0x43,0x50-0x53 irq 0 on acpi0
    May 24 13:13:10 	kernel 		Event timer "RTC" frequency 32768 Hz quality 0
    May 24 13:13:10 	kernel 		atrtc0: registered as a time-of-day clock, resolution 1.000000s
    May 24 13:13:10 	kernel 		atrtc0: <AT realtime clock> port 0x70-0x71,0x74-0x77 irq 8 on acpi0
    May 24 13:13:10 	kernel 		cpu7: <ACPI CPU> numa-domain 0 on acpi0
    May 24 13:13:10 	kernel 		cpu6: <ACPI CPU> numa-domain 0 on acpi0
    May 24 13:13:10 	kernel 		cpu5: <ACPI CPU> numa-domain 0 on acpi0
    May 24 13:13:10 	kernel 		cpu4: <ACPI CPU> numa-domain 0 on acpi0
    May 24 13:13:10 	kernel 		cpu3: <ACPI CPU> numa-domain 0 on acpi0
    May 24 13:13:10 	kernel 		cpu2: <ACPI CPU> numa-domain 0 on acpi0
    May 24 13:13:10 	kernel 		cpu1: <ACPI CPU> numa-domain 0 on acpi0
    May 24 13:13:10 	kernel 		cpu0: <ACPI CPU> numa-domain 0 on acpi0
    May 24 13:13:10 	kernel 		acpi0: Power Button (fixed)
    May 24 13:13:10 	kernel 		acpi0: <SUPERM SUPERM> on motherboard
    May 24 13:13:10 	kernel 		padlock0: No ACE support.
    May 24 13:13:10 	kernel 		cryptosoft0: <software crypto> on motherboard
    May 24 13:13:10 	kernel 		nexus0
    May 24 13:13:10 	kernel 		random: fast provider: "Intel Secure Key RNG"
    May 24 13:13:10 	kernel 		random: registering fast source Intel Secure Key RNG
    May 24 13:13:10 	kernel 		module_register_init: MOD_LOAD (vesa, 0xffffffff8120aaa0, 0) error 19
    May 24 13:13:10 	kernel 		netmap: loaded module
    May 24 13:13:10 	kernel 		kbd1 at kbdmux0
    May 24 13:13:10 	kernel 		wlan: mac acl policy registered
    May 24 13:13:10 	kernel 		module_register_init: MOD_LOAD (iwi_monitor_fw, 0xffffffff806a85c0, 0) error 1
    May 24 13:13:10 	kernel 		iwi_monitor: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
    May 24 13:13:10 	kernel 		iwi_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi.LICENSE.
    May 24 13:13:10 	kernel 		module_register_init: MOD_LOAD (iwi_ibss_fw, 0xffffffff806a8510, 0) error 1
    May 24 13:13:10 	kernel 		iwi_ibss: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
    May 24 13:13:10 	kernel 		iwi_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi.LICENSE.
    May 24 13:13:10 	kernel 		module_register_init: MOD_LOAD (iwi_bss_fw, 0xffffffff806a8460, 0) error 1
    May 24 13:13:10 	kernel 		iwi_bss: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
    May 24 13:13:10 	kernel 		iwi_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi.LICENSE.
    May 24 13:13:10 	kernel 		module_register_init: MOD_LOAD (ipw_monitor_fw, 0xffffffff80681590, 0) error 1
    May 24 13:13:10 	kernel 		ipw_monitor: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
    May 24 13:13:10 	kernel 		ipw_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw.LICENSE.
    May 24 13:13:10 	kernel 		module_register_init: MOD_LOAD (ipw_ibss_fw, 0xffffffff806814e0, 0) error 1
    May 24 13:13:10 	kernel 		ipw_ibss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
    May 24 13:13:10 	kernel 		ipw_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw.LICENSE.
    May 24 13:13:10 	kernel 		random: entropy device external interface
    May 24 13:13:10 	kernel 		module_register_init: MOD_LOAD (ipw_bss_fw, 0xffffffff80681430, 0) error 1
    May 24 13:13:10 	kernel 		ipw_bss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
    May 24 13:13:10 	kernel 		ipw_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw.LICENSE.
    May 24 13:13:10 	kernel 		Timecounter "TSC-low" frequency 1097459581 Hz quality 1000
    May 24 13:13:10 	kernel 		SMP: AP CPU #3 Launched!
    May 24 13:13:10 	kernel 		SMP: AP CPU #5 Launched!
    May 24 13:13:10 	kernel 		SMP: AP CPU #7 Launched!
    May 24 13:13:10 	kernel 		SMP: AP CPU #6 Launched!
    May 24 13:13:10 	kernel 		SMP: AP CPU #2 Launched!
    May 24 13:13:10 	kernel 		SMP: AP CPU #4 Launched!
    May 24 13:13:10 	kernel 		SMP: AP CPU #1 Launched!
    May 24 13:13:10 	kernel 		ioapic4 <Version 2.0> irqs 48-55 on motherboard
    May 24 13:13:10 	kernel 		ioapic3 <Version 2.0> irqs 40-47 on motherboard
    May 24 13:13:10 	kernel 		ioapic2 <Version 2.0> irqs 32-39 on motherboard
    May 24 13:13:10 	kernel 		ioapic1 <Version 2.0> irqs 24-31 on motherboard
    May 24 13:13:10 	kernel 		ioapic0 <Version 2.0> irqs 0-23 on motherboard
    May 24 13:13:10 	kernel 		FreeBSD/SMP: 1 package(s) x 4 core(s) x 2 hardware threads
    May 24 13:13:10 	kernel 		FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs
    May 24 13:13:10 	kernel 		ACPI APIC Table: <SUPERM SMCI--MB>
    May 24 13:13:10 	kernel 		Event timer "LAPIC" quality 600
    May 24 13:13:10 	kernel 		avail memory = 32890949632 (31367 MB)
    May 24 13:13:10 	kernel 		real memory = 34359738368 (32768 MB)
    May 24 13:13:10 	kernel 		TSC: P-state invariant, performance statistics
    May 24 13:13:10 	kernel 		VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID,VID,PostIntr
    May 24 13:13:10 	kernel 		XSAVE Features=0xf<XSAVEOPT,XSAVEC,XINUSE,XSAVES>
    May 24 13:13:10 	kernel 		Structured Extended Features3=0x9c002400<IBPB,STIBP,SSBD>
    May 24 13:13:10 	kernel 		Structured Extended Features2=0x8<PKU>
    May 24 13:13:10 	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 13:13:10 	kernel 		AMD Features2=0x121<LAHF,ABM,Prefetch>
    May 24 13:13:10 	kernel 		AMD Features=0x2c100800<SYSCALL,NX,Page1GB,RDTSCP,LM>
    May 24 13:13:10 	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 13:13:10 	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 13:13:10 	kernel 		Origin="GenuineIntel" Id=0x50654 Family=0x6 Model=0x55 Stepping=4
    May 24 13:13:10 	kernel 		CPU: Intel(R) Xeon(R) D-2123IT CPU @ 2.20GHz (2194.92-MHz K8-class CPU)
    May 24 13:13:10 	kernel 		VT(efifb): resolution 1024x768
    May 24 13:13:10 	kernel 		FreeBSD clang version 6.0.0 (tags/RELEASE_600/final 326565) (based on LLVM 6.0.0)
    May 24 13:13:10 	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 13:13:10 	kernel 		FreeBSD 11.2-RELEASE-p10 #9 4a2bfdce133(RELENG_2_4_4): Wed May 15 18:54:42 EDT 2019
    May 24 13:13:10 	kernel 		FreeBSD is a registered trademark of The FreeBSD Foundation.
    May 24 13:13:10 	kernel 		The Regents of the University of California. All rights reserved.
    May 24 13:13:10 	kernel 		Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
    May 24 13:13:10 	kernel 		Copyright (c) 1992-2018 The FreeBSD Project.
    May 24 13:13:10 	syslogd 		kernel boot file is /boot/kernel/kernel
    May 24 13:11:03 	syslogd 		exiting on signal 15
    May 24 13:11:03 	reboot 		rebooted by root
    May 24 13:11:01 	php-fpm 	58652 	/diag_reboot.php: Stopping all packages.
    


  • Dynamic DNS update of GoDaddy's API for IPv6 is failing also. Going to go back to DHCP on the WAN instead prefix delegation. I guess pfSense still provides IPv6 based on the external prefix, as I can access my server externally with mydomain.com pointed to the server GUA address.

    0813d21d-f6a0-4197-af11-0805fc669877-image.png



  • 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:
    


  • 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,



  • @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.


  • LAYER 8 Global Moderator

    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.



  • @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.



  • @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.



  • @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.


  • LAYER 8 Global Moderator

    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.



  • 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 
    

Log in to reply