
Nmap Development mailing list archives
Re: Force TCP traceroute
From: Fyodor <fyodor () nmap org>
Date: Sat, 17 Oct 2015 20:47:29 -0700
On Fri, Oct 16, 2015 at 6:35 AM, Jochen Bartl <jochenbartl () mailbox org> wrote:
I would like to be able to trace the path via TCP-syn packets to figure out, which firewall in the path is most likely filtering the packets.
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
_______________________________________________ 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)