Subject: Re: IPv4-mapped addresses in Multicast sockets?
To: Jonathan A. Kollasch <jakllsch@kollasch.net>
From: Sourath Roy <sourath@gmail.com>
List: current-users
Date: 02/02/2007 18:44:38
------=_Part_5896_11442309.1170422078880
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

By default IPv4-mapped address support is turned off for IPv6 sockets. But
NetBSD allows usage ot that by setting kernel parameter
net.inet6.ip6.v6only=0. So IPv4-mapped addresses are still possible with
NetBSD.

But looking at the implementation it appears that the restriction strictly
applies to Multicast addresses. No IPv4-mapped addresses are allowed there,
no matter what net.inet6.ip6.v6only reads like.

-- Sourath

On 1/27/07, Jonathan A. Kollasch <jakllsch@kollasch.net> wrote:
>
> On Thu, Jan 25, 2007 at 02:26:02PM +0530, Sourath Roy wrote:
> > Hello all,
> > I have a question related to Multicast and IPv4 mapped addresses on
> AF_INET6
> > sockets. Can we use IPv4 mapped multicast addresses alongwith to
> > IPV6_JOIN_GROUP? In general does INET6 multicasting allow sockets of
> > AF_INET6 communicate over IPv4 multicast addresses?
> > Currently when I look into the code, it doesn't seem like considering
> the
> > IPv4 compatible/mapped addresses at all.
>
> That would agree with  http://en.wikipedia.org/wiki/IPv4_mapped_address .
>
> It looks like the only portable thing to do is not rely on this feature.
> Additionally, Multicast is the last thing I would expect to work using a
> translation layer such as this.
>
>         Jonathan Kollasch
>
>
>

------=_Part_5896_11442309.1170422078880
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

By default IPv4-mapped address support is turned off for IPv6 sockets.
But NetBSD allows usage ot that by setting kernel parameter
net.inet6.ip6.v6only=0. So IPv4-mapped addresses are still possible
with NetBSD.<br>
<br>
But looking at the implementation it appears that the restriction
strictly applies to Multicast addresses. No IPv4-mapped addresses are
allowed there, no matter what net.inet6.ip6.v6only reads like.<br>
<br>
-- Sourath<br><br><div><span class="gmail_quote">On 1/27/07, <b class="gmail_sendername">Jonathan A. Kollasch</b> &lt;<a href="mailto:jakllsch@kollasch.net">jakllsch@kollasch.net</a>&gt; wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Thu, Jan 25, 2007 at 02:26:02PM +0530, Sourath Roy wrote:<br>&gt; Hello all,<br>&gt; I have a question related to Multicast and IPv4 mapped addresses on AF_INET6<br>&gt; sockets. Can we use IPv4 mapped multicast addresses alongwith to
<br>&gt; IPV6_JOIN_GROUP? In general does INET6 multicasting allow sockets of<br>&gt; AF_INET6 communicate over IPv4 multicast addresses?<br>&gt; Currently when I look into the code, it doesn&#39;t seem like considering the
<br>&gt; IPv4 compatible/mapped addresses at all.<br><br>That would agree with&nbsp;&nbsp;<a href="http://en.wikipedia.org/wiki/IPv4_mapped_address">http://en.wikipedia.org/wiki/IPv4_mapped_address</a> .<br><br>It looks like the only portable thing to do is not rely on this feature.
<br>Additionally, Multicast is the last thing I would expect to work using a<br>translation layer such as this.<br><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Jonathan Kollasch<br><br><br></blockquote></div><br>

------=_Part_5896_11442309.1170422078880--