Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

TCP checksum #1223

Open
treiher opened this issue Jul 2, 2021 · 0 comments
Open

TCP checksum #1223

treiher opened this issue Jul 2, 2021 · 0 comments
Labels
examples
Projects
RecordFlux Future

Comments

@treiher
Copy link
Collaborator

treiher commented Jul 2, 2021 •
edited
Loading

The calculation of the TCP checksum requires access to fields of the IP packet:

The checksum also covers a 96 bit pseudo header conceptually prefixed to the TCP header. This pseudo header contains the Source Address, the Destination Address, the Protocol, and TCP length.

The current message specifications for IP packets and TCP segments are independent of each other, and thus it is not possible to reference fields of an IP packet from a TCP segment. One possible solution would be removing the independence between the message specifications, e.g., by merging the IP packet and the TCP segment specification into one combined TCP/IP message. Another solution could be the use of parameterized messages.
@treiher treiher mentioned this issue Jul 2, 2021
Merged
@treiher treiher mentioned this issue Aug 10, 2021
Closed
@treiher treiher transferred this issue from Componolit/RecordFlux-specifications Oct 7, 2022
@treiher treiher added this to Medium in RecordFlux Future via automation Oct 7, 2022
@senier senier moved this from Medium to Low in RecordFlux Future Nov 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
examples
Projects
No open projects
RecordFlux Future
  
Low
Milestone
No milestone
Development

No branches or pull requests
1 participant
@treiher