Sponsored Content
Special Forums IP Networking Help determining what's blocking ports Post 302269339 by Lazydog on Wednesday 17th of December 2008 12:05:02 PM
Old 12-17-2008
OK, do a TRACEROUTE to get the path that the packets are traversing.
Then you will have a path of devices to check.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

determining open ports

hi all 1) how to determine available ports in a box (solaris) do i have to go for a netstat on all the ports? 2) how to block a particular port for a particular type of connection. Any help would be greatly appreciated Thanks (7 Replies)
Discussion started by: matrixmadhan
7 Replies

2. UNIX for Dummies Questions & Answers

Determining file length

How can I determine what UNIX thinks the record size of any given file is?? (1 Reply)
Discussion started by: jbrubaker
1 Replies

3. SCO

Blocking ports and reseting conections

Hi folks! We have SCO Open System V 5.0.5 here. When I type "netstat -n" I found a line mentioning a conection at the port 1025, as follows: tcp 0 0 quartzo.1025 200-203-8-90.csl.aas ESTABLISHED Here we use only conections thru ports 22,23 and 25. I would like to... (0 Replies)
Discussion started by: Marcio Moraes
0 Replies

4. Shell Programming and Scripting

Determining directory path

Hello, I have a script where I get the full directory path of the script being executed: BASE=$0 echo "BASE:" $BASE The output looks like this: BASE: /webapps/appsdev/ACURA/rlz/oses3.sh I'd like to truncate the shell name, leaving just the directory path. The directory path can be... (2 Replies)
Discussion started by: cwalsek
2 Replies

5. Shell Programming and Scripting

Problem determining file

I got the following code, it partially works. Can someone tell me why it partially doenst work? #!/bin/sh file=$1 if then echo "File is a directory" else echo "File is not a directory!" fi heres the output: philip@philip-laptop:~/Desktop$ sh exFive.sh test.java File is... (4 Replies)
Discussion started by: philmetz
4 Replies

6. Solaris

determining miniroot revision

Hi guys I have a bunch of x4100's x4140's etc with solaris 10 update4 running on them but I suspect that when a lot of these boxes were originally built, the jumpstart process used an update2 miniroot, now as far as i understand it, the miniroot used at jumpstart is the miniroot that stays on... (1 Reply)
Discussion started by: hcclnoodles
1 Replies

7. Solaris

Blocking outgoing connection to ports/host in solaris

Hi, I want to block all outgoing connection ( the IMAP ) to my exchnage . I have to do it in my solaris server; from solaris host no outgoing connection can be made to the imap server. Please help me to configure that. I am new in solaris. Kind regards, Akhtar (2 Replies)
Discussion started by: akhtarbd
2 Replies

8. Programming

determining the IP of a function

Is there a way to determine the "Instruction Pointer" of a function in c++, and if so can someone tell me? (5 Replies)
Discussion started by: neur0n
5 Replies

9. UNIX for Dummies Questions & Answers

Determining Disk Speed

Hi, I went to a computer store and the salesman sold me a SATA cable and told me that all SATA cables are the same. Another salesman at a different store told me a cable rated for SATA 2, which I bought, MIGHT work as well as one rate for SATA 3 but it is not guaranteed. I decided to run a... (3 Replies)
Discussion started by: mojoman
3 Replies

10. Programming

Which are blocking and non-blocking api's in sockets in C ?

among the below socket programming api's, please let me know which are blocking and non-blocking. socket accept bind listen write read close (2 Replies)
Discussion started by: VSSajjan
2 Replies
TRACEROUTE(1)						      General Commands Manual						     TRACEROUTE(1)

NAME
traceroute - print the route packets take to network host SYNOPSIS
traceroute [-46FInrRTV] [-f first_ttl] [-p port] [-m max_hops] [-N concurrent_hops] [-t tos] [-w timeout] [-q nqueries] [-S source_addr] [-i interface] [-g gateway] host [packetlen] traceroute6 [options] DESCRIPTION
traceroute tracks the route packets take across a TCP/IP network on their way to a given host. It utilizes the IP protocol's time to live (TTL) field and attempts to elicit an ICMP TIME_EXCEEDED response from each gateway along the path to the host. traceroute6 is just another name for the same program, and is equivalent to invoking traceroute with the -6 option. Tracing with UDP The default mode of operation is to use UDP packets for path detection. This will send packets of a given size to a range of destination ports, usually in the high port range, and increment the destination port number for each probe packet sent). Intermediate gateways will return ICMP time exceeded errors when the packet's TTL reaches zero. When a packet reaches the remote host, and the chosen port is not in use, the host will return an ICMP port unreachable error. If the port is in use, the probe packet will be delivered to this port, more likely than not without eliciting a response. The port range is chosen so that it is rather unlikely that this port will be in use on the remote system. Tracing in UDP mode does not require super user privileges, as the Linux UDP implementation supports a so-called error queue, through which ICMP error packets related to a specific port can be delivered to the application. Tracing with ICMP In this mode, traceroute sends ICMP echo packets to the destination host, pretty much like the ping utility. ICMP tracing requires super user privilege, as it needs to open a raw socket to listen for incoming ICMP packets. Non-root users are not permitted to open such sockets for security reasons. ICMP traces are currently supported over IPv4 only. Tracing with TCP In TCP mode, traceroute will try to connect to the destination host. This causes the kernel to send a SYN packet to the remote host, again varying the TTL for each probe. The default port number used for TCP probes is 80 (http). When the probe reaches the destination host, it will either accept the connection (in case there's a service listening on this port), or respond with a TCP RST packet (in case there isn't). TCP tracing requires super user privilege, as it needs to open a raw socket to listen for incoming ICMP packets. Non-root users are not permitted to open such sockets for security reasons. ICMP traces are currently supported over IPv4 only. Caveats Many gateways are configured to limit the rate at which they will send ICMP error packets. Thus, when you run lots of traces in close suc- cession, an increasing number of gateways may "disappear", with probes timing out instead of eliciting an ICMP response. Rate limiting often happens at a granularity of 30 to 60 seconds, so do not expect things to work properly if you run more than two or three traces per minute. OPTIONS
The only required parameter is the name or IP address of the destination host. This parameter can be followed by the size of the probing packet sent to that host (40 by default). Varying the size of the packet in conjunction with the -F parameter can be used to obtain infor- mation about the MTU of individual network hops. This does not apply to TCP, which uses SYN packets to establish a path trace. Additional options are: -6, -4 Explicitly force IPv4 or IPv6 traceouting. By default, the program will try to resolve the name given, and choose the appropriate protocol automatically. If resolving a host name returns both IPv4 and IPv6 addresses, traceroute will use IPv4. Invoking the pro- gram as traceroute6 is the same as using the -6 option. -F Set the "Don't Fragment" bit. This tells intermediate routers not to fragment the packet when they find it's too big for a network hop's MTU. -f first_ttl Specifies with what TTL to start. Defaults to 1. -g gateway Tells traceroute to add an IP source routing option to the outgoing packet that tells the network to route the packet through the specified gateway. Not very useful, because most routers have disabled source routing for security reasons. -I Use ICMP ECHO instead of UDP packets when probing the route. This option is available to the super user only, as normal users do not have the privileges to create raw sockets. -i interface Specifies the interface through which to traceroute should send packets. By default, the interface is selected according to the routing table. NOTE: This option changed from previous versions of traceroute! Older versions used -I to specify the interface name. -m max_hops Specifies the maximum number of hops traceroute will probe. The default value is 30. -N concurrent_hops Specifies the number of probe packets sent out simultaneously. Sending several probes concurrently can speed up traceroute consid- erably. However, when specifying a number that's too large, the destination host will start to throw away random ICMP responses (if it implements ICMP rate throttling), and traceroute will be unable to detect the final hope reliably. The default value is 6. -n Do not try to map IP addresses to host names when displaying them. -p port Specifies the UDP destination port base traceroute will use. When sending its UDP probe packets, it will send them to port + hop - 1 for each hop. If there are ports in this range in use on the destination host, traceroute will not be able to identify reliably when it has reached the destination host (probes will appear to time out). The default port is 33434; you can use -p to change this to a different value. -q numqueries Sets the number of probe packets per hop. The default value is 3. -r Bypass the normal routing tables and send directly to a host on an attached network. If the host is not on a directly-attached net- work, an error is returned. This option can be used to ping a local host through an interface that has no route through it. -R Set the loose source route option on outgoing packets, asking intermediate routers to record their address as the packet passes. This can be useful if you want to find the address of an intermediate router that has been configured to not respond to traceroute packets. This feature hasn't been implemented yet. -S source_addr Chooses an alternative source address. Note that you must select the address of one of the interfaces. By default, the address of the outgoing interface is used. -T Use TCP instead of UDP packets when probing the route. This option is available to the super user only, as this requires a raw ICMP socket, which normal users are not permitted to create. -t tos Set the IP Type of Service (TOS) and Precedence value. Useful values are 16 (low delay) and 8 (high throughput). Note that in order to use some TOS precendence values, you have to be super user. -V Print the version and exit. -w sec Wait for sec seconds before sending the next probe packet. Note that unlike older traceroute versions, this implementation will transmit several probe packets in parallel, for different hop values. However, it will never send more than 1 packet per hop value at the same time. SEE ALSO
ping(8), netstat(8). AUTHOR
Concept and command line options based on the original LBL implementation of traceroute, written by Van Jacobson. This implentation is a complete rewrite and redesign, written and copyright (C) 2000-2008 Olaf Kirch <okir@suse.de>. 4.3 Berkeley Distribution 6 December 2000 TRACEROUTE(1)
All times are GMT -4. The time now is 09:09 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy