Sponsored Content
Top Forums UNIX for Dummies Questions & Answers What prot is a process listening on? Post 302143622 by Le Badger on Friday 2nd of November 2007 07:02:27 AM
Old 11-02-2007
What prot is a process listening on?

Hi,

Bit of a newbie question . . .

How can I detrimine what TCP port a particular process is listening on?

TIA.
 

8 More Discussions You Might Find Interesting

1. IP Networking

port not listening..

Hi.. I am using HPux11.0 i want to know if server not listening to a tcp port what should we do to resolve the problem.... in /etc/services tcp port 7108/tcp is mentioned for some perticular application.. while starting that application error is coming could not establish listening address... (1 Reply)
Discussion started by: Prafulla
1 Replies

2. What is on Your Mind?

So... What are you listening to?

Hi guys, lets make this more interesting... I'm sure you listen to something when your working on a project or something... I know, I do, helps with concentration. Track: ±¯¸èÖ®Íõ (King of sad songs) Artist: -îǧ‹Ã Miriam Yeung Lovely forum BTW! :D (33 Replies)
Discussion started by: hype.it
33 Replies

3. What is on Your Mind?

What are you listening to right now?

This is has been posted many times before... It is not in this forum as of now, so I have decided to put it here :D I'm listening to The Outsiders (AKA Hell is for Heros Part I) by Modern Life is War.... what about ya'll? (4 Replies)
Discussion started by: Mars8082686
4 Replies

4. Ubuntu

f prot

i m new to linux i m not able to install F PROT antivirus how will i do that pls help (1 Reply)
Discussion started by: mallicksaran
1 Replies

5. SuSE

Apache2 No listening Sockets available

I installed Apache2 and Gadmin-Httpd on Suse after installation I got a error message no listening sockets available when start apache. Please advise, I check lot of forums but unable to find solution (4 Replies)
Discussion started by: real-chess
4 Replies

6. Red Hat

No process ID for listening ports

How can I have ports that are listening without processes being associated with them? root@ldv002 # netstat -ltnup Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0... (2 Replies)
Discussion started by: Padow
2 Replies

7. AIX

Process running but not listening

Hello guys I am experiencing a very strange behavior on one of our AIX servers. We have an application with several processes that listen on several port numbers. Sometimes we receive complains that people cannot connect to the server on a specific port that is used by one the application... (6 Replies)
Discussion started by: abohmeed
6 Replies

8. Shell Programming and Scripting

Is my Socket Free or Listening

Hi, bash-3.2$ uname -a Linux mymac 2.6.18-409.el5 #1 SMP Fri Feb 12 06:37:28 EST 2016 x86_64 x86_64 x86_64 GNU/Linux bash-3.2$ telnet 10.12.228.40 13900 Trying 10.12.228.40... telnet: connect to address 10.12.228.40: Connection refused bash-3.2$ telnet 10.12.228.40 23900 Trying... (2 Replies)
Discussion started by: mohtashims
2 Replies
BLACKHOLE(4)						   BSD Kernel Interfaces Manual 					      BLACKHOLE(4)

NAME
blackhole -- a sysctl(8) MIB for manipulating behaviour in respect of refused TCP or UDP connection attempts SYNOPSIS
sysctl net.inet.tcp.blackhole[=[0 | 1 | 2]] sysctl net.inet.udp.blackhole[=[0 | 1]] DESCRIPTION
The blackhole sysctl(8) MIB is used to control system behaviour when connection requests are received on TCP or UDP ports where there is no socket listening. Normal behaviour, when a TCP SYN segment is received on a port where there is no socket accepting connections, is for the system to return a RST segment, and drop the connection. The connecting system will see this as a ``Connection refused''. By setting the TCP blackhole MIB to a numeric value of one, the incoming SYN segment is merely dropped, and no RST is sent, making the system appear as a blackhole. By setting the MIB value to two, any segment arriving on a closed port is dropped without returning a RST. This provides some degree of protection against stealth port scans. In the UDP instance, enabling blackhole behaviour turns off the sending of an ICMP port unreachable message in response to a UDP datagram which arrives on a port where there is no socket listening. It must be noted that this behaviour will prevent remote systems from running traceroute(8) to a system. The blackhole behaviour is useful to slow down anyone who is port scanning a system, attempting to detect vulnerable services on a system. It could potentially also slow down someone who is attempting a denial of service attack. WARNING
The TCP and UDP blackhole features should not be regarded as a replacement for firewall solutions. Better security would consist of the blackhole sysctl(8) MIB used in conjuction with one of the available firewall packages. This mechanism is not a substitute for securing a system. It should be used together with other security mechanisms. SEE ALSO
ip(4), tcp(4), udp(4), ipf(8), ipfw(8), pfctl(8), sysctl(8) HISTORY
The TCP and UDP blackhole MIBs first appeared in FreeBSD 4.0. AUTHORS
Geoffrey M. Rehmet BSD
January 1, 2007 BSD
All times are GMT -4. The time now is 12:46 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy