4. Patches

4.1. Error during the first restart following an update to v2.5.4.0

In some cases, following the update to v2.5.4.0, a problem may occur during the first restart

This problem is fixed in v2.5.4.1.

4.2. Blocking of the update in v2.5.4.0

If the /boot is full, the GCap update might get stuck.

This problem is fixed in v2.5.4.1.

4.3. After the update, error in executing commands with certain hardware versions

Some commands are non-functional for certain hardware versions following an update to 2.5.4.0.

This problem is fixed in v2.5.4.1.

4.4. Sigflow: error when starting the detection engine

On some GCap models, the detection engine does not start if more than two capture interfaces are enabled.

This problem is fixed in v2.5.4.1.

4.5. Sigflow: XDP filters do not apply correctly

In some cases, the XDP filters do not apply correctly.

This problem is fixed in v2.5.4.1.

4.6. Sigflow: receiving specific packets from the Modbus protocol may cause a restart of the engine

When activating the Modbus protocol, receiving a specific packet can cause the engine to restart

This problem is fixed in v2.5.4.1.

4.7. Netdata: absence of certain metrics

Some metrics are no longer retrieved by Netdata in version 2.5.4.0.

This problem is fixed in v2.5.4.1.

4.8. Sigflow: error when starting the detection engine

In some cases, the Sigflow detection engine does not start correctly when the system is initialized.

This problem is fixed in v2.5.4.2.

4.9. Netdata: erroneous value

In some cases, Netdata returns an erroneous value for the status of the detection engine.

This problem is fixed in v2.5.4.2.

4.10. System: Inadequate performance settings

Some system settings are not optimized for performance.

This problem is fixed in v2.5.4.2.

4.11. System: unable to install

In some cases, access to the WebUI is not possible.

This problem is fixed in v2.5.4.2.

4.12. Sigflow: Problem with cluster interfaces

When using cluster interface, a large drop of packets could occur.

This problem is fixed in v2.5.4.2.

4.13. Sigflow: memory allocation issue for some streams

Memory allocation for some streams is not optimized.

This problem is fixed in v2.5.4.2.

4.14. System: GCap storage space is running out

When analyzing a large amount of streaming streams, the GCap's storage space can become saturated.

This problem is fixed in v2.5.4.2.

4.15. System: CPU distribution

For some GCap models, the CPU distribution is not optimal.

This problem is fixed in v2.5.4.2.

4.17. Sigflow: options for debugging

Some options for system debugging are enabled by default.

This problem is fixed in v2.5.4.2.

4.18. Update: problem on restart

A problem may occur when restarting the system after an update.

This problem is fixed in v2.5.4.2.