Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Typically with a tar.gz file you have to gunzip to uncompress it then tar to extract it. GNU tar lets you do both on one command line:
tar tzvf <file.tar.gz>
Will show you what is in the file.
tar xzvf <file.tar.gz> will gunzip and extract what is in the file to your disk.
Usually you'll see a README file of some sort that will give you instructions on what to do with the bundle. Often the tar.gz stuff is source code that you have to run "configure" then "make" on to compile then often will have a "make install" to install what you compiled to the appropriate directory. However they don't all do it the same way (e.g. there is a Firefox tar.gz that is already compiled so you have to install it manually.)
Run the tar tzvf to see if you see any README files listed.
Typically with a tar.gz file you have to gunzip to uncompress it then tar to extract it. GNU tar lets you do both on one command line:
tar tzvf <file.tar.gz>
Will show you what is in the file.
tar xzvf <file.tar.gz> will gunzip and extract what is in the file to your disk.
Usually you'll see a README file of some sort that will give you instructions on what to do with the bundle. Often the tar.gz stuff is source code that you have to run "configure" then "make" on to compile then often will have a "make install" to install what you compiled to the appropriate directory. However they don't all do it the same way (e.g. there is a Firefox tar.gz that is already compiled so you have to install it manually.)
Run the tar tzvf to see if you see any README files listed.
The Readme file says:
Quote:
tcptraceroute -- A traceroute implementation using TCP packets
Copyright (c) 2001, 2002 Michael C. Toren <mct@toren.net>
This program is free software; you can redistribute it and/or modify it
under the terms of the GNU General Public License, version 2, as published
by the Free Software Foundation.
This program is distributed in the hope that it will be useful, but
WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY
or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License
for more details.
A copy of the GNU GPL is available as /usr/doc/copyright/GPL on Debian
systems, or on the World Wide Web at http://www.gnu.org/copyleft/gpl.html
You can also obtain it by writing to the Free Software Foundation, Inc.,
59 Temple Place - Suite 330, Boston, MA 02111-1307, USA
The files already appear (to me) to be on board and unzipped.
/home/rooster/morecols-0.3.5.1.xpi/tcptraceroute-1.4
Its just that I don't know why all the user console commands I know give, "No such file or directory".
Table of Contents
rcsE
tcptraceroute - A traceroute implementation using TCP packets
rcsOrcsS
tcptraceroute [-nNFSAE] [ -i interface ] [ -f first ttl ]
[ -l length ] [ -q number of queries ] [ -t tos ]
[ -m max ttl ] [ -p source port ] [ -s source address ]
[ -w wait time ] host [ destination port ] [ length ]
rcsCrcsTrcs
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.
It is worth noting that tcptraceroute never completely establishes a TCP connection with the destination host. If the host is not listening for incoming connections, it will respond with an RST indicating that the port is closed. If the host instead responds with a SYN|ACK, the port is known to be open, and an RST is sent by the kernel tcptraceroute is running on to tear down the connection without completing three-way handshake. This is the same half-open scanning technique that nmap(1) uses when passed the -sS flag.
rcsIrcs
-n
Display numeric output, rather than doing a reverse DNS lookup for each hop. By default, reverse lookups are never attempted on RFC1918 address space, regardless of the -n flag.
-N
Perform a reverse DNS lookup for each hop, including RFC1918 addresses.
-f
Set the initial TTL used in the first outgoing packet. The default is 1.
-m
Set the maximum TTL used in outgoing packets. The default is 30.
-p
Use the specified local TCP port in outgoing packets. The default is to obtain a free port from the kernel using bind(2). Unlike with traditional traceroute(8), this number will not increase with each hop.
-s
Set the source address for outgoing packets. See also the -i flag.
-i
Use the specified interface for outgoing packets.
-q
Set the number of probes to be sent to each hop. The default is 3.
-w
Set the timeout, in seconds, to wait for a response for each probe. The default is 3.
-S
Set the TCP SYN flag in outgoing packets. This is the default, if neither -S or -A is specified.
-A
Set the TCP ACK flag in outgoing packets. By doing so, it is possible to trace through stateless firewalls which permit outgoing TCP connections.
-E
Send ECN SYN packets, as described in RFC2481.
-t
Set the IP TOS (type of service) to be used in outgoing packets. The default is not to set any TOS.
-F
Set the IP "don't fragment" bit in outgoing packets.
-l
Set the total packet length to be used in outgoing packets. If the length is greater than the minimum size required to assemble the necessary probe packet headers, this value is automatically increased.
-d
Enable debugging, which may or may not be useful.
rcsMrcsS
Please see the examples.txt file included in the tcptraceroute distribution for a few real world examples.
To trace the path to a web server listening for connections on port 80:
tcptraceroute webserver
To trace the path to a mail server listening for connections on port 25:
tcptraceroute mailserver 25
rcsS
No error checking is performed on the source address specified by the -s flag, and it is therefore possible for tcptraceroute to send out TCP SYN packets for which it has no chance of seeing a response to.
rcsHrcs rcs rcs rcskrcs rcs rcscrcst rcs rcscrcscrcsf rcsircsa rcsprcse
Michael C. Toren <mct@toren.net>
rcsIrcsIrcsY
For updates, please see:
OK I'm a little confused. You say the files are "on board and unzipped" but the README you quote says you need to compile (the line starting with gcc). Did you do that?
As to why typing the command wouldn't work (assuming you had one) you would need:
1) To be sure the command had execute permission set for the user attempting to run it (presumably root).
2) Be sure you had /home/rooster/morecols-0.3.5.1.xpi/tcptraceroute-1.4 in your PATH variable OR type in the full command path OR cd to the directory and type ./ in front of the command.
e.g. if the command is "tcptraceroute" owned by root you'd need to be sure it had permissions like:
-rwxr-x-r-x
You'd need to include the above directory in your PATH - you could append it to existing PATH varaiable by typing:
export PATH=$PATH:/home/rooster/morecols-0.3.5.1.xpi/tcptraceroute-1.4
-OR-
You could type full path of the command:
/home/rooster/morecols-0.3.5.1.xpi/tcptraceroute-1.4/tcptraceroute
-OR-
You could
cd /home/rooster/morecols-0.3.5.1.xpi/tcptraceroute-1.4
./tcptraceroute
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
