From: Kevin Dwyer <kevin@pheared.net>
To: Casey Carter <Casey@Carter.net>
Cc: netdev@oss.sgi.com, linux-ha@lists.linux-ha.org
Subject: Re: Strange UDP binding behavior (SO_BINDTODEVICE)
Date: Mon, 6 Oct 2003 21:06:00 -0400 [thread overview]
Message-ID: <20031006210600.37da62c9.kevin@pheared.net> (raw)
In-Reply-To: <3F81F1CD.8050803@Carter.net>
[-- Attachment #1: Type: text/plain, Size: 879 bytes --]
On Mon, 06 Oct 2003 17:50:53 -0500
Casey Carter <Casey@Carter.net> wrote:
> This is not a bug, it's a feature! It is possible to use multiple
> sockets with the same port number bound to different interfaces (where
> "no interface" is one possible choice). The UDP packet delivery code
> favors the socket that is bound to the interface through which packets
> are received. So, if I am only interested in packets for port 6666 on
> eth1, then I am prioritized ahead of the socket bound to "no
> interface" port 6666.
Well, I would buy that as reasonable, acceptable behavior, but I think
the reverse is true.
We are binding specifically to say, eth0 on port 694. Someone comes
along and binds to "no interface" on port 694 and trumps our socket.
Isn't that the opposite of what you describe?
--
- kpd
"If at first you don't succeed, redefine success." - Anonymous
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-10-07 1:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-05 17:01 Strange UDP binding behavior (SO_BINDTODEVICE) Kevin Dwyer
2003-10-06 22:50 ` Casey Carter
2003-10-07 1:06 ` Kevin Dwyer [this message]
2003-10-07 20:51 ` Casey Carter
2003-10-07 21:08 ` Kevin Dwyer
2003-10-07 21:49 ` Casey Carter
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=20031006210600.37da62c9.kevin@pheared.net \
--to=kevin@pheared.net \
--cc=Casey@Carter.net \
--cc=linux-ha@lists.linux-ha.org \
--cc=netdev@oss.sgi.com \
/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;
as well as URLs for NNTP newsgroup(s).