Time/Date wrong after a power cycle, tough to recover

[superm1]

Describe the bug Quite recently I've noticed that my date and time are wrong when the system power cycles. This used to be OK because NTP would recover things just fine, but lately they're so far off that the certificate for my wpa_supplicant-udmpro won't fly:

eth4: CTRL-EVENT-EAP-TLS-CERT-ERROR reason=3 depth=0 subject='/C=US/ST=Michigan/L=Southfield/O=ATT Services Inc/OU=OCATS/CN=aut03lsanca.lsanca.sbcglobal.net' err='certificate is not yet valid'
SSL: SSL3 alert: write (local SSL3 detected an error):fatal:bad certificate
OpenSSL: openssl_handshake - SSL_connect error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed
eth4: CTRL-EVENT-EAP-FAILURE EAP authentication failed

Now since I can't get things up and running I can't get to the web until I fix the date/time. To make matters worse WPA2 enterprise won't authenticate any Wifi clients. This inevitably means I need to plug in something with Ethernet that doesn't need 802.1x, SSH in to the UDM, and then manually run the date -s command and then restart the docker container for wpa supplicant.

A clear and concise description of what the bug is.

To Reproduce Steps to reproduce the behavior: Reboot the machine.

Expected behavior Internet comes back up on it's own.

UDM Information

• Variant: UDM base
• Firmware Version: 1.12.22
• Controller Version: 7.2.97

Additional context Add any other context about the problem here.

I suspect this problem has been there all along, but I've noticed it now because the skew is so much further on the date for the cert to "hardcoded" date in the firmware.

I don't really know where the default date comes from. It's "October 2022". Perhaps it's a hardcoded date of when the firmware was made? In that case upgrading firmware to a newer version might "get me by" for a little bit if it's less of a skew. I'm always super wary of upgrading the firmware on the UDM in fear that these scripts will stop working though too.