From: David Miller <davem@davemloft.net>
To: bofh1234567@yahoo.com
Cc: alan@lxorguk.ukuu.org.uk, jengelh@linux01.gwdg.de,
linux-kernel@vger.kernel.org
Subject: Re: SO_REUSEPORT and multicasting
Date: Wed, 14 Jun 2006 15:14:18 -0700 (PDT) [thread overview]
Message-ID: <20060614.151418.32173686.davem@davemloft.net> (raw)
In-Reply-To: <20060614174825.94383.qmail@web53612.mail.yahoo.com>
Instead of degenerating this mailing list into a BSD socket
programming class, you may find this informative:
http://www.unixguide.net/network/socketfaq/4.11.shtml
and it's covered extensively in W. Richard Steven's book, TCP/IP
Illustrated, Volume 2. It is considered the bible on BSD socket
programming.
Particularly telling is the final paragraph from that web page which
reads:
Basically SO_REUSEPORT is a BSD'ism that arose when
multicast was added, evne though it was not used in the
original Steve Deering code. I believe some BSD-derived
systems may also include it. SO_REUSEPORT lets you bind
the same address *and* port, but only if all the binders
have specified it. But when binding to multicast address
(its main use), SO_REUSEADDR is considered identical to
SO_REUSEPORT (p. 731, "TCP/IP Illustrated, Volume 2").
So for portability of multicast applications, I always
use SO_REUSEADDR.
I STRONGLY suggest you go read that reference to page 731 in
the Steven book.
next prev parent reply other threads:[~2006-06-14 22:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-13 19:24 Jason
2006-06-13 20:20 ` Jan Engelhardt
2006-06-14 14:26 ` Jason
2006-06-14 14:51 ` Alan Cox
2006-06-14 17:48 ` Jason
2006-06-14 22:14 ` David Miller [this message]
2006-06-14 22:57 ` Jason
2006-06-14 23:04 ` David Miller
2006-06-15 13:32 ` Jason
2006-06-14 14:40 ` James Courtier-Dutton
2006-06-14 18:04 ` Jason
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060614.151418.32173686.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bofh1234567@yahoo.com \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®