Skip to content

Conversation

joelanders
Copy link
Contributor

No description provided.

@willscott
Copy link
Contributor

Main issue to flag is that we expect most common clients to not have root access / raw socket support, which will limit the ability of the client to control fragmentation / sending behavior.

A test helper can be privileged and change semantics at this layer in responses back to a client, and learn about the DPI behavior in the Server->Client direction.

@bassosimone
Copy link
Contributor

See measurement-kit/measurement-kit#1522 for a possible implementation of this concept. Given that we're moving towards a Go engine, measurement-kit/measurement-kit#1522 will not ever be merged in MK. Therefore, I'm linking it here, so we do remember about its existence, and then I'm going to proceed with closing the PR.

@Samboy1990
Copy link

DPI-Fragmentation-Spec

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants