From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id C0AABC433EF for ; Mon, 11 Apr 2022 16:13:53 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1344051AbiDKQQF (ORCPT ); Mon, 11 Apr 2022 12:16:05 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:55018 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231284AbiDKQQC (ORCPT ); Mon, 11 Apr 2022 12:16:02 -0400 Received: from ams.source.kernel.org (ams.source.kernel.org [IPv6:2604:1380:4601:e00::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A93BC2B8; Mon, 11 Apr 2022 09:13:48 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id 6EDA0B81704; Mon, 11 Apr 2022 16:13:47 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 76885C385A3; Mon, 11 Apr 2022 16:13:45 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1649693626; bh=S4RgEBNrSyI+ophc0QVA8uNOdYjwnqrns4P7akRNFaI=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=u6j2TNukG/Ye5tRQPNUxnV2SOuyDUoYoChUBMIbom+cpoQ0Zn/BEGeeQb3x33QKy6 iLS44nfmiV0iqUPciH14pEgtnMGByPaiINkJeyDpGpE+rhUC7ge4KRijekqh1TjRGA qseaDRToWLTReU/pvUu+81XSxrsu93EoG7ecEWegxNmMpJAo8bZYHuyA0fs3ZClIGW QzpjAN1iraiktH0G3WnTmK5oRfuB+thCM6cL9rMJ9OUBvGgu/C7i2Vi8x1wU7eFlw1 TZJwZzLxneElwllZsXdw3TPhhi3Xwhrvud+o0n4UdYwgYcQteqaYVLZoaENV7abKUm IqFJ2fHTiw4MA== Message-ID: <1d595632-ae6d-39f0-b624-7dfc5bfc1ea7@kernel.org> Date: Mon, 11 Apr 2022 10:13:44 -0600 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.7.0 Subject: Re: [PATCH net-next v2] net/ipv6: Introduce accept_unsolicited_na knob to implement router-side changes for RFC9131 Content-Language: en-US To: Arun Ajith S Cc: netdev@vger.kernel.org, davem@davemloft.net, linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org, yoshfuji@linux-ipv6.org, kuba@kernel.org, pabeni@redhat.com, corbet@lwn.net, prestwoj@gmail.com, gilligan@arista.com, noureddine@arista.com, gk@arista.com References: <20220407074428.1623-1-aajith@arista.com> From: David Ahern In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On 4/11/22 9:41 AM, Arun Ajith S wrote: > > mausezahn doesn't have good support for ICMPv6. > I tried using --type icmp6 -t icmp6 "type=136, payload=" > to manually craft a NA packet with the target address and the target > ll addr option. > But it still doesn't allow me to set the flags to mark it as an > unsolicited advertisement. > > How about this alternative for a test: > 1. Setup a veth tunnel across two namespaces, one end being the host > and the other the router. > 2. On the host side, I can configure > net.ipv6.conf..ndisc_notify to send out unsolicited NAs. > 3. On the router side, I can try out various combinations of > (accept_unsolicited_na, drop_unsolicted_na and forwarding) > that works too. even simpler.