lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 05 Dec 2008 16:11:17 +0900 (JST)
From:	YOSHIFUJI Hideaki / 吉藤英明 
	<yoshfuji@...ux-ipv6.org>
To:	pekkas@...core.fi
Cc:	netdev@...r.kernel.org, yoshfuji@...ux-ipv6.org
Subject: Re: IPv6 multicast bind(), esp. v4-mapped addresses

Hello.

In article <alpine.LRH.2.00.0812050820380.28482@...core.fi> (at Fri, 5 Dec 2008 08:42:37 +0200 (EET)), Pekka Savola <pekkas@...core.fi> says:

> Two questions:
> 
>   1) should this be supported?  I think we're talking about a change in
>      net/ipv6/af_inet6.c, replacing something like (not tested, adapted
>      from net/ipv4/af_inet.c):
> 
> 273         if (addr_type == IPV6_ADDR_MAPPED) {
> 274                 v4addr = addr->sin6_addr.s6_addr32[3];
> 275                 if (inet_addr_type(net, v4addr) != RTN_LOCAL) {
> 276                         err = -EADDRNOTAVAIL;
> 277                         goto out;
> 278                 }
> 279         } else {
> 
> with:
> 
>           if (addr_type == IPV6_ADDR_MAPPED) {
>                   v4addr = addr->sin6_addr.s6_addr32[3];
>  		 if (inet_addr_type(net, v4addr) == RTN_MULTICAST ||
>  		     inet_addr_type(net, v4addr) == RTN_BROADCAST) {
>  			inet->saddr = 0; /* Use device */
>                   } else {
>  	                 if (inet_addr_type(net, v4addr) != RTN_LOCAL) {
>  	                         err = -EADDRNOTAVAIL;
>  	                         goto out;
>  	                 }
>  		}
>           } else {

I think similar issue(s) have been pointed out several times.
IPv4-mapped addresses are not portable, unfortunately, anyway, and
people should use native interface, especially for multicasts.

BTW, do you know what kind of socket option do they use for setting/getting
ttl etc?

If we fully support "IPv4-Mapped" function, we should transparently
configure ipv4-multicast parameters etc. as well.


>   2) it appears that ip_nonlocal_bind sysctl only supports ipv4.
>      Similar option or applying the same for v6 may be useful,
>      especially if 1) is not changed, such a toggle might be useful
>      with v6 as well.

I don't think this could not be an answer.

--yoshfuji
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