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

Synthetic UUIDs from connection 4-tuples are not unique #69

Open
mattmathis opened this issue Apr 6, 2020 · 3 comments
Open

Synthetic UUIDs from connection 4-tuples are not unique #69

mattmathis opened this issue Apr 6, 2020 · 3 comments

Comments

@mattmathis
Copy link
Contributor

The ephemeral port space is too small, such that beacons and OAM reuse 4-tuples thousands of times.

See: SELECT * FROM mlab-sandbox.inspector.DupUnifiedUUIDs LIMIT 1000

Consider adding Julian date (and either explicitly make it opaque or parsable).

@autolabel autolabel bot added the review/triage Team should review and assign priority label Apr 6, 2020
@pboothe
Copy link
Contributor

pboothe commented Apr 13, 2020

Yes. This requires careful throught.

@autolabel autolabel bot removed the review/triage Team should review and assign priority label Apr 13, 2020
@pboothe
Copy link
Contributor

pboothe commented May 4, 2020

Add the date, make the date opaque.

@mattmathis
Copy link
Contributor Author

This applies to web100 only. Date has been added, but some heavy hitting beacons still wrap the ports pace many times per day, so some duplicate UUIDs continus.

This is good enough for joining traceroute and other stable annotations, but insufficient for pcap and other per test annotations.
Lowering to P2.

@mattmathis mattmathis added P2 and removed P1 labels Mar 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants