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

Traceroute do not resolve #599

Open
khilmar opened this issue Jan 16, 2025 · 8 comments
Open

Traceroute do not resolve #599

khilmar opened this issue Jan 16, 2025 · 8 comments

Comments

@khilmar
Copy link

khilmar commented Jan 16, 2025

Can we get a -n flag for traceroute that prints the server's with just ip addresses and also to avoid a name server lookup?

@jimaek
Copy link
Member

jimaek commented Jan 17, 2025

Sure I think we can do it. But can you please tell us more about the use-case? To better understand what the end goal is and help us set priorities.

@khilmar
Copy link
Author

khilmar commented Jan 17, 2025

just to provide a quicker output. it takes slightly longer when ip addresses have to be resolved to hostname's

From traceroute man page:
-n
Do not try to map IP addresses to host names when displaying them.

https://linux.die.net/man/8/traceroute

@jimaek
Copy link
Member

jimaek commented Jan 19, 2025

Indeed the difference in speed is significant. We should do it, just need to make sure we handle correctly the new output format

@MartinKolarik
Copy link
Member

The difference is negligible in most cases. It'll likely take you more time to write the two extra characters or click the switch than it would save on the execution time. I'd rather not add new options without serious consideration, as each tool we support has tens of them.

@jimaek
Copy link
Member

jimaek commented Jan 19, 2025

On a large scale if someone asks for hundreds of traceroutes it would make a lot of difference

@MartinKolarik
Copy link
Member

MartinKolarik commented Jan 20, 2025

It doesn't matter how many you run if the difference is < 100 ms on a measurement that takes 5 - 10 seconds. Traceroute is usually slow because of waiting for the tracing packets, not because of DNS.

@jimaek
Copy link
Member

jimaek commented Jan 20, 2025

For me the difference was closer to 3-4 seconds

@khilmar
Copy link
Author

khilmar commented Jan 21, 2025

@MartinKolarik Respectfully, you should let the users decide if that's a negligible difference or not. Giving us another way to fine-tune our tests would make it easier to tweak things to fit our needs without imposing a one size fits all approach

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

3 participants