Major issues after upgrade from 25.1.10 to 25.1.11

Started by AG_2023, July 17, 2025, 05:03:21 PM

Previous topic - Next topic
Print
Go Down Pages 1 2
User actions
July 20, 2025, 11:03:53 AM #15
Guys, this makes little sense without enough information as previously stated.
July 20, 2025, 11:51:19 AM #16
I included a file in my bug report. Note that I just found that this file is neither flagged as being too big nor is imported correctly. I cannot make claims as to if that breaks a subsequent configuration load.
Intel N100, 4* I226-V, 2* 82559, 16 GByte, 500 GByte NVME, ZTE F6005

1100 down / 800 up, Bufferbloat A+
July 22, 2025, 05:18:10 PM #17
Quote from: Monviech (Cedrik) on July 18, 2025, 04:31:09 PMits a unix timestamp

root@opn03:/usr/local/etc # date -j -f "%s" 1752053171
Wed Jul  9 11:26:11 CEST 2025


On OPNsense and other BSD systems (including macOS) it is much simpler to use like this:

 % date -r 1752053171
Wed Jul  9 11:26:11 CEST 2025

As far as I know this does not work on Linux systems.
July 23, 2025, 03:03:44 AM #18
Quote from: Fabian Wenk on July 22, 2025, 05:18:10 PMOn OPNsense and other BSD systems (including macOS) it is much simpler to use like this:

 % date -r 1752053171
Wed Jul  9 11:26:11 CEST 2025

As far as I know this does not work on Linux systems.

On Linux, it is this:

$ date -d @1752053171
Wed Jul  9 04:26:11 AM CDT 2025

Print
Go Up Pages 1 2
User actions