OPNsense Forum

Archive => 19.7 Legacy Series => Topic started by: bimmerdriver on February 09, 2019, 05:44:28 am

Title: Problem building 19.7a
Post by: bimmerdriver on February 09, 2019, 05:44:28 am
I'm currently running 19.7a_39. Trying to update but can't get make upgrade to complete.

Here is the shell output:

Code: [Select]
root@OPNsense:/usr # rm -rf core
root@OPNsense:/usr # opnsense-code core
Cloning into '/usr/core'...
remote: Enumerating objects: 189, done.
remote: Counting objects: 100% (189/189), done.
remote: Compressing objects: 100% (124/124), done.
remote: Total 120845 (delta 101), reused 119 (delta 57), pack-reused 120656
Receiving objects: 100% (120845/120845), 64.08 MiB | 2.04 MiB/s, done.
Resolving deltas: 100% (86578/86578), done.
root@OPNsense:/usr # cd core
root@OPNsense:/usr/core # make upgrade
pkg: No package(s) matching squid
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
All repositories are up to date.
pkg: No packages available to install matching 'squid' have been found in the repositories
*** Error code 70

Stop.
make: stopped in /usr/core
root@OPNsense:/usr/core #

Any suggestions?
Title: Re: Problem building 19.7a
Post by: newsense on February 09, 2019, 07:11:52 am
A bit soon to be talking about 19.7 alpha problems ? There isn't even a dedicated forum for it and the production one is not the ideal venue :)
Title: Re: Problem building 19.7a
Post by: opnsenseuser on February 09, 2019, 10:42:48 am
I'm currently running 19.7a_39. Trying to update but can't get make upgrade to complete.

Here is the shell output:

Code: [Select]
root@OPNsense:/usr # rm -rf core
root@OPNsense:/usr # opnsense-code core
Cloning into '/usr/core'...
remote: Enumerating objects: 189, done.
remote: Counting objects: 100% (189/189), done.
remote: Compressing objects: 100% (124/124), done.
remote: Total 120845 (delta 101), reused 119 (delta 57), pack-reused 120656
Receiving objects: 100% (120845/120845), 64.08 MiB | 2.04 MiB/s, done.
Resolving deltas: 100% (86578/86578), done.
root@OPNsense:/usr # cd core
root@OPNsense:/usr/core # make upgrade
pkg: No package(s) matching squid
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
All repositories are up to date.
pkg: No packages available to install matching 'squid' have been found in the repositories
*** Error code 70

Stop.
make: stopped in /usr/core
root@OPNsense:/usr/core #

Any suggestions?

I have the same problem.
Title: Re: Problem building 19.7a
Post by: mimugmail on February 09, 2019, 12:54:44 pm
You have to wait until squid pkg is built. If you feel brave to run devel code you should also follow every repo to understand whats going on
Title: Re: Problem building 19.7a
Post by: bimmerdriver on February 09, 2019, 07:22:22 pm
You have to wait until squid pkg is built. If you feel brave to run devel code you should also follow every repo to understand whats going on
Thanks, that's all I need to know. I'm running it on a VM guest, so it's throw a throw-away if something bad happens.
Title: Re: Problem building 19.7a
Post by: mimugmail on February 09, 2019, 07:34:44 pm
Franco switched packages to Squid 4, but it's Not yet build in repo .. when you chase all commits you'll see it ;)
Title: Re: Problem building 19.7a
Post by: franco on February 10, 2019, 11:08:17 am
# make upgrade CORE_SQUID=3


Cheers,
Franco
Title: Re: Problem building 19.7a
Post by: bimmerdriver on February 10, 2019, 06:13:45 pm
# make upgrade CORE_SQUID=3
That did the trick. Now running 19.7.a_70.
Title: Re: Problem building 19.7a
Post by: hgeorge123 on February 15, 2019, 02:52:11 am
hello is planned in this version include some dansguardian style tool or acl to proxy to create rules by user group or ip?
Title: Re: Problem building 19.7a
Post by: mimugmail on February 15, 2019, 05:29:18 am
There is a plugin for acl available, have you checked it?
Title: Re: Problem building 19.7a
Post by: bimmerdriver on February 24, 2019, 06:43:23 pm
I updated this morning, after a couple of weeks of being away. The version is OPNsense 19.7.a_156-amd64. The configd service will not start and I cannot log into root on the console. It says the password is incorrect. Does anyone have a suggestion how to get around the login problem?
Title: Re: Problem building 19.7a
Post by: franco on February 24, 2019, 07:44:06 pm
Pull again, see https://github.com/opnsense/core/commit/91be9a6974 for discussion and fix.


Cheers,
Franco
Title: Re: Problem building 19.7a
Post by: bimmerdriver on February 26, 2019, 08:28:09 pm
Thank you for the help. It was not possible to login using the console, but I was able to get in using SSH. From there, I did another pull and was able to build the latest version. The console is still not working properly, however. When I attempt to login, it says "Login incorrect". It works fine using SSH.
Title: Re: Problem building 19.7a
Post by: franco on February 27, 2019, 12:20:28 am
Sounds like an issue with the PAM rework going on, let me check tomorrow.  :)
Title: Re: Problem building 19.7a
Post by: franco on February 27, 2019, 07:32:41 am
Confirmed. A fix should hit master some time later today.


Cheers,
Franco
Title: Re: Problem building 19.7a
Post by: bimmerdriver on February 28, 2019, 03:27:09 am
It's fixed.
Title: Re: Problem building 19.7a
Post by: franco on February 28, 2019, 09:08:44 pm
Yes, the new PAM stuff is all sorted now.


Cheers,
Franco
Title: Re: Problem building 19.7a
Post by: opnsenseuser on March 06, 2019, 05:28:49 pm
problem "make upgrade"

Code: [Select]
pkg: No package(s) matching php71-phpseclib
Code: [Select]
pkg: No packages available to install matching 'php71-phpseclib' have been found
Title: Re: Problem building 19.7a
Post by: franco on March 06, 2019, 05:29:52 pm
You guys need to wait for new releases sometimes... we can't always have master ready for use... or just change the makefile... but please don't always report it.
Title: Re: Problem building 19.7a
Post by: opnsenseuser on March 07, 2019, 09:08:33 am
sorry franco.

i thought we might have to use a particular parameter or switch again just like the squid problematic recently.

from now on I'll always wait a few days to post something. thanks,

best regards, rene :(
Title: Re: Problem building 19.7a
Post by: franco on March 07, 2019, 09:30:25 pm
Apologies, it has been a taxing week trying to balance a 19.1.3 release on top of discussions and the day job...

19.1.3 is out in a few minutes and phpseclib package will be available then.


Cheers,
Franco
Title: Re: Problem building 19.7a
Post by: bimmerdriver on March 09, 2019, 08:11:34 pm
problem "make upgrade"

Code: [Select]
pkg: No package(s) matching php71-phpseclib
Code: [Select]
pkg: No packages available to install matching 'php71-phpseclib' have been found
I'm using hyper-v, so I can easily checkpoint a VM and revert if there is a problem. I tried building the latest version. The same error occurred, but make completed, so I rebooted and gave it a try. It seems to work fine.
Title: Re: Problem building 19.7a
Post by: franco on March 17, 2019, 12:11:13 pm
The switch to PHP 7.2 happens some time next week. To upgrade before packages are in sync use:

# make upgrade CORE_PHP=71

Unfortunately we can't do hybrid environments of PHP 7.1 and 7.2 because there are upgrade bugs in the FreeBSD package tool being utterly confused by the choices.


Cheers,
Franco
Title: Re: Problem building 19.7a
Post by: bimmerdriver on March 17, 2019, 05:28:48 pm
Thank you for the heads-up.

I'm noticing that opnsense-update updates opnsense-devel from 19.7.a_272 to 19.7.a_288, but make-upgrade reverses it. Everything is working fine, otherwise. Is this expected behaviour?
Title: Re: Problem building 19.7a
Post by: franco on March 18, 2019, 08:53:03 am
opnsense-update operates on packages mirror which are synched with every release. The corresponding devel version in 19.1.4 is 19.7.a_288. The master branch of core.git is currently at 19.7.a_363.

"make upgrade" doesn't reverse opnsense-update, it merely installs whatever checked out version of core.git you want it to upgrade to (git describe).

opnsense-update on the other hand only forward-updates.

So what you are seeing is normal: you actually downgrade using make upgrade from 288 -> 272 so opnsense-update will bring you back to 288. If you upgrade to 363 then opnsense-update will not bring you back to 288. :)

Use git-pull or opnsense-code to update your core repository. I guess the full sequence is this then:

# opnsense-update; opnsense-code core; make upgrade


Cheers,
Franco
Title: Re: Problem building 19.7a
Post by: bimmerdriver on March 18, 2019, 08:27:32 pm
Hi Franco,

Thank you very much for the explanation. I know you're busy. I really appreciate that you took the time to respond.

BR,
BD
Title: Re: Problem building 19.7a
Post by: franco on March 18, 2019, 08:38:17 pm
Hi BD,

No problem. :)

BTW, the PHP 7.2 change is in effect. The packages for PHP 7.2 will be released next week with 19.1.5.


Cheers,
Franco
Title: Re: Problem building 19.7a
Post by: bimmerdriver on March 19, 2019, 03:39:38 am
Just rebuilt successfully. Now running OPNsense 19.7.a_368-amd64.
Title: Re: Problem building 19.7a
Post by: bimmerdriver on April 06, 2019, 07:31:05 pm
Just finished a successful build with the new 7.2 packages.
Title: Re: Problem building 19.7a
Post by: bimmerdriver on April 14, 2019, 06:17:00 pm
Updated from OPNsense 19.7.a_555-amd64 to OPNsense 19.7.a_561-amd64 this morning. There was an error after rebooting, which I reported. The update also broke IPv6.

Reverted to OPNsense 19.7.a_555-amd64. There was also an error after rebooting, which I reported, but IPv6 was working. Not sure how I missed the error after rebooting when I previously upgraded to OPNsense 19.7.a_555-amd64.

Reverted to OPNsense 19.7.a_516-amd64. No more error after rebooting.
Title: Re: Problem building 19.7a
Post by: bimmerdriver on April 16, 2019, 02:22:06 am
I updated to OPNsense 19.7.a_572-amd64 and the previously mentioned issues seem to have gone away. It's working as expected.
Title: Re: Problem building 19.7a
Post by: bimmerdriver on April 19, 2019, 03:55:57 am
Updated to OPNsense 19.7.a_586-amd64. The gateway monitor for WAN_DHCP6 will not start. Searched in the log for dpinger messages, but didn't find any. Maybe I'm not looking in the right place. Since it's otherwise working properly. I'll try upgrading to the next release and will report back if the problem goes away.
Title: Re: Problem building 19.7a
Post by: mimugmail on April 19, 2019, 03:41:21 pm
Maybe you should follow every commit on core so you would know there is heavy work on this right now :)
Title: Re: Problem building 19.7a
Post by: bimmerdriver on April 19, 2019, 05:52:40 pm
Maybe you should follow every commit on core so you would know there is heavy work on this right now :)
I'm aware that it's under development and things may or may not work on any given day. I'm just giving anyone who might upgrade heads-up. I'm running it on a VM so it only takes a click to return to a previous version.
Title: Re: Problem building 19.7a
Post by: franco on April 20, 2019, 07:18:55 pm
This thread is an idea by bimmerdriver and I've grown rather fond of it for a two reasons:

1. Users updating to latest development versions reporting it works ok or this or that some things looks odd.

2. If updates are not working people can report it and we can help them through it.

So by all means please continue. :)


Cheers,
Franco
Title: Re: Problem building 19.7a
Post by: franco on April 20, 2019, 07:30:18 pm
Updated to OPNsense 19.7.a_586-amd64. The gateway monitor for WAN_DHCP6 will not start. Searched in the log for dpinger messages, but didn't find any. Maybe I'm not looking in the right place. Since it's otherwise working properly. I'll try upgrading to the next release and will report back if the problem goes away.

I would have to test this at the office next week. I haven't seen an issue after Ad worked through a few loose ends this week. Does that also happen on a clean reboot with the latest code?


Cheers,
Franco
Title: Re: Problem building 19.7a
Post by: bimmerdriver on April 20, 2019, 08:27:22 pm
Updated to OPNsense 19.7.a_586-amd64. The gateway monitor for WAN_DHCP6 will not start. Searched in the log for dpinger messages, but didn't find any. Maybe I'm not looking in the right place. Since it's otherwise working properly. I'll try upgrading to the next release and will report back if the problem goes away.

I would have to test this at the office next week. I haven't seen an issue after Ad worked through a few loose ends this week. Does that also happen on a clean reboot with the latest code?


Cheers,
Franco
The system is currently running OPNsense 19.7.a_588-amd64. I rebooted and the WAN_DHCP6 gateway is still not starting. If you tell me where to find dpinger log messages, I can post them, if that would help.

Update: There are no symptoms other than the gateway monitor. IPv6 is working fine.
Title: Re: Problem building 19.7a
Post by: franco on April 21, 2019, 07:45:54 pm
Can you restart the particular monitor and go to system log for clues? (System: Log Files: General)


Thanks,
Franco
Title: Re: Problem building 19.7a
Post by: bimmerdriver on April 21, 2019, 08:04:59 pm
Can you restart the particular monitor and go to system log for clues? (System: Log Files: General)


Thanks,
Franco
There aren't any dpinger messages at all in the log for either the IPv4 or the IPv6 gateway monitor. When I attempt to start the IPv6 gateway monitor, no new messages from any source appear in the log. It's the same if I restart the IPv4 gateway monitor.
Title: Re: Problem building 19.7a
Post by: franco on April 26, 2019, 12:52:00 pm
Nothing in the system log as well?

# clog /var/log/system.log | grep dpinger

The office FW is working fine with native IPv6 and gateway monitoring for it on the latest master code.

Please also check System: Gateways: Single if it shows the same gateways or IPv6 is missing. I saw something just out of sync with how Dpinger is "deciding" which monitors it can use and then they are basically offline because they don't exist which is ok because they are not configured...


Cheers,
Franco
Title: Re: Problem building 19.7a
Post by: franco on April 26, 2019, 03:15:39 pm
Added more system.log logging to master. If you press "play" on the broken monitor it should reveal what's going on.

Maybe WAN has DHCPv6 enabled, but your WAN doesn't give an IPv6. The system used to ignore this, but these days we try to show that IPv6 is not working so it can be disabled manually in the WAN config.


Cheers,
Franco
Title: Re: Problem building 19.7a
Post by: marjohn56 on April 26, 2019, 03:35:09 pm
He has an ISP that does not issue an address on the WAN, only PD - I set up a fake monitor for him a while back.

@Bimmnerdriver contact me and I'll remote in and take a look.
Title: Re: Problem building 19.7a
Post by: bimmerdriver on April 27, 2019, 04:20:40 am
Upgraded to OPNsense 19.7.a_623-amd64. Big step backwards. IPv6 not working.

@marjohn56 Let me know when is a good time for you to take a look. I'll check for your email in the morning, UTC-7.
Title: Re: Problem building 19.7a
Post by: marjohn56 on April 28, 2019, 02:32:02 am
@franco - there are issues with 19.7.a_661 - getting this:

Code: [Select]
Fatal error: Uncaught Error: Call to undefined function services_dhcpd_configure() in /usr/local/etc/inc/interfaces.inc:2573 Stack trace: #0 /usr/local/www/interfaces.php(598): interface_configure(false, 'lan', true) #1 {main} thrown in /usr/local/etc/inc/interfaces.inc on line 2573.
Also there was a previous call that failed in interfaces.inc, had to add require_once("services.inc"); to interfaces.inc to resolve it, cannot remember what the function was that was missing, I'll try and force it again.
Title: Re: Problem building 19.7a
Post by: franco on April 28, 2019, 02:40:36 pm
@marjohn56: Sorry, my bad. I am trying to get rid of most services.inc requirements.

https://github.com/opnsense/core/commit/b140e91b7

@bimmeldriver: please try opnsense-devel-19.7.a_666 and dump the system.log here if the issue continues.


Cheers,
Franco
Title: Re: Problem building 19.7a
Post by: marjohn56 on April 28, 2019, 03:59:13 pm
@franco - that's working again. It was whilst I was teamviewered into bimmer's system that I saw his showing that error, then saw it on my test system when I changing dhcp6 server from manual to automatic. I was also seeing a routing issue but that appears to have cleared too.
Title: Re: Problem building 19.7a
Post by: franco on April 30, 2019, 07:27:00 am
Okay, glad to hear.
Title: Re: Problem building 19.7a
Post by: bimmerdriver on May 01, 2019, 03:38:55 am
Updated to OPNsense 19.7.a_700-amd64. Ipv6 not working.

Noticed on the console:

Setting up gateway monitors...done
Warning: vsprintf(): Too few arguments in /usr/local/etc/inc/util.inc on line 984
done.

I cleared the logs, then rebooted. Here is the log:

Code: [Select]
Apr 30 18:22:30 OPNsense syslogd: kernel boot file is /boot/kernel/kernel
Apr 30 18:22:33 OPNsense sshlockout[65553]: sshlockout/webConfigurator v3.0 starting up
Apr 30 18:22:56 OPNsense shutdown: reboot by root:
Apr 30 18:22:56 OPNsense shutdown: reboot by root:
Apr 30 18:22:56 OPNsense syslogd: exiting on signal 15
Apr 30 18:24:08 OPNsense syslogd: kernel boot file is /boot/kernel/kernel
Apr 30 18:24:08 OPNsense kernel: Copyright (c) 2013-2018 The HardenedBSD Project.
Apr 30 18:24:08 OPNsense kernel: [1] Copyright (c) 1992-2018 The FreeBSD Project.
Apr 30 18:24:08 OPNsense kernel: [1] Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
Apr 30 18:24:08 OPNsense kernel: [1] The Regents of the University of California. All rights reserved.
Apr 30 18:24:08 OPNsense kernel: [1] FreeBSD is a registered trademark of The FreeBSD Foundation.
Apr 30 18:24:08 OPNsense kernel: [1] FreeBSD 11.2-RELEASE-p4-HBSD  4b21e5691ff(master) amd64
Apr 30 18:24:08 OPNsense kernel: [1] FreeBSD clang version 6.0.0 (tags/RELEASE_600/final 326565) (based on LLVM 6.0.0)
Apr 30 18:24:08 OPNsense kernel: [1] VT(efifb): resolution 1024x768
Apr 30 18:24:08 OPNsense kernel: [1] Hyper-V Version: 6.3.9600 [SP18]
Apr 30 18:24:08 OPNsense kernel: [1]   Features=0xe7f<VPRUNTIME,TMREFCNT,SYNIC,SYNTM,APIC,HYPERCALL,VPINDEX,REFTSC,IDLE,TMFREQ>
Apr 30 18:24:08 OPNsense kernel: [1]   PM Features=0x0 [C2]
Apr 30 18:24:08 OPNsense kernel: [1]   Features3=0x17b2<DEBUG,XMMHC,IDLE,NUMA,TMFREQ,SYNCMC,CRASH,NPIEP>
Apr 30 18:24:08 OPNsense kernel: [1] Timecounter "Hyper-V" frequency 10000000 Hz quality 2000
Apr 30 18:24:08 OPNsense kernel: [1] HardenedBSD: initialize and check features (__HardenedBSD_version 1100056 __FreeBSD_version 1102000).
Apr 30 18:24:08 OPNsense kernel: [1] CPU: Intel(R) Xeon(R) CPU           E5504  @ 2.00GHz (1999.04-MHz K8-class CPU)
Apr 30 18:24:08 OPNsense kernel: [1]   Origin="GenuineIntel"  Id=0x106a5  Family=0x6  Model=0x1a  Stepping=5
Apr 30 18:24:08 OPNsense kernel: [1]   Features=0x1f83fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE,SSE2,SS,HTT>
Apr 30 18:24:08 OPNsense kernel: [1]   Features2=0x80982201<SSE3,SSSE3,CX16,SSE4.1,SSE4.2,POPCNT,HV>
Apr 30 18:24:08 OPNsense kernel: [1]   AMD Features=0x20100800<SYSCALL,NX,LM>
Apr 30 18:24:08 OPNsense kernel: [1]   AMD Features2=0x1<LAHF>
Apr 30 18:24:08 OPNsense kernel: [1] Hypervisor: Origin = "Microsoft Hv"
Apr 30 18:24:08 OPNsense kernel: [1] real memory  = 2097152000 (2000 MB)
Apr 30 18:24:08 OPNsense kernel: [1] avail memory = 1980538880 (1888 MB)
Apr 30 18:24:08 OPNsense kernel: [1] Event timer "LAPIC" quality 100
Apr 30 18:24:08 OPNsense kernel: [1] ACPI APIC Table: <VRTUAL MICROSFT>
Apr 30 18:24:08 OPNsense kernel: [1] FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
Apr 30 18:24:08 OPNsense kernel: [1] FreeBSD/SMP: 1 package(s) x 2 core(s)
Apr 30 18:24:08 OPNsense kernel: [1] ioapic0 <Version 1.1> irqs 0-23 on motherboard
Apr 30 18:24:08 OPNsense kernel: [1] SMP: AP CPU #1 Launched!
Apr 30 18:24:08 OPNsense kernel: [1] Timecounter "Hyper-V-TSC" frequency 10000000 Hz quality 3000
Apr 30 18:24:08 OPNsense kernel: [1] wlan: mac acl policy registered
Apr 30 18:24:08 OPNsense kernel: [1] random: entropy device external interface
Apr 30 18:24:08 OPNsense kernel: [1] netmap: loaded module
Apr 30 18:24:08 OPNsense kernel: [1] module_register_init: MOD_LOAD (vesa, 0xffffffff8113ee30, 0) error 19
Apr 30 18:24:08 OPNsense kernel: [1] kbd0 at kbdmux0
Apr 30 18:24:08 OPNsense kernel: [1] nexus0
Apr 30 18:24:08 OPNsense kernel: [1] cryptosoft0: <software crypto> on motherboard
Apr 30 18:24:08 OPNsense kernel: [1] acpi0: <VRTUAL MICROSFT> on motherboard
Apr 30 18:24:08 OPNsense kernel: [1] cpu0: <ACPI CPU> on acpi0
Apr 30 18:24:08 OPNsense kernel: [1] cpu1: <ACPI CPU> on acpi0
Apr 30 18:24:08 OPNsense kernel: [1] atrtc0: <AT realtime clock> port 0x70-0x71 irq 8 on acpi0
Apr 30 18:24:08 OPNsense kernel: [1] atrtc0: registered as a time-of-day clock, resolution 1.000000s
Apr 30 18:24:08 OPNsense kernel: [1] Event timer "RTC" frequency 32768 Hz quality 0
Apr 30 18:24:08 OPNsense kernel: [1] Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
Apr 30 18:24:08 OPNsense kernel: [1] acpi_timer0: <32-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0
Apr 30 18:24:08 OPNsense kernel: [1] acpi_syscontainer0: <System Container> on acpi0
Apr 30 18:24:08 OPNsense kernel: [1] vmbus0: <Hyper-V Vmbus> on acpi_syscontainer0
Apr 30 18:24:08 OPNsense kernel: [1] vmbus_res0: <Hyper-V Vmbus Resource> irq 5 on acpi0
Apr 30 18:24:08 OPNsense kernel: [1] Timecounters tick every 10.000 msec
Apr 30 18:24:08 OPNsense kernel: [1] usb_needs_explore_all: no devclass
Apr 30 18:24:08 OPNsense kernel: [1] vmbus0: version 3.0
Apr 30 18:24:08 OPNsense kernel: [1] hvet0: <Hyper-V event timer> on vmbus0
Apr 30 18:24:08 OPNsense kernel: [1] Event timer "Hyper-V" frequency 10000000 Hz quality 1000
Apr 30 18:24:08 OPNsense kernel: [1] hvkbd0: <Hyper-V KBD> on vmbus0
Apr 30 18:24:08 OPNsense kernel: [1] storvsc0: <Hyper-V SCSI> on vmbus0
Apr 30 18:24:08 OPNsense kernel: [1] hvheartbeat0: <Hyper-V Heartbeat> on vmbus0
Apr 30 18:24:08 OPNsense kernel: [1] da0 at storvsc0 bus 0 scbus0 target 0 lun 0
Apr 30 18:24:08 OPNsense kernel: [1] da0: <Msft Virtual Disk 1.0> Fixed Direct Access SPC-3 SCSI device
Apr 30 18:24:08 OPNsense kernel: [1] da0: 300.000MB/s transfers
Apr 30 18:24:08 OPNsense kernel: [1] da0: Command Queueing enabled
Apr 30 18:24:08 OPNsense kernel: [1] da0: 130048MB (266338304 512 byte sectors)
Apr 30 18:24:08 OPNsense kernel: [1] cd0 at storvsc0 bus 0 scbus0 target 0 lun 1
Apr 30 18:24:08 OPNsense kernel: [1] cd0: <Msft Virtual DVD-ROM 1.0> Removable CD-ROM SPC-3 SCSI device
Apr 30 18:24:08 OPNsense kernel: [1] cd0: 300.000MB/s transfers
Apr 30 18:24:08 OPNsense kernel: [1] cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed
Apr 30 18:24:08 OPNsense kernel: [1] hvkvp0: <Hyper-V KVP> on vmbus0
Apr 30 18:24:08 OPNsense kernel: [1] hvshutdown0: <Hyper-V Shutdown> on vmbus0
Apr 30 18:24:08 OPNsense kernel: [1] hvtimesync0: <Hyper-V Timesync> on vmbus0
Apr 30 18:24:08 OPNsense kernel: [1] hvvss0: <Hyper-V VSS> on vmbus0
Apr 30 18:24:08 OPNsense kernel: [1] hn0: <Hyper-V Network Interface> on vmbus0
Apr 30 18:24:08 OPNsense kernel: [1] hn0: Ethernet address: 00:15:5d:5c:e2:3b
Apr 30 18:24:08 OPNsense kernel: [1] hn0: link state changed to UP
Apr 30 18:24:08 OPNsense kernel: [1] hn1: <Hyper-V Network Interface> on vmbus0
Apr 30 18:24:08 OPNsense kernel: [2] hn1: Ethernet address: 00:15:5d:5c:e2:3c
Apr 30 18:24:08 OPNsense kernel: [2] hn1: link state changed to UP
Apr 30 18:24:08 OPNsense kernel: [2] Trying to mount root from ufs:/dev/gpt/rootfs [rw]...
Apr 30 18:24:08 OPNsense kernel: [18] random: unblocking device.
Apr 30 18:24:08 OPNsense kernel: [47] aesni0: No AESNI support.
Apr 30 18:24:08 OPNsense kernel: done.
Apr 30 18:24:08 OPNsense kernel: done.
Apr 30 18:24:09 OPNsense dhclient: Starting delete_old_states()
Apr 30 18:24:09 OPNsense sshlockout[63927]: sshlockout/webConfigurator v3.0 starting up
Apr 30 18:24:09 OPNsense dhclient[57741]: DHCPREQUEST on hn0 to 255.255.255.255 port 67
Apr 30 18:24:09 OPNsense dhclient[57741]: DHCPACK from 10.27.191.77
Apr 30 18:24:09 OPNsense dhclient: Starting delete_old_states()
Apr 30 18:24:09 OPNsense dhclient: New IP Address (hn0): 162.156.72.57
Apr 30 18:24:09 OPNsense dhclient: New Subnet Mask (hn0): 255.255.252.0
Apr 30 18:24:09 OPNsense dhclient: New Broadcast Address (hn0): 162.156.75.255
Apr 30 18:24:09 OPNsense dhclient: New Routers (hn0): 162.156.72.1
Apr 30 18:24:09 OPNsense dhclient: route add default 162.156.72.1
Apr 30 18:24:09 OPNsense dhclient: Creating resolv.conf
Apr 30 18:24:09 OPNsense opnsense-devel: /usr/local/etc/rc.newwanip: IP renewal deferred during boot on 'hn0'
Apr 30 18:24:09 OPNsense dhclient[57741]: bound to 162.156.72.57 -- renewal in 300 seconds.
Apr 30 18:24:09 OPNsense opnsense-devel: /usr/local/etc/rc.bootup: Accept router advertisements on interface hn0
Apr 30 18:24:09 OPNsense dhcp6c: RTSOLD script - Starting dhcp6 client for interface wan(hn0)
Apr 30 18:24:09 OPNsense kernel: done.
Apr 30 18:24:09 OPNsense kernel: done.
Apr 30 18:24:09 OPNsense kernel: [54] pflog0: promiscuous mode enabled
Apr 30 18:24:10 OPNsense dhcp6c[57746]: Sending Solicit
Apr 30 18:24:10 OPNsense kernel: ...
Apr 30 18:24:10 OPNsense kernel: done.
Apr 30 18:24:11 OPNsense sshd[32722]: Server listening on :: port 22.
Apr 30 18:24:11 OPNsense kernel: done.
Apr 30 18:24:11 OPNsense sshd[32722]: Server listening on 0.0.0.0 port 22.
Apr 30 18:24:11 OPNsense dhcp6c[57746]: Sending Request
Apr 30 18:24:11 OPNsense kernel: done.
Apr 30 18:24:11 OPNsense opnsense-devel: /usr/local/etc/rc.bootup: ROUTING: entering configure using defaults
Apr 30 18:24:11 OPNsense kernel: done.
Apr 30 18:24:11 OPNsense opnsense-devel: /usr/local/etc/rc.bootup: ROUTING: IPv4 default gateway set to wan
Apr 30 18:24:11 OPNsense opnsense-devel: /usr/local/etc/rc.bootup: ROUTING: setting IPv4 default route to 162.156.72.1
Apr 30 18:24:11 OPNsense opnsense-devel: /usr/local/etc/rc.bootup: ROUTING: keeping current default gateway '162.156.72.1'
Apr 30 18:24:11 OPNsense opnsense-devel: /usr/local/etc/rc.bootup: ROUTING: IPv6 default gateway set to wan
Apr 30 18:24:11 OPNsense opnsense-devel: /usr/local/etc/rc.bootup: ROUTING: setting IPv6 default route to dynamic
Apr 30 18:24:11 OPNsense opnsense-devel: /usr/local/etc/rc.bootup: ROUTING: creating /tmp/hn0_defaultgwv6 using 'dynamic'
Apr 30 18:24:12 OPNsense dhcp6c[57746]: Received REPLY for REQUEST
Apr 30 18:24:12 OPNsense dhcp6c[57746]: add an address 2001:569:74b4:dc00:215:5dff:fe5c:e23c/64 on hn1
Apr 30 18:24:12 OPNsense dhcp6c: dhcp6c REQUEST on hn0 - running newipv6
Apr 30 18:24:12 OPNsense opnsense-devel: /usr/local/etc/rc.newwanipv6: IP renewal deferred during boot on 'hn0'
Apr 30 18:24:15 OPNsense opnsense-devel: user root authenticated successfully for sshd [using OPNsense\Auth\Services\System + OPNsense\Auth\Local]
Apr 30 18:24:15 OPNsense sshd[97082]: Accepted keyboard-interactive/pam for root from 192.168.1.100 port 60098 ssh2
Apr 30 18:24:41 OPNsense opnsense-devel: /usr/local/etc/rc.bootup: The command '/sbin/route add -'inet6' default 'dynamic'' returned exit code '71', the output was 'route: dynamic: hostname nor servname provided, or not known'
Apr 30 18:24:42 OPNsense kernel: done.
Apr 30 18:24:42 OPNsense kernel: done.
Apr 30 18:24:42 OPNsense kernel: done.
Apr 30 18:24:42 OPNsense kernel: done.
Apr 30 18:24:44 OPNsense kernel: done.
Apr 30 18:24:44 OPNsense kernel:
Apr 30 18:24:45 OPNsense kernel: ...
Apr 30 18:24:45 OPNsense kernel: done.
Apr 30 18:24:47 OPNsense opnsense-devel: /usr/local/etc/rc.bootup: Resyncing OpenVPN instances.
Apr 30 18:24:47 OPNsense kernel: deferred.
Apr 30 18:24:47 OPNsense kernel: done.
Apr 30 18:24:48 OPNsense kernel: done.
Apr 30 18:24:48 OPNsense syslogd: exiting on signal 15
Apr 30 18:24:48 OPNsense syslogd: kernel boot file is /boot/kernel/kernel
Apr 30 18:24:48 OPNsense kernel: done.
Apr 30 18:24:48 OPNsense opnsense-devel: /usr/local/etc/rc.newwanip: IP renewal is starting on 'hn0'
Apr 30 18:24:48 OPNsense sshlockout[97587]: sshlockout/webConfigurator v3.0 starting up
Apr 30 18:24:48 OPNsense opnsense-devel: /usr/local/etc/rc.newwanip: On (IP address: 162.156.72.57) (interface: WAN[wan]) (real interface: hn0).
Apr 30 18:24:48 OPNsense opnsense-devel: /usr/local/etc/rc.newwanip: ROUTING: entering configure using 'wan'
Apr 30 18:24:48 OPNsense opnsense-devel: /usr/local/etc/rc.newwanip: ROUTING: IPv4 default gateway set to wan
Apr 30 18:24:48 OPNsense opnsense-devel: /usr/local/etc/rc.newwanip: ROUTING: setting IPv4 default route to 162.156.72.1
Apr 30 18:24:48 OPNsense opnsense-devel: /usr/local/etc/rc.newwanip: ROUTING: keeping current default gateway '162.156.72.1'
Apr 30 18:24:48 OPNsense opnsense-devel: /usr/local/etc/rc.newwanip: ROUTING: IPv6 default gateway set to wan
Apr 30 18:24:48 OPNsense opnsense-devel: /usr/local/etc/rc.newwanip: ROUTING: setting IPv6 default route to dynamic
Apr 30 18:24:48 OPNsense opnsense-devel: /usr/local/etc/rc.newwanip: ROUTING: removing /tmp/hn0_defaultgwv6
Apr 30 18:24:48 OPNsense opnsense-devel: /usr/local/etc/rc.newwanip: ROUTING: creating /tmp/hn0_defaultgwv6 using 'dynamic'
Apr 30 18:24:49 OPNsense opnsense-devel: /usr/local/etc/rc.newwanip: The command '/sbin/route add -'inet6' default 'dynamic'' returned exit code '71', the output was 'route: dynamic: hostname nor servname provided, or not known'
Apr 30 18:24:50 OPNsense kernel: OK
Apr 30 18:24:50 OPNsense opnsense-devel: /usr/local/etc/rc.newwanipv6: IP renewal is starting on 'hn0'
Apr 30 18:24:50 OPNsense opnsense-devel: /usr/local/etc/rc.newwanipv6: On (IP address: fe80::215:5dff:fe5c:e23b) (interface: WAN[wan]) (real interface: hn0).
Apr 30 18:24:51 OPNsense opnsense-devel: /usr/local/etc/rc.newwanipv6: ROUTING: entering configure using 'wan'
Apr 30 18:24:51 OPNsense opnsense-devel: /usr/local/etc/rc.newwanipv6: ROUTING: IPv4 default gateway set to wan
Apr 30 18:24:51 OPNsense opnsense-devel: /usr/local/etc/rc.newwanipv6: ROUTING: setting IPv4 default route to 162.156.72.1
Apr 30 18:24:51 OPNsense opnsense-devel: /usr/local/etc/rc.newwanipv6: ROUTING: keeping current default gateway '162.156.72.1'
Apr 30 18:24:51 OPNsense opnsense-devel: /usr/local/etc/rc.newwanipv6: ROUTING: IPv6 default gateway set to wan
Apr 30 18:24:51 OPNsense opnsense-devel: /usr/local/etc/rc.newwanipv6: ROUTING: setting IPv6 default route to dynamic
Apr 30 18:24:51 OPNsense opnsense-devel: /usr/local/etc/rc.newwanipv6: ROUTING: removing /tmp/hn0_defaultgwv6
Apr 30 18:24:51 OPNsense opnsense-devel: /usr/local/etc/rc.newwanipv6: ROUTING: creating /tmp/hn0_defaultgwv6 using 'dynamic'
Apr 30 18:24:52 OPNsense opnsense-devel: /usr/local/etc/rc.newwanipv6: The command '/sbin/route add -'inet6' default 'dynamic'' returned exit code '71', the output was 'route: dynamic: hostname nor servname provided, or not known'
Apr 30 18:24:53 OPNsense kernel: OK
Apr 30 18:24:56 OPNsense kernel: OK
Apr 30 18:24:58 OPNsense kernel: SHA256 kR6ba0FzdjYHbQILbXPVGjVr/Z3K6grkY1jI2YP2Qx4 (ED25519)
Apr 30 18:25:35 OPNsense opnsense-devel: /index.php: Successful login for user 'root' from: fe80::18e0:4a20:6d32:ba92
Apr 30 18:28:52 OPNsense opnsense-devel: user root authenticated successfully for login [using OPNsense\Auth\Services\System + OPNsense\Auth\Local]
Apr 30 18:28:52 OPNsense login: login on ttyv0 as root
Apr 30 18:28:52 OPNsense login: ROOT LOGIN (root) ON ttyv0
Apr 30 18:28:52 OPNsense login: ROOT LOGIN (root) ON ttyv0
Apr 30 18:29:10 OPNsense dhclient: Creating resolv.conf
Apr 30 18:29:12 OPNsense dhcp6c[57746]: Sending Renew
Apr 30 18:29:12 OPNsense dhcp6c[57746]: Received REPLY for RENEW
Title: Re: Problem building 19.7a
Post by: franco on May 01, 2019, 11:33:05 am
Thanks, might be https://github.com/opnsense/core/commit/6adafe8b -- something around system_default_route() calls with empty gateway now, it might need further protection.


