You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
See https://github.com/insomniacslk/dublin-traceroute
From this link:
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.The text was updated successfully, but these errors were encountered: