Nmap Development mailing list archives
Re: Force TCP traceroute
From: Jochen Bartl <jochenbartl () mailbox org>
Date: Sun, 18 Oct 2015 22:37:44 +0200
Perhaps this is a job for Nping (https://nmap.org/nping/), which comes with Nmap and is designed for special case low-level packet crafting like this. Use a command like: nping --tcp -p [portnum] --traceroute [host] Nping will start with a TTL of 1 and increase it for each packet sent. And it shows you each packet sent and received so you know exactly what is going on. Cheers, Fyodor
Thanks for your feedback Fyodor. Using Nping in this situation works for me since it comes with Nmap's Windows installation. I'll definitely need to have a closer look at it. Every now and then I work on Windows and it is good to have a familiar set of tools for troubleshooting around without installing a dozen of software packages. Regards, Jochen
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Sent through the dev mailing list https://nmap.org/mailman/listinfo/dev Archived at http://seclists.org/nmap-dev/
Current thread:
- Force TCP traceroute Jochen Bartl (Oct 16)
- Re: Force TCP traceroute Jacek Wielemborek (Oct 16)
- Re: Force TCP traceroute Jochen Bartl (Oct 16)
- Re: Force TCP traceroute Jacek Wielemborek (Oct 16)
- Re: Force TCP traceroute Jochen Bartl (Oct 16)
- Re: Force TCP traceroute Jochen Bartl (Oct 16)
- Re: Force TCP traceroute Jacek Wielemborek (Oct 16)
- Re: Force TCP traceroute Fyodor (Oct 17)
- Re: Force TCP traceroute Jochen Bartl (Oct 18)