-
Notifications
You must be signed in to change notification settings - Fork 5
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.
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
total WIP of adding ipv4 defrag #22
base: master
Are you sure you want to change the base?
Conversation
Still messing around with this. Reading https://tools.ietf.org/html/rfc815 this may be a bit more complicated than what is expressed in this MR. |
…d be able to take the payloads in order. Right now, I have 2 components: 1 the hole checker, and the other is a btreemap of that will allow us to read packets in order once we know no gaps exist. Perhaps these could be combined, but to make testing easier for now they are seperate.
…e in case of fragments
Thinking we need to pass a FlowParsingContext, this context could dictate if ip fragmentation happens, and allow for state of fragmentation buffers to be stored. Also, could like to make fragmentation more generic if possible, however more research is needed on ipv6 fragmentation. |
@kornstar11 there is no fragmentation on IPv6. This is only for IPv4. On IPv6 they removed fragmentation and let the application or higher protocols (TCP) do any fragmentation |
Work to add a ipv4 defrag component to capture ipv4 packets, and when ready to reassemble it should hand back the reassembled payload.