10-01-2001
The ESTABLISHED sockets have a process at each end and they are communicating. Eventually the processes will invoke close(2) or shutdown(2) on the sockets and they will go away. You could also kill the processes and the exit(2) system call will close them.
When a socket completely closes, it will enter TIME_WAIT for awhile before it disappears. In your case you have two processes talking on the same host. Usually there would be two different hosts with a network connecting them. It is possible for packets to have been lost in transit. Such packets could arrive late, even after the socket has closed. If a packet arrives for a socket in TIME_WAIT, it is discarded. If you somehow discarded a socket in TIME_WAIT, you lose that protection. The socket could be reused and it will freak when any lost packets from the previous connection arrive. TIME_WAIT sockets should not last very long.
10 More Discussions You Might Find Interesting
1. IP Networking
Hi
what is the command to see the process name/application name
along with the port number, connection status ...
netstat is not giving process/application name
Is there any way to know which application is holding which port?
Thanks in advance (3 Replies)
Discussion started by: axes
3 Replies
2. UNIX for Advanced & Expert Users
Hi..,
Now, I am reading about the netstat command and its implementation. I have doubts in some options and its functionalities,
natstat - M (Which is described as display masqueraded connections), what it means?
What is Forwarding Information Base.?(--fib)
Thanks in advance,... (3 Replies)
Discussion started by: nagalenoj
3 Replies
3. BSD
For FreeBSD I use this command to determine what ports are listenning
netstat -an | grep LISTEN
is there another way, perhaps another command? (2 Replies)
Discussion started by: edgarvm
2 Replies
4. IP Networking
I can't tell what the output of the netstat command means. Is there anywhere that has this information? I tried the man pages, but they weren't helpful. (3 Replies)
Discussion started by: Ultrix
3 Replies
5. Solaris
Greetings to all,
Here is a line of output from my netstat command
cbp031.904 wdcprodhome.nfsd 98304 0 49640 0 ESTABLISHED
The only thing i recognize is the unix machine "cbp031" but what is .904 and all the other data telling me?
Thanks in advance. (3 Replies)
Discussion started by: Harleyrci
3 Replies
6. Shell Programming and Scripting
Hi,
In my project we use sftp with batch mode (password less) script in parallel for 14 sessions which connects to 2 different servers alternatively i.e. 7 connects to one server say server1 and the other 7 connects to say server 2.
Now the problem is that these 14 sessions are run in... (5 Replies)
Discussion started by: dips_ag
5 Replies
7. UNIX for Advanced & Expert Users
Hi,
I want to list the time for how long a secure connections last to my server/blade. i am using netstat command to get the same, but not sure how to get the time for how long connections is being ESTABLISHED.
netstat -na | grep 'ESTABLISHED' | grep :443 |awk '{print $4}' | cut -d: -f1 |... (1 Reply)
Discussion started by: Siddheshk
1 Replies
8. UNIX for Dummies Questions & Answers
Do I have this command correct to show all current connections/sessions my Solaris box has? It does not seem to do anything.
netstat -an | grep EST (6 Replies)
Discussion started by: SIFT3R
6 Replies
9. Red Hat
Hi
Can any body tell me about TIME_WAIT status meaning in the following command output.
# netstat -anp|grep 5000
tcp 0 0 127.0.0.1:50006 0.0.0.0:* LISTEN 5058/ccsd
tcp 0 0 0.0.0.0:50008 0.0.0.0:* ... (3 Replies)
Discussion started by: mastansaheb
3 Replies
10. OS X (Apple)
When running netstat -i from the Command Terminal,
It returns with 21 different connections..
The addresses all look like this:
::1
fe80:1::1
10:dd:b1:a5:c4:ba
with Network names like
Linke#2
fe80::8e2d
How can I delve deeper into this to clarify what is going on with my network?... (0 Replies)
Discussion started by: dwfiedler
0 Replies
ip(4p) ip(4p)
Name
ip - Internet Protocol
Syntax
#include <sys/socket.h>
#include <netinet/in.h>
s = socket(AF_INET, SOCK_RAW, 0);
Description
The IP is the transport layer protocol used by the Internet protocol family. It can be accessed through a ``raw socket'' when developing
new protocols or special purpose applications. IP sockets are connectionless and are normally used with the and calls. The call, however,
can also be used to fix the destination for future packets, in which case the or and or system calls can be used.
Outgoing packets automatically have an IP header prepended to them, based on the destination address and the protocol number the socket is
created with. Incoming packets are received with their IP headers and options intact.
Diagnostics
On failure, a socket operation returns any of the following errors:
[EISCONN] Tried to establish a connection on a socket that already had one, or tried to send a datagram with the destination address
specified when the socket was already connected.
[ENOTCONN] Tried to send a datagram, but no destination address was specified and the socket was not connected.
[ENOBUFS] The system ran out of memory for an internal data structure.
[EADDRNOTAVAIL]
Made an attempt to create a socket with a network address for which no network interface existed.
See Also
send(2), recv(2), inet(4f), intro(4n), packetfilter(4)
ip(4p)