Cheers,
Franco
Title: Re: Problem building 19.7a
Post by: bimmerdriver on May 02, 2019, 05:02:06 am
Upgraded to OPNsense 19.7.a_704-amd64 today. IPv6 is working again, but still no gateway monitor. No dpinger messages in the log. Let me know if there is anything I can provide.
Title: Re: Problem building 19.7a
Post by: franco on May 02, 2019, 06:37:24 am
Okay, so far so good. Can I take a look at that system with SSH maybe? Flying blind and not sure where to look next. PM me if okay.


Cheers,
Franco
Title: Re: Problem building 19.7a
Post by: bimmerdriver on May 04, 2019, 06:28:15 pm
Updated to OPNsense 19.7.a_718-amd64. No change. You're welcome to have a look.
Title: Re: Problem building 19.7a
Post by: bimmerdriver on May 14, 2019, 06:58:28 am
Updated to OPNsense 19.7.b_43-amd64. No change. WAN_DHCP6 gateway monitor not working.
Title: Re: Problem building 19.7a
Post by: bimmerdriver on May 25, 2019, 09:47:21 pm
Updated to OPNsense 19.7.b_80-amd64. Back to Gateway Monitor (WAN_DHCP6) and IPv6 not working.

I cleared the logs and rebooted.

Here is the log:

