Sponsored Content
Full Discussion: TCP ports - TIME_WAIT
Top Forums UNIX for Advanced & Expert Users TCP ports - TIME_WAIT Post 36045 by potato-head on Monday 19th of May 2003 06:03:09 PM
Old 05-19-2003
It almost sounds as if the design should be modifed a bit-

Personally, I'd modify it to include a backlog for possible connections (The number will be something OS-specific, and I don't know what that is for SCO)- Kernel modifications sometimes allow for multiple connections to be backlogged. On top of that, I'd probably look into something to speed up what ever task is performed on the host machine, forking, threading (if you want it to be a huge task)-

Remember, you have to keep track of all opened connections, and allowing a box with every last opened port presents you with somewhat of a resource concern, not to mention security problem (Should also be addressed)-
 

10 More Discussions You Might Find Interesting

1. IP Networking

TCP Ports

We are being setup with a client over their VPN to support them remotely. We are unable to access their VPN through our server, they said to look and make sure that the TCP ports are enabled for their security setup (ports are in the 4000 range). How do you look for this and how do you enable a... (3 Replies)
Discussion started by: blacksheep
3 Replies

2. UNIX for Dummies Questions & Answers

TCP Listening Ports

Hello all, Can someone instruct me on how to change the listening port for ftp ( or any tcp service) from 21 to another port number? Thanks in advance.. -AJ (3 Replies)
Discussion started by: jacobsa
3 Replies

3. UNIX for Dummies Questions & Answers

TCP/UDP Ports

Just starting to work with unix, wondering if there is any good on-line documentation explaining TCP/UDP ports, how to use them, etc... Thanks.... (1 Reply)
Discussion started by: eugene_mayo
1 Replies

4. IP Networking

TCP/UDP Ports

Just wondering if anyone knows of any good on-line documentation on TCP/UDP Ports. Basically i want to know how to check if they are in use, learn how to close them, etc... Thanks... (5 Replies)
Discussion started by: eugene_mayo
5 Replies

5. Windows & DOS: Issues & Discussions

TCP ports and file sharing

In using a music file sharing program (WinMx), I am told that I cannot make a primary connection (fastest downloads) because I do not have a TCP and UDP port. I am running Windows Me.What do I do? Thanks. (6 Replies)
Discussion started by: dookster5
6 Replies

6. UNIX for Advanced & Expert Users

TCP slow access though certain ports

hi, I'm currently running with an issue whereby we are experiencing very poor access speeds to our Informix database. Connections or requests to the DB are taking in excess of 2/3/4 minutes during peek periods during the day. This has only just started to happen but so far we have been unable to... (0 Replies)
Discussion started by: fastyan
0 Replies

7. UNIX for Dummies Questions & Answers

Opening TCP ports

I'm not sure if this is the right place for this post, but I'd be grateful if somebody could please help me. I'm trying to open ports 999, 1982 and 1983 but am not having much luck. I used iptables -A INPUT -i eth0 -p tcp --sport 999 -m state --state NEW,ESTABLISHED -j ACCEPT iptables -A INPUT -i... (2 Replies)
Discussion started by: thehaapyappy
2 Replies

8. IP Networking

problem opening TCP ports

Please can somebody help me. I'm trying to open ports 999, 1982 and 1983 but am not having much luck. I used iptables -A INPUT -i eth0 -p tcp --sport 999 -m state --state NEW,ESTABLISHED -j ACCEPT iptables -A INPUT -i eth0 -p tcp --sport 1982 -m state --state NEW,ESTABLISHED -j ACCEPT iptables... (5 Replies)
Discussion started by: thehaapyappy
5 Replies

9. Solaris

List TCP ports with process

Hello, One of our developers is asking for a command/script in Solaris similar to "netstat -anp" in Linux. He gave this output as an example: root@xxx:~# netstat -anp | grep LISTEN tcp 0 0 0.0.0.0:7937 0.0.0.0:* LISTEN 16082/nsrexecd tcp 0 ... (7 Replies)
Discussion started by: vimes
7 Replies

10. Red Hat

How to kill a TCP connection which has status TIME_WAIT & no PID

Hi, I want to kill TCP connections which have status as TIME_WAIT & no PID (as per the output of the "netstat - p" command). Is there any command/utility available to kill connections to a specific port or IP address. The problem is that these connections don't have process ID (see... (4 Replies)
Discussion started by: Davinder31may
4 Replies
vrport(1M)																vrport(1M)

NAME
vrport - Veritas Volume Replicator port management utility SYNOPSIS
vrport [-a | -r] data [port | portlow-porthigh [,port...]] vrport heartbeat [port] vrport vradmind [port] vrport vxrsyncd [port] DESCRIPTION
The vrport utility manages the various UDP and TCP ports used by Veritas Volume Replicator (VVR). VVR uses the UDP and TCP transport protocols to communicate between the Primary and Secondary. VVR exchanges three types of message between the Primary and Secondary: heartbeat, data and administrative control. The heartbeat messages are transmitted using the UDP protocol on the IANA approved 4145 UDP Port number. VVR can use either the UDP trans- port protocol or the TCP transport protocol to exchange data messages. VVR uses UDP Anonymous ports for data replication between Primary and the Secondary if the network protocol is UDP. VVR uses IANA approved 4145 TCP port number for TCP listener port on the Secondary and TCP Anonymous ports on the Primary for data replication if the network protocol is TCP. VVR uses IANA approved 8199 TCP port for communication between the vradmind daemons on the Primary and the Secondary. vradmind server pro- vides administration of VVR objects in a distributed environment. VVR uses 8989 TCP port number for communication between the vxrsyncd dae- mons on the Primary and the Secondary. Use vrport to display, change or set the port numbers used by VVR. You may have to change the port numbers to resolve a port number con- flict with other applications, to configure VVR to work in a firewall environment when using UDP network protocol by restricting the number of ports to replicate data between the Primary and the Secondary. The action performed by vrport depends on the specified keyword operand(s). When invoked with no arguments, vrport displays the port number(s) used for heartbeat, data, vradmind and vxrsyncd communication between the Primary and Secondary on the standard output. KEYWORDS
data [port | portlow-porthigh [,port...]] Without any arguments, the vrport data command displays the port number(s) used by VVR for data replication between the Primary and the Secondary. This is applicable only if you have chosen UDP for network protocol. With the port number(s) or range specified, restricts VVR to use the ports or list of ports specified for data replication. If the -a flag is specified, the vrport data command appends the given port numbers(s) or range to the existing port number(s) or range to be used for data replication. If the -r flag is specified, the vrport data command removes the given port number(s) or range from the existing port number(s) for data replication. You need to execute /usr/sbin/vxnetd, and pause and resume all RLINKs for VVR to use the new port information. heartbeat [port] Without the port argument, displays the UDP port number used to exchange heartbeat messages. With the port argument specified, sets the UDP port number to exchange heartbeat messages. Use the vradmin changeip command to update the RLINKs with the new port information. To have VVR use the new port number, enter the command /usr/sbin/vxnetd stop followed by /usr/sbin/vxnetd. vradmind [port] Without the port argument, displays the TCP port number used by the vradmind daemons for communication between the Primary and the Secondary. With the port argument specified, sets the TCP port number to be used by the vradmind daemons. The new port is used when the vradmind process is restarted. vxrsyncd [port] Without the port argument, displays the port the TCP port number used by vxrsyncd daemons for communication between the Primary and the Secondary hosts. With the port argument specified, command sets the TCP port number to be used by the vxrsyncd daemons. The new port is used when the vxrsyncd process is restarted. EXAMPLES
See the Veritas Volume Replicator Configuration Notes for examples. EXIT CODES
The vrport utility exits with a non-zero status if the attempted operation fails. A non-zero exit code is not a complete indicator of the problems encountered but denotes the first condition that prevented further execution of the utility. SEE ALSO
vradmin(1M),vxrlink(1M) Veritas Volume Replicator Administrator's Guide Veritas Volume Replicator Configuration Notes VxVM 5.0.31.1 24 Mar 2008 vrport(1M)
All times are GMT -4. The time now is 06:27 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy