Fix network target waited on boot
We resolved a bug for which the network systemd target waited on boot was not sufficient in guaranteeing that all interfaces were actually ready, causing possibly some services failing to bind, under certain circumstances.
List of updated packages
To solve the issues mentioned above, the following packages have been updated for NetEye 4.43:
neteye,neteye-stable,neteye-testingto version4.43.0-2neteye-satellite-manager,neteye-satellite-manager-autosetupto version0.49.1-1elastic-agent,elastic-agent-autosetup,elastic-agent-neteye-config,elastic-stack-configurator,elasticsearch,elasticsearch-autosetup,elasticsearch-neteye-config,elasticsearch-xpack-license,filebeat,filebeat-autosetup,filebeat-neteye-config,kibana,kibana-autosetup,kibana-neteye-config,logstash,logstash-autosetup,logstash-neteye-config,logstash-neteye-config-autosetupto version8.18.3_neteye3.81.7-1
Davide Sbetti
Hi! I'm Davide and I'm a Software Developer with the R&D Team in the "IT System & Service Management Solutions" group here at Würth Phoenix. IT has been a passion for me ever since I was a child, and so the direction of my studies was...never in any doubt! Lately, my interests have focused in particular on data science techniques and the training of machine learning models.
Author
Latest posts by Davide Sbetti
26. 06. 2025
Automation, Development, Documentation, NetEye
Building (and Customizing) Documentation for Your Ansible Collections