Code: [Select]
May 25 12:55:51 OPNsense syslogd: kernel boot file is /boot/kernel/kernel
May 25 12:55:54 OPNsense sshlockout[66451]: sshlockout/webConfigurator v3.0 starting up
May 25 12:55:55 OPNsense syslogd: exiting on signal 15
May 25 12:55:55 OPNsense syslogd: kernel boot file is /boot/kernel/kernel
May 25 12:55:57 OPNsense sshlockout[35239]: sshlockout/webConfigurator v3.0 starting up
May 25 12:56:07 OPNsense shutdown: reboot by root:
May 25 12:56:07 OPNsense shutdown: reboot by root:
May 25 12:56:07 OPNsense syslogd: exiting on signal 15
May 25 12:57:12 OPNsense syslogd: kernel boot file is /boot/kernel/kernel
May 25 12:57:12 OPNsense kernel: Copyright (c) 2013-2018 The HardenedBSD Project.
May 25 12:57:12 OPNsense kernel: [1] Copyright (c) 1992-2018 The FreeBSD Project.
May 25 12:57:12 OPNsense kernel: [1] Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
May 25 12:57:12 OPNsense kernel: [1] The Regents of the University of California. All rights reserved.
May 25 12:57:12 OPNsense kernel: [1] FreeBSD is a registered trademark of The FreeBSD Foundation.
May 25 12:57:12 OPNsense kernel: [1] FreeBSD 11.2-RELEASE-p4-HBSD  4b21e5691ff(master) amd64
May 25 12:57:12 OPNsense kernel: [1] FreeBSD clang version 6.0.0 (tags/RELEASE_600/final 326565) (based on LLVM 6.0.0)
May 25 12:57:12 OPNsense kernel: [1] VT(efifb): resolution 1024x768
May 25 12:57:12 OPNsense kernel: [1] Hyper-V Version: 6.3.9600 [SP18]
May 25 12:57:12 OPNsense kernel: [1]   Features=0xe7f<VPRUNTIME,TMREFCNT,SYNIC,SYNTM,APIC,HYPERCALL,VPINDEX,REFTSC,IDLE,TMFREQ>
May 25 12:57:12 OPNsense kernel: [1]   PM Features=0x0 [C2]
May 25 12:57:12 OPNsense kernel: [1]   Features3=0x17b2<DEBUG,XMMHC,IDLE,NUMA,TMFREQ,SYNCMC,CRASH,NPIEP>
May 25 12:57:12 OPNsense kernel: [1] Timecounter "Hyper-V" frequency 10000000 Hz quality 2000
May 25 12:57:12 OPNsense kernel: [1] HardenedBSD: initialize and check features (__HardenedBSD_version 1100056 __FreeBSD_version 1102000).
May 25 12:57:12 OPNsense kernel: [1] CPU: Intel(R) Xeon(R) CPU           E5504  @ 2.00GHz (1999.04-MHz K8-class CPU)
May 25 12:57:12 OPNsense kernel: [1]   Origin="GenuineIntel"  Id=0x106a5  Family=0x6  Model=0x1a  Stepping=5
May 25 12:57:12 OPNsense kernel: [1]   Features=0x1f83fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE,SSE2,SS,HTT>
May 25 12:57:12 OPNsense kernel: [1]   Features2=0x80982201<SSE3,SSSE3,CX16,SSE4.1,SSE4.2,POPCNT,HV>
May 25 12:57:12 OPNsense kernel: [1]   AMD Features=0x20100800<SYSCALL,NX,LM>
May 25 12:57:12 OPNsense kernel: [1]   AMD Features2=0x1<LAHF>
May 25 12:57:12 OPNsense kernel: [1] Hypervisor: Origin = "Microsoft Hv"
May 25 12:57:12 OPNsense kernel: [1] real memory  = 2097152000 (2000 MB)
May 25 12:57:12 OPNsense kernel: [1] avail memory = 1980538880 (1888 MB)
May 25 12:57:12 OPNsense kernel: [1] Event timer "LAPIC" quality 100
May 25 12:57:12 OPNsense kernel: [1] ACPI APIC Table: <VRTUAL MICROSFT>
May 25 12:57:12 OPNsense kernel: [1] FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
May 25 12:57:12 OPNsense kernel: [1] FreeBSD/SMP: 1 package(s) x 2 core(s)
May 25 12:57:12 OPNsense kernel: [1] ioapic0 <Version 1.1> irqs 0-23 on motherboard
May 25 12:57:12 OPNsense kernel: [1] SMP: AP CPU #1 Launched!
May 25 12:57:12 OPNsense kernel: [1] Timecounter "Hyper-V-TSC" frequency 10000000 Hz quality 3000
May 25 12:57:12 OPNsense kernel: [1] wlan: mac acl policy registered
May 25 12:57:12 OPNsense kernel: [1] random: entropy device external interface
May 25 12:57:12 OPNsense kernel: [1] netmap: loaded module
May 25 12:57:12 OPNsense kernel: [1] module_register_init: MOD_LOAD (vesa, 0xffffffff8113ee30, 0) error 19
May 25 12:57:12 OPNsense kernel: [1] kbd0 at kbdmux0
May 25 12:57:12 OPNsense kernel: [1] nexus0
May 25 12:57:12 OPNsense kernel: [1] cryptosoft0: <software crypto> on motherboard
May 25 12:57:12 OPNsense kernel: [1] acpi0: <VRTUAL MICROSFT> on motherboard
May 25 12:57:12 OPNsense kernel: [1] cpu0: <ACPI CPU> on acpi0
May 25 12:57:12 OPNsense kernel: [1] cpu1: <ACPI CPU> on acpi0
May 25 12:57:12 OPNsense kernel: [1] atrtc0: <AT realtime clock> port 0x70-0x71 irq 8 on acpi0
May 25 12:57:12 OPNsense kernel: [1] atrtc0: registered as a time-of-day clock, resolution 1.000000s
May 25 12:57:12 OPNsense kernel: [1] Event timer "RTC" frequency 32768 Hz quality 0
May 25 12:57:12 OPNsense kernel: [1] Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
May 25 12:57:12 OPNsense kernel: [1] acpi_timer0: <32-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0
May 25 12:57:12 OPNsense kernel: [1] acpi_syscontainer0: <System Container> on acpi0
May 25 12:57:12 OPNsense kernel: [1] vmbus0: <Hyper-V Vmbus> on acpi_syscontainer0
May 25 12:57:12 OPNsense kernel: [1] vmbus_res0: <Hyper-V Vmbus Resource> irq 5 on acpi0
May 25 12:57:12 OPNsense kernel: [1] Timecounters tick every 10.000 msec
May 25 12:57:12 OPNsense kernel: [1] usb_needs_explore_all: no devclass
May 25 12:57:12 OPNsense kernel: [1] vmbus0: version 3.0
May 25 12:57:12 OPNsense kernel: [1] hvet0: <Hyper-V event timer> on vmbus0
May 25 12:57:12 OPNsense kernel: [1] Event timer "Hyper-V" frequency 10000000 Hz quality 1000
May 25 12:57:12 OPNsense kernel: [1] hvkbd0: <Hyper-V KBD> on vmbus0
May 25 12:57:12 OPNsense kernel: [1] storvsc0: <Hyper-V SCSI> on vmbus0
May 25 12:57:12 OPNsense kernel: [1] da0 at storvsc0 bus 0 scbus0 target 0 lun 0
May 25 12:57:12 OPNsense kernel: [1] hvheartbeat0: da0: <Hyper-V Heartbeat><Msft Virtual Disk 1.0> Fixed Direct Access SPC-3 SCSI device
May 25 12:57:12 OPNsense kernel: [1] da0: 300.000MB/s transfers on vmbus0
May 25 12:57:12 OPNsense kernel: [1]
May 25 12:57:12 OPNsense kernel: [1] da0: Command Queueing enabled
May 25 12:57:12 OPNsense kernel: [1] da0: 130048MB (266338304 512 byte sectors)
May 25 12:57:12 OPNsense kernel: [1] cd0 at storvsc0 bus 0 scbus0 target 0 lun 1
May 25 12:57:12 OPNsense kernel: [1] hvkvp0: cd0: <Hyper-V KVP> on vmbus0
May 25 12:57:12 OPNsense kernel: [1] <Msft Virtual DVD-ROM 1.0> Removable CD-ROM SPC-3 SCSI device
May 25 12:57:12 OPNsense kernel: [1] cd0: 300.000MB/s transfers
May 25 12:57:12 OPNsense kernel: [1] cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed
May 25 12:57:12 OPNsense kernel: [1] hvshutdown0: <Hyper-V Shutdown> on vmbus0
May 25 12:57:12 OPNsense kernel: [1] hvtimesync0: <Hyper-V Timesync> on vmbus0
May 25 12:57:12 OPNsense kernel: [1] hvvss0: <Hyper-V VSS> on vmbus0
May 25 12:57:12 OPNsense kernel: [1] hn0: <Hyper-V Network Interface> on vmbus0
May 25 12:57:12 OPNsense kernel: [1] hn0: Ethernet address: 00:15:5d:5c:e2:3b
May 25 12:57:12 OPNsense kernel: [1] hn0: link state changed to UP
May 25 12:57:12 OPNsense kernel: [1] hn1: <Hyper-V Network Interface> on vmbus0
May 25 12:57:12 OPNsense kernel: [2] hn1: Ethernet address: 00:15:5d:5c:e2:3c
May 25 12:57:12 OPNsense kernel: [2] hn1: link state changed to UP
May 25 12:57:12 OPNsense kernel: [2] Trying to mount root from ufs:/dev/gpt/rootfs [rw]...
May 25 12:57:12 OPNsense kernel: [18] random: unblocking device.
May 25 12:57:12 OPNsense kernel: [44] aesni0: No AESNI support.
May 25 12:57:12 OPNsense kernel: done.
May 25 12:57:12 OPNsense kernel: done.
May 25 12:57:12 OPNsense dhclient: Starting delete_old_states()
May 25 12:57:13 OPNsense dhclient[14733]: DHCPREQUEST on hn0 to 255.255.255.255 port 67
May 25 12:57:13 OPNsense sshlockout[24113]: sshlockout/webConfigurator v3.0 starting up
May 25 12:57:13 OPNsense dhclient[14733]: DHCPACK from 10.27.191.77
May 25 12:57:13 OPNsense dhclient: Starting delete_old_states()
May 25 12:57:13 OPNsense dhclient: New IP Address (hn0): 154.20.116.43
May 25 12:57:13 OPNsense dhclient: New Subnet Mask (hn0): 255.255.252.0
May 25 12:57:13 OPNsense dhclient: New Broadcast Address (hn0): 154.20.119.255
May 25 12:57:13 OPNsense dhclient: New Routers (hn0): 154.20.116.1
May 25 12:57:13 OPNsense dhclient: route add default 154.20.116.1
May 25 12:57:13 OPNsense dhclient: Creating resolv.conf
May 25 12:57:13 OPNsense opnsense-devel: /usr/local/etc/rc.newwanip: IP renewal deferred during boot on 'hn0'
May 25 12:57:13 OPNsense dhclient[14733]: bound to 154.20.116.43 -- renewal in 300 seconds.
May 25 12:57:13 OPNsense opnsense-devel: /usr/local/etc/rc.bootup: Accept router advertisements on interface hn0
May 25 12:57:13 OPNsense dhcp6c: RTSOLD script - Starting dhcp6 client for interface wan(hn0)
May 25 12:57:13 OPNsense kernel: done.
May 25 12:57:13 OPNsense kernel: [46] pflog0: promiscuous mode enabled
May 25 12:57:14 OPNsense kernel: ...
May 25 12:57:14 OPNsense dhcp6c[9936]: Sending Solicit
May 25 12:57:14 OPNsense kernel: done.
May 25 12:57:14 OPNsense sshd[81609]: Server listening on :: port 22.
May 25 12:57:14 OPNsense kernel: done.
May 25 12:57:14 OPNsense sshd[81609]: Server listening on 0.0.0.0 port 22.
May 25 12:57:15 OPNsense dhcp6c[9936]: Sending Request
May 25 12:57:15 OPNsense kernel: done.
May 25 12:57:15 OPNsense opnsense-devel: /usr/local/etc/rc.bootup: ROUTING: entering configure using defaults
May 25 12:57:15 OPNsense kernel: done.
May 25 12:57:15 OPNsense opnsense-devel: /usr/local/etc/rc.bootup: ROUTING: IPv4 default gateway set to wan
May 25 12:57:15 OPNsense opnsense-devel: /usr/local/etc/rc.bootup: ROUTING: setting IPv4 default route to 154.20.116.1
May 25 12:57:15 OPNsense opnsense-devel: /usr/local/etc/rc.bootup: ROUTING: keeping current default gateway '154.20.116.1'
May 25 12:57:15 OPNsense dhcp6c[9936]: Received REPLY for REQUEST
May 25 12:57:15 OPNsense kernel: done.
May 25 12:57:15 OPNsense dhcp6c[9936]: add an address 2001:569:74c2:9000:215:5dff:fe5c:e23c/64 on hn1
May 25 12:57:15 OPNsense dhcp6c: dhcp6c REQUEST on hn0 - running newipv6
May 25 12:57:15 OPNsense kernel: done.
May 25 12:57:15 OPNsense opnsense-devel: /usr/local/etc/rc.newwanipv6: IP renewal deferred during boot on 'hn0'
May 25 12:57:16 OPNsense kernel: done.
May 25 12:57:16 OPNsense kernel: done.
May 25 12:57:17 OPNsense kernel: done.
May 25 12:57:18 OPNsense kernel: done.
May 25 12:57:19 OPNsense kernel: ...
May 25 12:57:19 OPNsense kernel: done.
May 25 12:57:21 OPNsense opnsense-devel: /usr/local/etc/rc.bootup: Resyncing OpenVPN instances.
May 25 12:57:22 OPNsense kernel: done.
May 25 12:57:22 OPNsense kernel: done.
May 25 12:57:22 OPNsense syslogd: exiting on signal 15
May 25 12:57:22 OPNsense syslogd: kernel boot file is /boot/kernel/kernel
May 25 12:57:23 OPNsense kernel: done.
May 25 12:57:23 OPNsense opnsense-devel: /usr/local/etc/rc.newwanip: IP renewal is starting on 'hn0'
May 25 12:57:23 OPNsense sshlockout[19363]: sshlockout/webConfigurator v3.0 starting up
May 25 12:57:23 OPNsense opnsense-devel: /usr/local/etc/rc.newwanip: On (IP address: 154.20.116.43) (interface: WAN[wan]) (real interface: hn0).
May 25 12:57:23 OPNsense opnsense-devel: /usr/local/etc/rc.newwanip: ROUTING: entering configure using 'wan'
May 25 12:57:23 OPNsense opnsense-devel: /usr/local/etc/rc.newwanip: ROUTING: IPv4 default gateway set to wan
May 25 12:57:23 OPNsense opnsense-devel: /usr/local/etc/rc.newwanip: ROUTING: setting IPv4 default route to 154.20.116.1
May 25 12:57:23 OPNsense opnsense-devel: /usr/local/etc/rc.newwanip: ROUTING: keeping current default gateway '154.20.116.1'
May 25 12:57:24 OPNsense kernel: OK
May 25 12:57:24 OPNsense opnsense-devel: /usr/local/etc/rc.newwanipv6: IP renewal is starting on 'hn0'
May 25 12:57:24 OPNsense opnsense-devel: /usr/local/etc/rc.newwanipv6: On (IP address: fe80::215:5dff:fe5c:e23b) (interface: WAN[wan]) (real interface: hn0).
May 25 12:57:25 OPNsense opnsense-devel: /usr/local/etc/rc.newwanipv6: ROUTING: entering configure using 'wan'
May 25 12:57:25 OPNsense opnsense-devel: /usr/local/etc/rc.newwanipv6: ROUTING: IPv4 default gateway set to wan
May 25 12:57:25 OPNsense opnsense-devel: /usr/local/etc/rc.newwanipv6: ROUTING: setting IPv4 default route to 154.20.116.1
May 25 12:57:25 OPNsense opnsense-devel: /usr/local/etc/rc.newwanipv6: ROUTING: keeping current default gateway '154.20.116.1'
May 25 12:57:26 OPNsense kernel: OK
May 25 12:57:29 OPNsense kernel: OK
May 25 12:57:30 OPNsense kernel: SHA256 CD 8A 8C 14 76 43 4F C9 0C D2 7E 4D 40 FE 9B 34
May 25 12:57:31 OPNsense kernel: SHA256 bH1hdcRBQRF6JnSMjcR2mYpDBAB/0sOB2MHgMNRWUMA (ECDSA)
May 25 12:57:35 OPNsense opnsense-devel: user root authenticated successfully for login [using OPNsense\Auth\Services\System + OPNsense\Auth\Local]
May 25 12:57:35 OPNsense login: login on ttyv0 as root
May 25 12:57:35 OPNsense login: ROOT LOGIN (root) ON ttyv0
May 25 12:57:35 OPNsense login: ROOT LOGIN (root) ON ttyv0