Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: V2.0.8.25, V2.0.8.26, V2.0.8.27, V2.0.8.28, V2.0.8.29, V2.0.8.30, V2.0.8.31, V2.0.8.32, V2.0.8.33, V2.0.8.34, V2.1.10.0, V2.1.11.0, V2.1.11.1, V2.1.11.2, V2.1.11.3, V2.1.11.4, V2.1.11.5, V2.1.11.6, V2.1.11.7, V2.1.11.8, V2.1.11.9, V2.1.11.10, V2.1.11.11, V2.1.12.0, V2.1.13.0, V2.1.14.0, V2.1.14.1, V2.1.14.2, V2.1.15.0
-
Component/s: Drivers
-
Labels:None
-
Account:SDO rcX (SDORCX)
Description
The Driver EDD function check the recived frame for correct IP checksum. This calculation drops IP frames where the correct IP checksum is 0xFFFF.
Currently the IP checksum is checked by calculating the checksum again, and comparing the result with the received checksum. This works for all possible checksum correct, except when the checksum is 0xFFFF.
The recommended way to verify the checksum is to compute it over the complete header (including the actual CRC) and to compare it with 0xFFFF (see https://tools.ietf.org/html/rfc1624 - chapter 5).
This bug emerges if an intermediate system changes a value in the header and computes the checksum via an incremental update instead of calculating it from scratch. An example is given in RFC 1624.
Attachments
Issue Links
- is blocked by
-
PSEIS-975
Update rcX to V2.1.15.1
-
- Closed
-