Sponsored Content
Special Forums IP Networking Safe port number to use for custom purpose? Post 302741349 by tay9000 on Saturday 8th of December 2012 07:24:34 AM
Old 12-08-2012
Safe port number to use for custom purpose?

Hello, this is a really quick question that should be easy to answer. I want to forward a certain port through a firewall. I know 0-1024 are out of the question and 1024-49151 are considered "registered" ports and 49152-65535 are dynamic or private. I want to be sure I pick a port that won't ever be used by another application. So should I pick something in the 49152-65535 range or 1024-49151 range? I am guessing 1024-49151 but most of the servers in this network will be using this forwarded port so I don't want to run into the possibility of another application using the port I picked and then having to customize that installation. Thanks!
 

9 More Discussions You Might Find Interesting

1. Cybersecurity

get number of a port

Hello every one. I work in a LAN with many application server. Each one use a different port. What command permit to obtain the number of these port. thanks (2 Replies)
Discussion started by: hoang
2 Replies

2. UNIX for Dummies Questions & Answers

Need to know port number

Hi expert, I wanted to know in which port my apache is running in solaris box thanks Shaan (1 Reply)
Discussion started by: shaan_dmp
1 Replies

3. UNIX for Dummies Questions & Answers

port number

hi all i want to connect a system, how can i know the port number of a system. (2 Replies)
Discussion started by: tukuna82
2 Replies

4. Solaris

Async-Signal-Safe versus MT-Safe

Hi, I am Solaris 9 developer and notice that the documentation does not provide a clear notion of the inherent concurrency in routines defined as "Async-Signal-Safe". Routines defined as "MT-Safe" obviously have the best level of concurrency, compared to normal "Safe" interfaces. I have... (1 Reply)
Discussion started by: tristan12
1 Replies

5. UNIX for Dummies Questions & Answers

Hitting with custom port in CLOSE_WAIT state for long time in solaris 10

Hi, Occasionally I am getting the port state in CLOSE_WAIT for long time in the solaris server. I am not sure is it application problem or not. Because we are using port 9009 for Tomcat process in our web application, some time when I start the application, the port 9009 is in CLOSE_WAIT... (0 Replies)
Discussion started by: mgmk.84
0 Replies

6. IP Networking

Sending data from DELL OMSA SNMP and Custom SNMP MIB to same UDP port 161

Hi , Currently DELL OMSA SNMP sends data through default udp port 161.I want my custom SNMP MIB also to send data in the same udp port 161.Whether its possible.If yes where to configure .I tried starting my custom MIB in udp port 161,but it throws port already in use.Kindly guide. (0 Replies)
Discussion started by: prabakar4all
0 Replies

7. Red Hat

Sending data from DELL OMSA SNMP and Custom SNMP MIB to same UDP port 161

Hi , Currently DELL OMSA SNMP sends data through default udp port 161.I want my custom SNMP MIB also to send data in the same udp port 161.Whether its possible.If yes where to configure .I tried starting my custom MIB in udp port 161,but it throws port already in use.Kindly guide. (1 Reply)
Discussion started by: prabakar4all
1 Replies

8. AIX

Safe Number of Disks Assigned to a VIO Server

Is there any sort of best practice as to how many disks should be assigned to a VIO server? I currently have around 190-ish. All of my VIO servers can see those disks. Can anyone tell me how many you have on your VIO servers? (3 Replies)
Discussion started by: kah00na
3 Replies

9. Solaris

How to find port number wwn of particular port on dual port HBA,?

please find the below o/p for your reference bash-3.00# fcinfo hba-port HBA Port WWN: 21000024ff295a34 OS Device Name: /dev/cfg/c2 Manufacturer: QLogic Corp. Model: 375-3356-02 Firmware Version: 05.03.02 FCode/BIOS Version: BIOS: 2.02; fcode: 2.01;... (3 Replies)
Discussion started by: sb200
3 Replies
straps(8)							 Tnm Tcl Extension							 straps(8)

__________________________________________________________________________________________________________________________________________________

NAME
straps - A simple SNMP trap multiplexer. SYNOPSIS
straps [ port ] _________________________________________________________________ DESCRIPTION
The straps trap daemon listens on the snmp-trap port (usually port 162/udp) for incoming SNMP trap or inform messages and forwards them to all connected clients (like scotty). The optional port argument allows to use the straps daemon to forward messages received on a non stan- dard SNMP trap port. However, port numbers below 1024 will be rejected. Clients connect to the straps daemon by opening the AF_UNIX domain stream socket /tmp/.straps-port. Thus, the default AF_UNIX domain stream socket is named /tmp/.straps-162. Received messages are forwarded using the following format: 4 byte IP address of the sender (network-byte-order). 2 byte Port number of the sender (network byte order). 4 byte Length of the trap message (host-byte-order). n bytes The trap message itself. The straps daemon must be installed setuid root because normal operating systems require root permissions to open the standard SNMP trap port 162/udp. The straps daemon rejects all port numbers below 1024 in order to protect the system security. SEE ALSO
scotty(1), tkined(1), Tnm(n) AUTHORS
Erik Schoenfelder <schoenfr@gaertner.de> Juergen Schoenwaelder <schoenw@cs.utwente.nl> Tnm straps(8)
All times are GMT -4. The time now is 02:50 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy