From: Josh Boyer <jwboyer@redhat.com>
To: netdev@vger.kernel.org
Subject: loopback IP alias breaks tftp?
Date: Wed, 5 Oct 2011 16:27:23 -0400 [thread overview]
Message-ID: <20111005202723.GE2479@zod.bos.redhat.com> (raw)
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.)
[1] https://bugzilla.redhat.com/show_bug.cgi?id=739534
josh
next reply other threads:[~2011-10-05 20:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-05 20:27 Josh Boyer [this message]
2011-10-05 21:18 ` loopback IP alias breaks tftp? Julian Anastasov
2011-10-06 13:23 ` Josh Boyer
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=20111005202723.GE2479@zod.bos.redhat.com \
--to=jwboyer@redhat.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).