Sponsored Content
Top Forums Programming Problem and question with TCP Post 302934055 by Corona688 on Wednesday 4th of February 2015 10:51:20 AM
Old 02-04-2015
TCP doesn't truncate, it fragments. Messages will arrive in multiple pieces. The sending and receiving programs don't have control of how many or what size.

If you require packets to arrive in specific sizes, use UDP. Packets larger than the MTU simply won't work at all.
 

10 More Discussions You Might Find Interesting

1. IP Networking

tcp problem with port

I am trying to connect via DBACCESS and Informix server to a server on a different computer. When I execute the connect command from dbaccess I get the following message, Exec format error cannot bind a name to the port. As far as I know the port is not being used by another client. How... (1 Reply)
Discussion started by: lopez
1 Replies

2. IP Networking

WinXP and TCP/IP Problem

Hi Eveyone, I have A small problems maybe some one can help me. I'm running a small network at home with internet access. Two PC's have Win XP and one has Win98se. I have them all hook up on a SMC router. ALL windows firewall are off and and harddrive sharing is on. I am using DCHP network... (3 Replies)
Discussion started by: Peterh
3 Replies

3. Solaris

TCP Problem

I am running a Java Client on Solaris 9 which communicates with the Server using TCP/IP. The client transmits a FIN packet to server. The server sends a ACK, FIN enters LAST_ACK state and then waits for ACK from client. The client did not respond back leaving the server in LAST_ACK itself. Also... (0 Replies)
Discussion started by: diarun
0 Replies

4. Programming

TCP status question

There is a server and a client,when client send a message to server,server can send a reply to client. The status of server and client is ESTABLISHED.Then I halt the client,I find the server status is CLOSE_WAIT and the client status is FIN_WAIT_2. Many minutes passed,I find the the server status... (1 Reply)
Discussion started by: konvalo
1 Replies

5. Programming

C & TCP question: AF_INET vs AF_UNIX

Greetings! I am attempting to write a *basic* network client in C. I have manage to create a socket but I have doubts as far as using AF_INET vs AF_UNIX. At the present time, my client runs with AF_INET. Is AF_UNIX faster across hosts using the same OS flavor (Red Hat)? What is the difference... (1 Reply)
Discussion started by: Alan Christen
1 Replies

6. Red Hat

tcp/ip problem

how the data from disk is loaded into memory and then it transfered to tcp/ip packet. how i can find how many pages are loaded into memory by that process what is the rate of context switch for that process. (5 Replies)
Discussion started by: amar20
5 Replies

7. Shell Programming and Scripting

tcp/ip and memory problem

how the data from disk is loaded into memory and then it supplied to tcp/ip packet. how i can trace the no of pages loaded in memory by that process and rate of context switch for that process. (1 Reply)
Discussion started by: amar20
1 Replies

8. Programming

Problem with tcp server

Hello @ all, I hope you can give me some advice :b: I will be following code for a tcp server and doStuff () function, the clients treated. From some point, I have several identical clients (zombies, I think), the same records in the database write. Has anyone an explanation? What can I... (1 Reply)
Discussion started by: yumos
1 Replies

9. IP Networking

Wireshark TCP and HTTP question.

Hello all. This is my first post and thank you for your forum. Here is my question. I have a simple setup at home and I was capturing some data with wireshark. Data between a workstation and the web server, requesting a page. Simple enough. Now when I open wireshark, I apply the TCP... (4 Replies)
Discussion started by: squaresphere
4 Replies

10. UNIX for Advanced & Expert Users

Bizzare TCP/IP problem

Hi all. I have a really really weird problem that I've been working on for days. The problem manifested as users cannot connect to our web servers via SSH when they're using our wireless network. Here's where it gets weird: - Clients from anywhere other than the wireless subnet can... (4 Replies)
Discussion started by: pileofrogs
4 Replies
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)
All times are GMT -4. The time now is 04:22 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy