From owner-freebsd-net@FreeBSD.ORG Fri Oct 17 23:26:13 2014 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5906D737 for ; Fri, 17 Oct 2014 23:26:13 +0000 (UTC) Received: from mail-vc0-x235.google.com (mail-vc0-x235.google.com [IPv6:2607:f8b0:400c:c03::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 16975D06 for ; Fri, 17 Oct 2014 23:26:13 +0000 (UTC) Received: by mail-vc0-f181.google.com with SMTP id le20so1343061vcb.12 for ; Fri, 17 Oct 2014 16:26:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=8Dihv2lgae3p6RqvrpktgTtuDTK0qACUz0cJM4wy5CU=; b=CvaAkPPjmnCKFxvJfl+Io/KIg+iFPQZoY+qRiRLpq4gZXfUg2wGosEap9KvBM6+k/8 GKSW0c/FJFsYuhTnYjd9I5onCj+SvBgmbaoHxrCN55SB7Ta8NMBLmDJeZV3M0QXAy3j4 dR5CzwtY+Rr9Tp98tbJ04APagC73l4iJghLDLDEnqGeu2G9gwYRUcC8SkgFSaOGvpENO 1Ls99yKSZnGjpmyp5xGOhpcqKsedehkgANjkbTZ362J7mgQYr/AmEUNh8fT/MFspTPhG ThoTLSmgIMRDN7rTmeu6Wm3njOf2eZgSu9uFHKi9GrrU8JsmdAxRuca922B9WJH7jcir cMyw== MIME-Version: 1.0 X-Received: by 10.221.46.4 with SMTP id um4mr9957382vcb.23.1413588372065; Fri, 17 Oct 2014 16:26:12 -0700 (PDT) Received: by 10.220.238.14 with HTTP; Fri, 17 Oct 2014 16:26:12 -0700 (PDT) In-Reply-To: References: Date: Fri, 17 Oct 2014 19:26:12 -0400 Message-ID: Subject: Re: IPv6 stacks responds to all node link local multicast NS From: Zaphod Beeblebrox To: prabhakar lakhera Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: FreeBSD Net X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Oct 2014 23:26:13 -0000 Urm ... question: is NS how, then, a client should be getting an IP over PPP? I have an l2tp server configured with mpd ... and I've noticed that mpd will allow me to turn on ipv6, but it won't assign addresses like ipv4. On Fri, Oct 17, 2014 at 2:28 PM, prabhakar lakhera < prabhakar.lakhera@gmail.com> wrote: > This probably is more of a compliance issue (or may be not as the NS > receipt section of RFC 4861 http://tools.ietf.org/html/rfc4861#page-62 > does > not talk about it). > > The neighbor solicitation message format says this: > > http://tools.ietf.org/html/rfc4861#page-22 > > > Destination Address > Either the solicited-node multicast address > corresponding to the target address, or the target > address. > > > Is it safe to assume that this is a MUST? > If yes, nd6_ns_input right now only checks if the destination is a > multicast or not (the check is more strict for DAD NS packets) and > therefore allows all node link local multicast address resolution NS > packets and process them completely (creates neighbor cache, responds > with NA etc). > > The fix is simple, however I wanted to know if there was some reason > to have it like this in the first place?: > > */** > ** Attaching target link-layer address to the NA?* > ** (RFC 2461 7.2.4)* > **** * NS IP dst is unicast/anycast MUST NOT add* > ** NS IP dst is solicited-node multicast MUST add** ** > ** In implementation, we add target link-layer address by default.* > ** We do not add one in MUST NOT cases.** */* > if (!IN6_IS_ADDR_MULTICAST > < > http://fxr.watson.org/fxr/source/netinet6/ident?v=FREEBSD10;im=bigexcerpts;i=IN6_IS_ADDR_MULTICAST > >(&daddr6)) > tlladdr = 0; > else > tlladdr = 1; > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >