I updated to 190 this morning, and it worked without problems, as always.
But the page (in German) Status - Verbindungen seems a bit “broken”. There is no longer a way to sort the entries in the list. At least, I haven’t found a way. Without the possibility to sort, this page isn’t really useful for me.
And second, there is an explanation field in pink labeled with Wireguard, but no way to activate it in Ipfire. And I would really like to have Wireguard.
Best wishes and a happy new year to all of you
Ingo
As Adolf mentioned, the change in the Connections page behaviour was actually introduced with Core Update 188. The table is now ordered by remaining lifetime (based on conntrack) rather than being sortable by column. We appreciate how that might be less convenient, but it’s currently the expected behaviour.
Regarding WireGuard, you’ve spotted an early placeholder. The feature is still undergoing development and testing, so it’s not yet available in the official builds. We’re all excited to see WireGuard included in IPFire, and we hope to have it ready soon. If you’re as enthusiastic about it as we are, please consider making a donation to the IPFire project—every contribution helps fund ongoing development work, including new features like WireGuard.
Many thanks for your feedback, and if you have any further questions, just let us know.
I’m sorry for not recognizing the sorting issue earlier. I’m using the connection list pretty often. So, I should have seen that before. My main use of this list is to observe, which hosts/nets are connected or try to connect. The remaining lifetime is of near-to-zero interest in my setup. And the link shows, that others miss this feature, too.
But one more thing concerning the connection list. Very often, I have hundreds of entries for 127.0.0.1 pointing to 127.0.0.1 in the list. This blows up the list extremely. In these cases, I get 30, 40, or more screen pages. This has always been annoying, but without sorting even more. Or is there a way to suppress the localhost entries?
Thanks for clarifying how you use the connection list. The remaining lifetime view can indeed be less helpful for certain use cases, and we understand it’s frustrating without the ability to sort or filter.
Regarding the many localhost-to-localhost (127.0.0.1) entries, there isn’t a built-in way in the IPFire WUI to hide or suppress them. Since this list is primarily intended for a quick real-time snapshot of current traffic, it will display everything passing through conntrack—including localhost connections.
If you’re looking for more robust or long-term monitoring, there are several add-ons available. For example, Observium Agent or Zabbix Agent can send IPFire’s data to your Observium or Zabbix server (running elsewhere). You can find these and other add-ons here:
These dedicated tools provide historical data, more detailed analysis, and comprehensive monitoring that goes beyond IPFire’s built-in “Connections” snapshot page.
If you have more questions or need any additional tips, just let us know!
building Netdata like described in the linked topic won´t work with the new IPFire build system. Like e.g. Wazuh, Netdata downloads data while the building process (a lot of go souces too), earlier it was possible to give resolve.conf in chroot an DNS address which was a hack of the building system to be able to build those packages. Now it is more complicated (even possible) and it is good that it is more complicated since it is not a good practice to download other sources while the building process of an HLFS but IMO it won´t also work with the IPFire standards for an merge request.
netdata has moved to a 2.x branch which is now at 2.1.1
Also note that if you want to use the netdataUI to visualise the data on a computer on your network then you will need to install a netdata binary on that system as the netdataUI is closed source and is only provided integrated into one of the netdata binary packages for various architectures.
I believe that none of the Linux distros provide the netdataUI, only the netdata agent, certainly that is the case for the Arch Linux package.
I wonder if the addition of Netdata by ummeegge would also be useful.