Not really, as there is no easy way of installing an externally provided package on IPFire. Pakfire is currently solely designed to install packages from IPFire repositories and packages are also dependent on the core update they where compiled on.
True, but most, if not all of those packages won’t break compatibility with external clients/servers if applicable.
Zabbix agent however, if we would ship v7.0 with IPFire, breaks compatibility with Zabbix 6.0 which is still fully supported by Zabbix and still gets bug- and security fixes.
So many companies (including the one I work for), will still be using 6.0 for a while and I don’t want to break things for them (in case they use IPFire). After all, upgrading to Zabbix Agent 7.0 would only bring a few (handy) enhancements (see my first post) but main functionality would remain the same.
Hence my call out here, to check if there actually are IPFire users still using Zabbix 6.0…
The current reactions however do not indicate that there are still Zabbix 6.x users among the IPFire users here so I may indeed switch to agent 7.0 in upcoming months.
Great, welcome to the club! Zabbix has its quirks, but is extremely flexible and versatile with a lively community so you will have a lot of fun experimenting with it. Also checkout my post here: Installing complementary monitoring with or on the IPFire server - #10 by robinr1 for a few extra starting tips.
I do recommend however, in a company setting, to stay on .0 LTS versions as the .2 and .4 releases stop getting updates immediately whenever a new version is released. So when you don’t have the time or resources to upgrade immediately, your instance may become vulnerable to security issues, or bugs may pop up that won’t get a fix anymore. A small single instance is upgraded easily, but when it grows over time and monitors thousands of hosts with hundreds of different templates using dozens of different monitoring methods having large history and trend datasets in the DB and possibly many Zabbix Proxies connecting to it and/or a HA setup. It will start taking some serious planning and time investment to upgrade to a next version smoothly. Staying on LTS keeps the pressure lower to upgrade immediately and avoids the scenario where on one day you are suddenly forced to upgrade on short term. And it also gives you the luxury of waiting at least a few minor releases until the biggest new bugs possibly introduced in a new major version, are fixed 