![]() |
|
|
|
|
|||||||
| Forums | Portal | Register | Forum Rules | FAQ | Contribute | Members List | Arcade | Search | Today's Posts | Mark Forums Read |
| UNIX for Advanced & Expert Users Advanced UNIX and Linux questions go here. Expert-to-Expert. |
|
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Tracking user | panknil | UNIX for Advanced & Expert Users | 5 | 06-25-2007 08:40 AM |
| tracking user action | xitrum | UNIX for Advanced & Expert Users | 7 | 03-07-2007 01:48 PM |
| Command Tracking | mahatma | UNIX for Advanced & Expert Users | 5 | 04-04-2006 05:30 AM |
| tracking sequence num | frustrated1 | Shell Programming and Scripting | 1 | 02-21-2006 01:34 AM |
| event number tracking | frustrated1 | Shell Programming and Scripting | 4 | 01-09-2006 04:17 AM |
|
|
Submit Tools | LinkBack | Thread Tools | Search this Thread | Display Modes |
|
#1
|
|||
|
|||
|
Tracking down the problem
Is there a way to track down what process is sending to a certain port? I have some thing pounding the network with requests to a multicast IP that doesn't exist. I have shut down all comms related processes and yet it is still there. Need a way to track the port or IP back to the process. Thanks in advance.
|
| Forum Sponsor | ||
|
|
|
#2
|
||||
|
||||
|
use "netstat" + "lsof" if they are present on your flavor of unix.
|
|
#3
|
|||
|
|||
|
That would only tell you if a UDP port was "connected" to the remote port....?
|
|
#4
|
||||
|
||||
|
Did I got the question wrong ?
Code:
lsof | grep gaim gaim 30514 sysgate 18u IPv4 97106 TCP sysgate.company.com:59973->205.188.8.226:aol (ESTABLISHED) gaim 30514 sysgate 20u IPv4 97116 TCP sysgate.company.com:35286->64.12.30.76:aol (ESTABLISHED) |
||||
| Google The UNIX and Linux Forums |