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
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
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
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
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
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
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
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
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
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
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
LEARN ABOUT HPUX
nfs3_max_transfer_size_cots
nfs3_max_transfer_size_cots(5) File Formats Manual nfs3_max_transfer_size_cots(5)
NAME
nfs3_max_transfer_size_cots - controls the data portion size of a NFS version 3 read, write, readdir, or readdirplus request over TCP
VALUES
Failsafe
Default
Allowed values
Recommended values
A warning will be issued at runtime if the tunable is set to a value greater than 1048576 since this is outside the tested limits. This is
not a serious warning but just an information message for the administrator.
DESCRIPTION
controls the maximum size of the data portion of a NFS version 3 read, write, readdir, or readdirplus request over TCP. This parameter con-
trols both the maximum size of a request that the server returns as well as the maximum size of a request that the client generates.
Who Is Expected to Change This Tunable?
Distributed file system administrators should examine this value if they want to decrease or increase the default size of a NFS version 3
packet over TCP.
Restrictions on Changing
The tunable is dynamic; however, the transfer size for a file system is set when the file system is mounted. To affect a particular file
system, unmount and mount the file system after changing this parameter.
The actual NFS version 3 transfer size over TCP is controlled by these tunable parameters: and The actual transfer size will depend on the
tunable with the smallest value. For NFS TCP traffic increase and to the same value to increase the transfer size. To decrease the transfer
size, just changing is sufficient.
When Should the Value of This Tunable Be Raised?
An increase in the transfer size will result in fewer requests to the NFS server at the expense of system resources on both the NFS client
and NFS server.
What Are the Side Effects of Raising the Value?
Setting the limit large causes more system resources to be consumed by both the NFS client and NFS server.
When Should the Value of This Tunable Be Lowered?
In the event of NFS communication failures, the value should be changed back to the default value.
What Are the Side Effects of Lowering the Value?
An increase in NFS version 3 network traffic over TCP caused by an increase in the number of I/O requests.
WARNINGS
All HP-UX kernel tunable parameters are release specific. This parameter may be removed or have its meaning changed in future releases of
HP-UX.
Installation of optional kernel software, from HP or other vendors, may cause changes to tunable parameter values. After installation,
some tunable parameters may no longer be at the default or recommended values. For information about the effects of installation on tun-
able values, consult the documentation for the kernel software being installed. For information about optional kernel software that was
factory installed on your system, see at
AUTHOR
was developed by Sun Microsystems, Inc.
SEE ALSO
kctune(1M), sam(1M), gettune(2), settune(2), nfs3_bsize(5), nfs3_max_transfer_size(5), values(5).
Tunable Kernel Parameters nfs3_max_transfer_size_cots(5)