netdev
[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

Re: SO_REUSEADDR behavior different from BSD

from [Fernando Gont] [Permanent Link][Original]
To: YOSHIFUJI Hideaki / 吉藤英明 <yoshfuji@xxxxxxxxxx>, mtk-lists@xxxxxxx
Subject: Re: SO_REUSEADDR behavior different from BSD
From: Fernando Gont <fernando@xxxxxxxxxxx>
Date: Sat, 07 Aug 2004 23:25:13 -0300
Cc: ahu@xxxxxxx, netdev@xxxxxxxxxxx
In-reply-to: <20040805.113437.91348248.yoshfuji@wide.ad.jp>
References: <19686.1091723777@www48.gmx.net> <20040805141444.GA2292@outpost.ds9a.nl> <19686.1091723777@www48.gmx.net>
Sender: netdev-bounce@xxxxxxxxxxx 
At 11:34 05/08/2004 -0700, YOSHIFUJI Hideaki wrote:

> Now, on Linux, at this point, the second instance of the
> server fails with EADDRINUSE, even though it did use
> SO_REUSEADDR.  On FreeBSD 5.1, the second server instance
> does successfully bind.

This behavior is intended.
First socket is REQUIRED to set SO_REUSEADDR
I hate BSD's behavior because it is asynmetry.
(Both sockets are required to agree on "REUSEADDR.")


Not sure what you mean by "asymetry".


--
Fernando Gont
e-mail: fernando@xxxxxxxxxxx || fgont@xxxxxxx



[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  Wireless Extensions WE-18 questions, Pedro Ramalhais
Next by Date:  Re: [PATCH 2.6] vlan ioctl propagation (rev.2), Glen Turner
Previous by Thread:  Re: SO_REUSEADDR behavior different from BSD, YOSHIFUJI Hideaki / 吉藤英明
Next by Thread:  Re: SO_REUSEADDR behavior different from BSD, Michael T Kerrisk
Indexes:  [Date] [Thread] [Top] [All Lists]