if one reads the infos it is clear:
correct date&time is essential on every device in times of TLS1.3 always on
i was not able to find a page on the wui showing the ipfire’s system date&time
where is it shown on the wui?
or should one ask technically more correct:
why is it not shown on the wui?
also lets have some fun and list routers/firewalls
incapable of/lacking this feature like ipfire:
My guess to the why question? Trade-off decisions taken by the developers prioritizing the workload and their time and resources.
The best course of action for a user is I believe to provide a patch to introduce this functionality. The second best, open good bug report to request the feature. For good, I mean detailed. Where this data should be shown and why, at the very minimum.
I do not see the necessity for this feature.
Each additional information in the page definition produces possible errors. Because of the effort to find and correct them, this should be done for essential things only.
To see IPFire’s time just use IPFire’s NTP server in your client.
Most (all?) desktops of current OSs show time and date. If it is retrieved from IPFire, it also IPFires time and date.
@cfusco
believe it or not i am very surprised that i have to create this topic here
besides the toys from avm ive not been confronted with an appliance
not able to show the appliances time on the appliances wui so far
btw: console≠wui
and to read something like:
I do not see the necessity for this feature.
Each additional information in the page definition produces possible errors. Because of the effort to find and correct them, this should be done for essential things only.
is fantastic
@world
anyone here disagrees that system’s time is crucial
What is ‘crucial’ to know ‘the system’s time’?
It is essentially that the system ( IPFire ) has the right time. This should be ensured by the time processes. If something is wrong, you have to go to the console anyway. And there you can get the information.
Currently not sure if it makes sense but if you place a script in e.g. /usr/bin named e.g. timecheck you can execute it via ssh to see some specifics… as an example
#!/bin/bash
#
# Check system time, ntp server time and hardware clock.
# Check as addition for ntpdate functionality
#
########################################################
#
# Check NTP time via ntpdate, date and hwclock
echo -e "\nNTP Time: " && \
ntpdate -q pool.ntp.org | tail -1 | awk '{print $1, $2, $3}' && \
echo -e "\nSystem Time: " && \
date '+%d %b %T' && \
echo -e "\nHardware Clock:" && \
hwclock --show && \
echo -e "\nIs ntpdate active ?" && \
ntpdate -q pool.ntp.org
# EOF
The ssh command executed on your client machine (if linux) can be →
In my IT adminstration carrer i have used and configured many firewalls like Check Point, Palo, pfSense, OPNsense, mikrotik, ipfire, m0n0wall, and so on. But nowhere, i ever had to see the time in a GUI. Exception is to see it on the console, when debugging. Because: The thing you do, as bbitsch said, you configure NTP, and rely on it working correctly. And, except for someone messing up firewall rules for port 123, i have never seen NTP failing. And if you have fear, it will somewhen fail - There is monitoring like Icinga, Prometheus, check_mk, and many others.
So speaking for my @world: I aggree, system time is crucial - but not visibly seeing it
@ummeegge
thx for the console snipped but this topic is all about wui here.
and thx for the reminder regarding the update-dilemma
@wiesel
morning, lucky you!
maybe you can help
if you still have access to those gui/wui and can examine if there is a gui-/wui-place showing the systems time
despite the fact you possibly ignored it your whole life
@mfischer
thx for the link, nice read. so i am not the only who needs to see
the systems time at the wui
even the leader agreed the time-thing
however patch means i have to apply the patch and build ipfire myself
if so this is beyond my resources. as soon as i have the time i will try the time.cgi hack
The patch submitter said he was working on an updated version which would be supplied in a months time. After that there was no further mail message from them in at least the following 6 months that I checked. So the patch submitter never came back again.