Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261330AbVDZGKT (ORCPT ); Tue, 26 Apr 2005 02:10:19 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261341AbVDZGKT (ORCPT ); Tue, 26 Apr 2005 02:10:19 -0400 Received: from ipx10069.ipxserver.de ([80.190.240.67]:64983 "EHLO codeblau.de") by vger.kernel.org with ESMTP id S261330AbVDZGKM (ORCPT ); Tue, 26 Apr 2005 02:10:12 -0400 Date: Tue, 26 Apr 2005 08:10:11 +0200 From: Felix von Leitner To: Pekka Savola Cc: "YOSHIFUJI Hideaki / ?$B5HF#1QL@" , linux-kernel@vger.kernel.org, netdev@oss.sgi.com Subject: Re: IPv6 has trouble assigning an interface Message-ID: <20050426061011.GA8527@codeblau.de> References: <20050311202122.GA13205@fefe.de> <20050311173308.7a076e8f.akpm@osdl.org> <20050324.205902.119922975.yoshfuji@linux-ipv6.org> <20050425195736.GB3123@codeblau.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.9i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1418 Lines: 31 Thus spake Pekka Savola (pekkas@netcore.fi): > >Here is an strace of some piece of code of mine: > > > >socket(PF_INET6, SOCK_DGRAM, IPPROTO_IP) = 3 > >setsockopt(3, SOL_SOCKET, SO_REUSEADDR, [12884901889], 4) = 0 > >bind(3, {sa_family=AF_INET6, sin6_port=htons(8002), inet_pton(AF_INET6, > >"::", &sin6_addr), sin6_flowinfo=0, sin6_scope_id=0}, 28) = 0 > >setsockopt(3, SOL_IPV6, IPV6_MULTICAST_LOOP, "\1", 1) = 0 > >[...] > >sendto(3, "ncp-lowfat-1.2.2", 16, 0, {sa_family=AF_INET6, > >sin6_port=htons(8002), inet_pton(AF_INET6, "ff02::6e63:7030", &sin6_addr), > >sin6_flowinfo=0, sin6_scope_id=0}, 28) = -1 EADDRNOTAVAIL (Cannot assign > >requested address) > > > >ff02 is a link-local multicast address. I've bound to ::. How can this > >fail? link-local should always work, even if no routes are set and no > >router has been found. > Umm.. link-local unicast and multicast both require that you specify > the interface, because otherwise it's ambiguous -- how could the > kernel know which interface should be used to send the packet? OK for unicast. But multicast? I expected link-local multicast to send on _all_ interfaces if I don't specify one. Felix - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/