netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Edward Wang <Yujiang.Wang@Sun.COM>
To: netdev@vger.kernel.org
Subject: 2.6.9 packets not received on link-local address
Date: Tue, 05 Jun 2007 15:56:26 +0800	[thread overview]
Message-ID: <4665172A.9010400@sun.com> (raw)

One 2.6.9 machine sends to its own link-local address some packets. But 
it simply can't receive those packets, for both TCP and UDP. If will 
succeeded if:

   - sending to a global address instead of a link-local one;
   - or, machine A sends packets, machine B will receive them;
   - or, 2.6.15 *do* receive TCP packets it sends to its link-local 
address. But UDP still fail.


It seems to be a known issue since 2.6.15 shows some improvement. But I 
can't find anything in mailing list archive. Any pointer?

And, there's a dummy route entry in 2.6.* route table, which use 
loopback_dev as reference device to link-local address. It seems really 
odd. Is it related to the problem I just asked? And why Linux IPv6 stack 
did that?

Thanks in advance.

-Ed

                 reply	other threads:[~2007-06-05  8:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4665172A.9010400@sun.com \
    --to=yujiang.wang@sun.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).