From: "David S. Miller" <davem@redhat.com>
To: Casey Carter <Casey@Carter.net>
Cc: netdev@oss.sgi.com
Subject: Re: [PATCH] Make SO_BINDTODEVICE bind very tightly
Date: Wed, 8 Oct 2003 04:49:48 -0700 [thread overview]
Message-ID: <20031008044948.4e3bdf3c.davem@redhat.com> (raw)
In-Reply-To: <3F833B39.4020606@Carter.net>
On Tue, 07 Oct 2003 17:16:25 -0500
Casey Carter <Casey@Carter.net> wrote:
> In the presence of both sockets that are and sockets that are not bound
> to a specific interface, those bound to the interface should always be
> favored for packet delivery over those not so bound.
No, the fix made in the original posting of this thread is the
correct one. One may not have some sockets with SO_BINDTODEVICE
and some with not bound at the same time to the same identity.
Therefore the fix should be a bind() time.
prev parent reply other threads:[~2003-10-08 11:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-07 22:16 [PATCH] Make SO_BINDTODEVICE bind very tightly Casey Carter
2003-10-08 11:49 ` David S. Miller [this message]
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=20031008044948.4e3bdf3c.davem@redhat.com \
--to=davem@redhat.com \
--cc=Casey@Carter.net \
--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).