[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1d595632-ae6d-39f0-b624-7dfc5bfc1ea7@kernel.org>
Date: Mon, 11 Apr 2022 10:13:44 -0600
From: David Ahern <dsahern@...nel.org>
To: Arun Ajith S <aajith@...sta.com>
Cc: netdev@...r.kernel.org, davem@...emloft.net,
linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org,
yoshfuji@...ux-ipv6.org, kuba@...nel.org, pabeni@...hat.com,
corbet@....net, prestwoj@...il.com, gilligan@...sta.com,
noureddine@...sta.com, gk@...sta.com
Subject: Re: [PATCH net-next v2] net/ipv6: Introduce accept_unsolicited_na
knob to implement router-side changes for RFC9131
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=<HEX-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.<interface>.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.
Powered by blists - more mailing lists