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

Implement Dublin Traceroute #146

Open
matthieugouel opened this issue Dec 7, 2022 · 0 comments
Open

Implement Dublin Traceroute #146

matthieugouel opened this issue Dec 7, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@matthieugouel
Copy link
Member

See https://github.com/insomniacslk/dublin-traceroute

From this link:

To detect NATs, Dublin Traceroute forges a custom IP ID in the outgoing packets, and keeps track of them in the response packets. If the response packet references an outgoing packet with different source/destination IP addresses and ports, this may indicate the presence of a NAT. In that case, the packet referenced in the response will be different from the one that was sent, and cannot be correlated anymore. However, the IP ID is expected to be unchanged (thanks to the presence of the don't-fragment bit), and it will contain a value to correlate it to one of the outgoing packets.

I think we could get this information from Caracal (maybe additional information to add to the measurement table will be required) and a minima have a new column has_nat_traversal  on the prefix table.

@matthieugouel matthieugouel added the enhancement New feature or request label Dec 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant