From: Josh Boyer <jwboyer@redhat.com>
To: Julian Anastasov <ja@ssi.bg>, Joel Sing <jsing@google.com>
Cc: netdev@vger.kernel.org
Subject: Re: loopback IP alias breaks tftp?
Date: Thu, 6 Oct 2011 09:23:53 -0400 [thread overview]
Message-ID: <20111006132353.GF2479@zod.bos.redhat.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1110060009020.1959@ja.ssi.bg>
On Thu, Oct 06, 2011 at 12:18:44AM +0300, Julian Anastasov wrote:
>
> Hello,
>
> On Wed, 5 Oct 2011, Josh Boyer wrote:
>
> > Hi All,
> >
> > We've had a report [1] of a change in behavior when trying to use an IP
> > alias to tftp from a loopback device. Apparently the steps outlined in
> > the bug worked in 2.6.35, and broke somewhere before 2.6.38.6.
> >
> > I can confirm the steps fail on a 3.0 based kernel and I'm trying to do
> > a git bisect to find the commit involved, but I thought I would send
> > this along to see if anyone might have an idea. (Also, I'm not really
> > sure how valid of a usecase this was to begin with.)
>
> What about commit 9fc3bbb4a752f108cf096d96640f3b548bbbce6c ?
>
> ipv4/route.c: respect prefsrc for local routes
>
> http://marc.info/?t=129412232500001&r=1&w=2
>
> > [1] https://bugzilla.redhat.com/show_bug.cgi?id=739534
Yep. That is exactly what my git bisect said too.
So now we have a change in behavior since that commit for the usecase
described in the bug above, but I'm unsure if that usecase was ever
really valid or if the commit had unintentional side effects.
Joel (or anyone else) can you take a look and comment?
josh
next prev parent reply other threads:[~2011-10-06 13:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-05 20:27 loopback IP alias breaks tftp? Josh Boyer
2011-10-05 21:18 ` Julian Anastasov
2011-10-06 13:23 ` Josh Boyer [this message]
2011-10-07 7:02 ` Joel Sing
2011-10-07 7:29 ` Eric Dumazet
2011-10-07 11:40 ` Josh Boyer
2011-10-07 12:04 ` Eric Dumazet
2011-10-07 12:23 ` Eric Dumazet
2011-10-10 15:10 ` Josh Boyer
2011-10-10 15:15 ` Olaf van der Spek
2011-10-10 15:22 ` Eric Dumazet
2011-10-10 15:25 ` Olaf van der Spek
2011-10-11 7:28 ` Francis SOUYRI
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=20111006132353.GF2479@zod.bos.redhat.com \
--to=jwboyer@redhat.com \
--cc=ja@ssi.bg \
--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).