From: "YOSHIFUJI Hideaki / 吉藤英明" <yoshfuji@linux-ipv6.org>
To: cat@zip.com.au
Cc: linux-kernel@vger.kernel.org, netdev@oss.sgi.com,
pekkas@netcore.fi, yoshfuji@linux-ipv6.org
Subject: Re: ipv6 and ipv4 interaction weirdness
Date: Fri, 11 Mar 2005 08:58:15 -0600 (CST) [thread overview]
Message-ID: <20050311.085815.100748583.yoshfuji@linux-ipv6.org> (raw)
In-Reply-To: <20050311121655.GE14146@zip.com.au>
In article <20050311121655.GE14146@zip.com.au> (at Fri, 11 Mar 2005 23:16:55 +1100), CaT <cat@zip.com.au> says:
> If it bound to :: port 22 then 0.0.0.0:22 would fail.
>
> On the other hand if I got it to bind to each address individually then
> both ipv4 (2 addresses) and ipv6 (1 address) binds would succeed.
>
> Maybe I'm just looking at it wrong but shouldn't ipv4 and ipv6 interfere
> with each other?
It is 100% intended, even it is not similar to BSD variants do.
IPv4 and IPv6 share address/port space.
:: and 0.0.0.0 is special "any" address, thus they confict.
::ffff:a.b.c.d and a.b.c.d also conflict.
--yoshfuji
next prev parent reply other threads:[~2005-03-11 14:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-11 12:16 CaT
2005-03-11 14:21 ` Simon Kelley
2005-03-11 14:58 ` YOSHIFUJI Hideaki / 吉藤英明 [this message]
2005-03-11 15:11 ` CaT
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=20050311.085815.100748583.yoshfuji@linux-ipv6.org \
--to=yoshfuji@linux-ipv6.org \
--cc=cat@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=pekkas@netcore.fi \
/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
all inboxes | Powered by JetHome®