Ipfire 196 testing verion, uptime in screenshot
This system does not have IPS or Web Proxy enabled. It is a minimally configured home setup. I included HTOP for a slightly different perspective. Will post others later with different configurations.
Here is system two. Mostly wired devices with some wireless. IPS, IP Address Blocklists, proxy, and OpenVPN running.
And here is the last IPFire. This system has a weaker processor and only 4GB RAM, but handles IPS, OVPN, DHCP, Proxy, QoS, etc. Devices on this network are almost exclusively wireless.
this is my htop of my home IPFire, wired clients (TV, voip phone, NAS, printer) wifi clients (laptop, tablet smartphone, thermostat, google home, etc..)
IPS, DHCP, Proxy, URL filter, RPZ, QoS, etc.
nice guys. well done.
and i like the ipfire in windows 10. i can tell it doesnt have rounded corners. nice,
What does the winner get?
1 Like
winner gets accolades for the longest uptime.
Not necessarily a good thing.
My production system would never be longer than the next Core Update.
2 Likes
A vulnerable, out-of-date system.
Exactly.
No uptime should ever be as long as the last release if you’re patching correctly.
3 Likes
I agree, but I usually add 1 week before installing the newest release.
A week is probably fair enough.
But depending on if a release has specific updates addressing CVEs in software IPFire uses, you might want to do it sooner.
Thanks,
A G
1 Like
But moving the date of the application doesn’t change the period (uptime). 
2 Likes
What does that do? We never change anything in the releases, so you will get the same bugs on day one or day eight…
2 Likes
If there is a serious enough bug that would affect me that is brought up in the forums, I can then elect to wait til it is fixed to do the next Core Update. I know it is highly unlikely, but I am completely comfortable with that one week cushion.
1 Like