Messages

[auth-user-pass]

Confirm. My workaround for now: Add auth-user-pass manually to config output

And if you check for updates it presents packages for 23.7 and it downloads them and reboots? If yes it should produce a log file.

Exactly! But no log...

Code Select Expand

***GOT REQUEST TO UPGRADE***
Currently running OPNsense 23.1.11_1 at Tue Aug  1 17:18:40 CEST 2023
Fetching packages-23.7-amd64.tar: ................ done
Extracting packages-23.7-amd64.tar... done
Please reboot.
***DONE***

but opnsense-update -G gives no output. Checked that before and after reboot.

FWIW, we still need the "Upgrade" audit, not the "Health" one you presented here. ;)

Wish i could... :o
Only presented connectivity,health and security as choice.

There is an upgrade log and it will tell you what custom package prevents you from upgrading...

Either System: Firmware: Status -> Run an Audit -> Upgrade

Thanks,
wow did not expect that. Seems to be worse... Kernel is on 23.7 already.. No idea what's happened..
Functionally all is ok. But i think i have to reinstall.

Code Select Expand

***GOT REQUEST TO AUDIT HEALTH***
Currently running OPNsense 23.1.11_1 at Tue Aug  1 12:58:09 CEST 2023
>>> Check installed kernel version
Version 23.7 is correct.
>>> Check for missing or altered kernel files
No problems detected.
>>> Check installed base version
Version 23.7 is correct.
>>> Check for missing or altered base files
No problems detected.
>>> Check installed repositories
OPNsense
>>> Check installed plugins
os-acme-client 3.17
os-apcupsd 1.1
os-dmidecode 1.1_1
os-hw-probe 1.0_1
os-iperf 1.0_1
os-lldpd 1.1_2
os-net-snmp 1.5_2
os-ntopng 1.2_2
os-redis 1.1_2
os-rfc2136 1.8
os-smart 2.2_2
>>> Check locked packages
No locks found.
>>> Check for missing package dependencies
Checking all packages: .......... done
>>> Check for missing or altered package files
Checking all packages: .......... done
>>> Check for core packages consistency
Core package "opnsense" has 67 dependencies to check.
Checking packages: ..
ca_root_nss-3.91 version mismatch, expected 3.89.1
Checking packages: ........................
opnsense-update-23.7 version mismatch, expected 23.1.11
Checking packages: .......................
py39-dnspython-2.4.0,1 version mismatch, expected 2.3.0,1
Checking packages: .
py39-duckdb-0.8.1 version mismatch, expected 0.6.1
Checking packages: ..
py39-numpy-1.25.0,1 version mismatch, expected 1.24.1_4,1
Checking packages: .
py39-pandas-2.0.3,1 version mismatch, expected 2.0.2,1
Checking packages: ....
py39-vici-5.9.11 version mismatch, expected 5.9.10
Checking packages: ......
sudo-1.9.14p3 version mismatch, expected 1.9.13p3
Checking packages: .
suricata-6.0.13_1 version mismatch, expected 6.0.13
Checking packages: ..
unbound-1.17.1_3 version mismatch, expected 1.17.1_2
Checking packages: .. done
***DONE***

This time no luck at all...

No matter if started via gui or console (ssh/serial both) this update does not work for me.
After restart it runs still on 23.1.11_1 

Have a hard time to debug this. Cannot find any relevant log.

What i see there is some 23.7 package here, but not up to date.
pkg version | grep opns
opnsense-23.1.11_1                 =
opnsense-installer-23.1            =
opnsense-lang-22.7.3               =
opnsense-update-23.7               >
pam_opnsense-19.1.3                =

Yes, i can reinstall, no problem. But i like to know what colud be "special" on my system..

Intel(R) Celeron(R) J4125 CPU @ 2.00GHz (4 cores, 4 threads)
ZFS

Found two topics about this.
One with 1.5k reads, the other with 3k. Maybe there is a need for this indeed ;-) ?

Try to implement this with actual possibilities: https://www.rfc-editor.org/rfc/rfc4890
Multiple one-liners for reaching this is a pain.

Now, December 2018, every attempt to migrate from 2.2.4 to 18.7 via backup fails in early stages. Even with single parts like Interfaces, DHCP or Rulesets. Trying with spare APU. Sometimes even fully freeze after startup beep. Have many Rules, many dhcp fixed leases. Fully IPv4 and IPv6 usage. Multiple subnets. Three physical interfaces, one with 5 VLAN's. Im not complaining, but i think the differences are now too big. For me the effort to rebuild the configuration is too expensive. Maybe there is a way over API.

Hallo,
bin neu hier und bereite mich langsam darauf vor den Übergang von pfSense nach opnsense Vorzubereiten.
Ich bin sehr zufrieden mit den APU's. Aber ich arbeite mit den SSD's. Darf man fragen, wieso ihr beim Preis von <20€ für die 16G SSD noch auf SD setzt?