On Tue, Dec 13, 2022 at 4:58 PM John Lemonovich
wrote:
>
> Thanks for the replies. Yes David, it's also my understanding per the spec,
> that the client's link-local address must be included for the solicit message.
Where does it say that in https://www.rfc-editor.org/rfc/rfc3315 ?
> The
From: John Lemonovich
> Sent: 13 December 2022 15:59
>
> Thanks for the replies. Yes David, it's also my understanding per the spec,
> that the client's link-
> local address must be included for the solicit message. The reply from the
> server is unicast. What
> do you mean by the proper
From: Denys Vlasenko
> Sent: 13 December 2022 15:22
>
> On Fri, Dec 9, 2022 at 5:09 PM John Lemonovich
> wrote:
> > Hello Denys,
> >
> > I am working on an embedded Linux project using an intel Arria 10 FPGA and
> > have been using IPv4 for
> a long time, and now need IPv6. I found your email
On Fri, Dec 9, 2022 at 5:09 PM John Lemonovich
wrote:
> Hello Denys,
>
> I am working on an embedded Linux project using an intel Arria 10 FPGA and
> have been using IPv4 for a long time, and now need IPv6. I found your email
> online searching for help. I have many things working with IPv6,
> +config LOOP_CONFIGURE
> + bool "always uses LOOP_CONFIGURE, kernel version >= 5.8"
> +
> +config NO_LOOP_CONFIGURE
> + bool "never uses LOOP_CONFIGURE, kernel version < 5.8"
> +
> +config TRY_LOOP_CONFIGURE
> + bool "try LOOP_CONFIGURE, kernel version is unknown"
The