| To: | cat@xxxxxxxxxx |
|---|---|
| Subject: | Re: ipv6 and ipv4 interaction weirdness |
| From: | YOSHIFUJI Hideaki / 吉藤英明 <yoshfuji@xxxxxxxxxxxxxx> |
| Date: | Fri, 11 Mar 2005 08:58:15 -0600 (CST) |
| Cc: | linux-kernel@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx, pekkas@xxxxxxxxxx, yoshfuji@xxxxxxxxxxxxxx |
| In-reply-to: | <20050311121655.GE14146@xxxxxxxxxx> |
| Organization: | USAGI Project |
| References: | <20050311121655.GE14146@xxxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
In article <20050311121655.GE14146@xxxxxxxxxx> (at Fri, 11 Mar 2005 23:16:55 +1100), CaT <cat@xxxxxxxxxx> 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 |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: 2.6.10 - "netdev=" kernel boot commands and the Intel e1000 nic, P |
|---|---|
| Next by Date: | Re: ipv6 and ipv4 interaction weirdness, CaT |
| Previous by Thread: | ipv6 and ipv4 interaction weirdness, CaT |
| Next by Thread: | Re: ipv6 and ipv4 interaction weirdness, CaT |
| Indexes: | [Date] [Thread] [Top] [All Lists] |