[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHS8izP-Dtvjgq009iXSpijsePb6VOF-52dj=U+r4KjxikHeow@mail.gmail.com>
Date: Thu, 3 Oct 2024 00:07:31 -0700
From: Mina Almasry <almasrymina@...gle.com>
To: Stanislav Fomichev <sdf@...ichev.me>
Cc: netdev@...r.kernel.org, davem@...emloft.net, edumazet@...gle.com,
kuba@...nel.org, pabeni@...hat.com
Subject: Re: [PATCH net-next v2 06/12] selftests: ncdevmem: Switch to AF_INET6
On Mon, Sep 30, 2024 at 10:18 AM Stanislav Fomichev <sdf@...ichev.me> wrote:
>
> Use dualstack socket to support both v4 and v6. v4-mapped-v6 address
> can be used to do v4.
>
The network on test machines I can run ncdevmem on are ipv4 only, and
ipv6 support is not possible for my test setup at all. Probably a mega
noob question, but are these changes going to regress such networks?
Or does the dualstack support handle ipv4 networks seamlessly?
If such regression is there, maybe we can add a -6 flag that enables
ipv6 support similar to how other binaries like nc do it?
Powered by blists - more mailing lists