[Ilugc] SO_REUSEADDR in conjunction with INADDR_ANY issue
- From: girishvenkatachalam@xxxxxxxxx (Girish Venkatachalam)
- Date: Sun, 31 Jul 2011 07:11:02 +0530
?I believe SO_REUSEPORT is not portable , its more used in BSD Unixes and i
believe that its functionality is covered by SO_REUSEADDR under linux as per
manual
Nothing like that. These differences are normal between UNICes.
I have tried? couple of more options for reusing the port by setting the
kernel parameters (TCP_TW_RECYCLE and TCP_TW_REUSE)? , not much luck here
also .
What? Why do you do things not necessary?
I have never heard of these. Look at
# sysctl -a
and grep for tcp or net.inet.tcp or something.
I? did do good amount of reserach online before posting ,? but could not get
much info to resolve
http://hea-www.harvard.edu/~fine/Tech/addrinuse.html
http://lkml.indiana.edu/hypermail/linux/kernel/9902.1/0922.html
http://stackoverflow.com/questions/3127990/linux-sockets-server-exits-before-client
https://www.ibm.com/developerworks/library/l-sockpit/
Narendra,
Your problem is that you are not doing the correct design.
No amount of digging around will solve that.
Certainly SO_REUSEADDR is unnecessary.
If you wait for few seconds, the port gets released by the kernel automatically.
You have connections in ESTABLISHED state and how do you expect to bind to it
again?
You have fundamental flaws in your understanding of TCP/IP.
Fix that. And stop bothering about these advanced concepts not at all relevant
to your problem.
Keep things simple. That is the way all great programmers do
great things.
-Girish
--
G3 Tech
Networking appliance company
web:
http://g3tech.in ?mail: girish at g3tech.in
Other related posts: