4. Patches

4.1. 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 issue is fixed in v2.5.5.0.

4.2. 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 issue is fixed in v2.5.5.0.

4.3. Sigflow: XDP filters are not applying correctly

In some cases, the XDP filters do not apply correctly.
This issue is fixed in v2.5.5.0.

4.4. 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 issue is fixed in v2.5.5.0.

4.5. Netdata: absence of certain metrics

Some metrics are no longer retrieved by Netdata in version 2.5.4.0.
This issue is fixed in v2.5.5.0.

4.6. Sigflow: problem starting the detection engine

In some cases, the Sigflow detection engine does not start correctly when the system is initialized.
This issue is fixed in v2.5.5.0.

4.7. Netdata: erroneous value

In some cases, Netdata returns an erroneous value for the status of the detection engine.
This issue is fixed in v2.5.5.0.

4.8. System: Inadequate performance settings

Some system settings are not optimized for performance.
This issue is fixed in v2.5.5.0.

4.9. System: unable to install

In some cases, it is not possible to install GCap.
This issue is fixed in v2.5.5.0.

4.10. Sigflow: Problem with cluster interfaces

When using a cluster interface, significant packet loss may occur.
This issue is fixed in v2.5.5.0.

4.11. Sigflow: memory allocation issue for some streams

Memory allocation for some streams is not optimized.
This issue is fixed in v2.5.5.0.

4.12. System: GCap storage space is running out

When analyzing a large amount of streaming streams, the GCap's storage space can become saturated.
This issue is fixed in v2.5.5.0.

4.13. System: CPU distribution

For some GCap models, the CPU distribution is not optimal.
This issue is fixed in v2.5.5.0.

4.14. System: default selection in the boot menu

Following a GCap update, it is possible to inadvertently select the entry that triggers a failback.
This issue is fixed in v2.5.5.0.

4.15. Sigflow: options for debugging

Some options for system debugging are enabled by default.
This issue is fixed in v2.5.5.0.

4.16. Update: problem on restart

A problem may occur when restarting the system after an update.
This issue is fixed in v2.5.5.0.

4.17. Sigflow: Reconstruction problem for the http2 protocol

A problem with rebuilding the HTTP2 protocol may occur in some cases.
This issue is fixed in v2.5.5.0.