Re: netstat output
On Mon, Jun 10, 2002 at 01:17:02PM -0400, James wrote: I use: netstat -vat | grep LISTEN That will tell you everything that is really listening on your server. Not really, IIRC it will not show you udp servers. You might want to check Tiger's test: check_listeningprocs Code snippet: $NETSTAT -ptuan | $GREP -v STREAM | while read type x y local remote listen proc do ... done type: udp or tcp proc: includes pid and listening process name local: includes socket number and address Regards Javi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: netstat output
On Tue, 2002-06-11 at 11:39, Javier Fernández-Sanguino Peña wrote: On Mon, Jun 10, 2002 at 01:17:02PM -0400, James wrote: I use: netstat -vat | grep LISTEN That will tell you everything that is really listening on your server. Not really, IIRC it will not show you udp servers. You might want to check Tiger's test: check_listeningprocs Code snippet: $NETSTAT -ptuan | $GREP -v STREAM | As a native dutch speaker I find it very easy to remember 'netstat -tulpen': -t: tcp -u: udp -l: show only listening sockets -p: show pid and program using the socket -e: display aditional information. -n: numeric output This gives you all the information you want, without the need to grep the output. -- Tot ziens, Bart-Jan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: netstat output
On Tue, Jun 11, 2002 at 11:57:34AM +0200, Bart-Jan Vrielink wrote: As a native dutch speaker I find it very easy to remember 'netstat -tulpen': -t: tcp -u: udp -l: show only listening sockets -p: show pid and program using the socket -e: display aditional information. -n: numeric output This gives you all the information you want, without the need to grep the output. Nice, will check and (probably) modify the tiger script. Javi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: netstat output
Ryan J Goss wrote: When I do a netstat -an, how do I properly decipher the output? To me it looks like a lot of ports are listening, is there a way to determine what daemon is running on those ports? netstat -anp will tell you which processes. lsof -i :port will tell you more specifically who (e.g. lsof -i :25) If you don't have lsof installed...get it. It's good for you. Mike Shappe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: netstat output
I use: netstat -vat | grep LISTEN That will tell you everything that is really listening on your server. You should be able to use lsof to find out what is actually listening on those ports. - James -Original Message- From: Ryan J Goss [mailto:[EMAIL PROTECTED] Sent: Monday, June 10, 2002 1:04 PM To: Debian security mailing list Subject: netstat output When I do a netstat -an, how do I properly decipher the output? To me it looks like a lot of ports are listening, is there a way to determine what daemon is running on those ports? --Ryan Goss [EMAIL PROTECTED] Systems Staff Counting in octal is just like counting in decimal--if you don't use your thumbs. -- Tom Lehrer -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: netstat output
Do netstat -anp as root instead, it gives process pid and name -Original Message- From: Ryan J Goss [EMAIL PROTECTED] Date: Mon, 10 Jun 2002 12:04:03 -0500 (CDT) Subject: netstat output When I do a netstat -an, how do I properly decipher the output? To me it looks like a lot of ports are listening, is there a way to determine what daemon is running on those ports? --Ryan Goss [EMAIL PROTECTED] Systems Staff Counting in octal is just like counting in decimal--if you don't use your thumbs. -- Tom Lehrer -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
