Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have a RHEL 4 server delivering long messages to several RHEL 4 clients. They work fine. I am trying a RHEL 5 client running the same client application as the RHEL 4 clients. The RHEL 5 client looses most messages. I have tried with two other clients running CentOS 5 with similar results. The server indicates write failure or blocked. The messages are typically 50 kilobytes. I have changed many parameters in sysctl.conf . Has anyone encountered similar problems? Any solutions?
Thanks,
Jim Cole
This is TCP over a socket connection.
The application is written specifically to receive and
pass on messages from a remote server. I have a reasonable
amount of networking experience and have configured sysctl.conf
for a variety of purposes. The internal logs report
the error code for every failed write. The error codes
at the server indicate write fail or write blocked.
Thanks for your response.
Jim Cole
It appears that we have solved the problem.
We have run since 10/25 00:35 EDT with no failures.
We added setsockopt SO_RCVBUF 8000000
setsockopt SO_SNDBUF 1000000
We added to sysctl.conf large maximums of 16777216
for net.ipv4.tcp_rmem net.ipv4.tcp_wmem
net.ipv4.tcp_mem
net.core.rmem_max net.core.wmem_max
Jim Cole
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.