From: Albert Pretorius <albertpretorius@yahoo.co.uk>
To: Shan Wei <shanwei@cn.fujitsu.com>
Cc: netdev@vger.kernel.org,
"yoshfuji@linux-ipv6.org >> YOSHIFUJI Hideaki"
<yoshfuji@linux-ipv6.org>, David Miller <davem@davemloft.net>,
pekkas@netcore.fi, jmorris@namei.org
Subject: Re: IPV6 loopback bound socket succeeds connecting to remote host
Date: Thu, 2 Dec 2010 07:45:48 +0000 (GMT) [thread overview]
Message-ID: <616589.97517.qm@web29017.mail.ird.yahoo.com> (raw)
In-Reply-To: <4CF604DB.8000302@cn.fujitsu.com>
Hi
--- On Wed, 1/12/10, Shan Wei <shanwei@cn.fujitsu.com> wrote:
> I think it make nonsense to translate data between loopback
> device and other e.g. eth0 device in same machine.
I agree, RFC4291 makes it clear for IPV6 that no interface should accept traffic from loopback, I should not have tried to make it behave like IPV4.
I can not find an equivalent statement for IPV4 though, all I could find is this from RFC3330:
127.0.0.0/8 - This block is assigned for use as the Internet host
loopback address. A datagram sent by a higher level protocol to an
address anywhere within this block should loop back inside the host.
This is ordinarily implemented using only 127.0.0.1/32 for loopback,
but no addresses within this block should ever appear on any network
anywhere [RFC1700, page 5].
Do you perhaps know?
thank you,
Albert Pretorius
next prev parent reply other threads:[~2010-12-02 7:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-29 10:55 IPV6 loopback bound socket succeeds connecting to remote host Albert Pretorius
2010-12-01 8:18 ` Shan Wei
2010-12-02 7:45 ` Albert Pretorius [this message]
2010-12-02 8:41 ` Shan Wei
2010-12-16 20:18 ` David Miller
2010-12-20 6:31 ` Shan Wei
2010-12-20 6:43 ` David Miller
2010-12-22 7:06 ` Shan Wei
2010-12-29 16:53 ` Albert Pretorius
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=616589.97517.qm@web29017.mail.ird.yahoo.com \
--to=albertpretorius@yahoo.co.uk \
--cc=davem@davemloft.net \
--cc=jmorris@namei.org \
--cc=netdev@vger.kernel.org \
--cc=pekkas@netcore.fi \
--cc=shanwei@cn.fujitsu.com \
--cc=yoshfuji@linux-ipv6.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.