From: David Miller <davem@davemloft.net>
To: hpa@zytor.com
Cc: ebiederm@xmission.com, netdev@vger.kernel.org, jsing@google.com
Subject: Re: FYI: tftp-hpa breaks when used on secondary ip addresses
Date: Fri, 04 Mar 2011 20:58:17 -0800 (PST) [thread overview]
Message-ID: <20110304.205817.193701195.davem@davemloft.net> (raw)
In-Reply-To: <4D719254.8000903@zytor.com>
From: "H. Peter Anvin" <hpa@zytor.com>
Date: Fri, 04 Mar 2011 17:31:00 -0800
> If this is done for all local connections (as opposed to the ones that
> have been configured explicitly by the administrator to behave that
> way), that's a massive lossage. Not only does a large number of
> applications use this trick to determine if an address is local (e.g.
> allowing bypass) -- it is pretty much the only portable way to do it --
> but it would cause applications which expect to get a reply back from
> the same address they sent a request to to completely fall on their face.
Actually this is what SOL_IP, IP_PKTINFO, was created for. Even glibc
uses it.
prev parent reply other threads:[~2011-03-05 4:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-05 0:58 FYI: tftp-hpa breaks when used on secondary ip addresses Eric W. Biederman
2011-03-05 1:31 ` H. Peter Anvin
2011-03-05 4:58 ` David 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=20110304.205817.193701195.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=hpa@zytor.com \
--cc=jsing@google.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).