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.

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

Feature #854 innermost ip randomization staging #881

Draft
wants to merge 3 commits into
base: 4.6.0-alpha
Choose a base branch
from

Conversation

fklassen
Copy link
Member

No description provided.

@fklassen fklassen marked this pull request as draft June 10, 2024 03:15
@fklassen fklassen changed the base branch from 4.6.0 to 4.6.0-alpha June 10, 2024 04:02
@jasonlue
Copy link

I have a local version that passed all the tests. Will try another time

@fklassen
Copy link
Member Author

I have a local version that passed all the tests. Will try another time

I must of messed up with the merge into 4.5.0. You think you can get this done in the next week or so? If so, I'll hold of 4.5.0 release, and create a 4.5.0-beta3 to get some soak time.

@jasonlue
Copy link

I'll give it a try again this weekend

@fklassen
Copy link
Member Author

I am also considering working on your PR's this weekend. If you want to colaberate contact me at tcpreplay at appneta dot com.

@jasonlue
Copy link

The MR itself is against the master. and that MR passed all the tests. I guess the merge into 4.5.0-beta3 might introduce some issues but need to compare them.

@fklassen
Copy link
Member Author

Then let me hava a look at it and see what is going wrong. Note that many CVEs have been fixed in this area, and every peek into a packet must be tested for overruns. Otherwise we will have a new round of bugs opened against this PR.

@fklassen
Copy link
Member Author

I included #853 to 4.5.0-beta3 and will let it sit there a about a week so people can test.

Although I would like to see this one go this release, I feel it should go into the next one. But I want to check with you first. If you have been working on this and will have it done soon, I may consider extending 4.5.0 release.

I'm not sure if you want to take this on, or if you want me to. I would like to see:

  • all the tests pass (may need to update test result files if new results are superior)
  • some kind of option that lets someone select level
    • e.g. --unique-ip-level which accepts a number, inner, outer etc. Default is probable outer.

@jasonlue
Copy link

jasonlue commented Jul 3, 2024

It's fine to go to the next release, giving more time for feedback, and to figure tests out. --unique-ip-level is a good idea. I can add it in relatively easily.

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.

3 participants