tcptraceroute is a traceroute implementation using TCP packets. The more traditional traceroute(8) sends out either UDP or ICMP ECHO packets with a TTL of one, and increments the TTL until the destination has been reached. By printing the gateways that generate ICMP time exceeded messages along the way, it is able to determine the path packets are taking to reach the destination. The problem is that with the widespread use of firewalls on the modern Internet, many of the packets that traceroute(8) sends out end up being filtered, making it impossible to completely trace the path to the destination. However, in many cases, these firewalls will permit inbound TCP packets to specific ports that hosts sitting behind the firewall are listening for connections on. By sending out TCP SYN packets instead of UDP or ICMP ECHO packets, tcptraceroute is able to bypass the most common firewall filters. WWW: http://michael.toren.net/code/tcptraceroute/ - Simon 'corecode' Schubert
UNIX traceroute(8) can already do that, see the -P option. -- Cheers, Phone: 250-387-8437 Cy Schubert Fax: 250-387-5766 Team Leader, Sun/Alpha Team Email: Cy.Schubert@osg.gov.bc.ca Open Systems Group, CITS Ministry of Management Services Province of BC FreeBSD UNIX: cy@FreeBSD.org
State Changed From-To: open->feedback This is already in the ports tree, maintained by ports@ and at version 1.2. Can you submit a diff against the port in-tree?
On Tue, 04 Jun 2002 20:16:16 -0700 Cy Schubert - CITS Open Systems Group wrote: > UNIX traceroute(8) can already do that, see the -P option. that's right. but besides that tcptraceroute is already in the ports tree (duh!) i had problems using traceroute -P TCP : it failed to catch the last hop and just produced * * * cheerz simon -- /"\ http://corecode.ath.cx/#donate \ / \ ASCII Ribbon Campaign / \ Against HTML Mail and News
Responsible Changed From-To: freebsd-ports->petef I'm working with the submitter on this.
State Changed From-To: feedback->closed Update committed w/setuid change, thanks!