From: Jakub Kicinski <kuba@kernel.org>
To: Dmitry Skorodumov <skorodumov.dmitry@huawei.com>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<andrey.bokhanko@huawei.com>, <edumazet@google.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Paolo Abeni <pabeni@redhat.com>
Subject: Re: [PATCH net-next 04/13] ipvlan: Support IPv6 in macnat mode.
Date: Tue, 18 Nov 2025 17:23:04 -0800 [thread overview]
Message-ID: <20251118172304.0cf92242@kernel.org> (raw)
In-Reply-To: <20251118100046.2944392-5-skorodumov.dmitry@huawei.com>
On Tue, 18 Nov 2025 13:00:36 +0300 Dmitry Skorodumov wrote:
> To make IPv6 work with macnat mode, need to
> process the TX-path:
> * Replace Source-ll-addr in Solicitation ndisc,
> * Replace Target-ll-addr in Advertisement ndisc
>
> No need to do anything in RX-path
drivers/net/ipvlan/ipvlan_core.c:343:18: warning: variable 'orig_skb' set but not used [-Wunused-but-set-variable]
343 | struct sk_buff *orig_skb = skb;
| ^
next prev parent reply other threads:[~2025-11-19 1:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-18 10:00 [PATCH v4 net-next 00/13] ipvlan: support mac-nat mode Dmitry Skorodumov
2025-11-18 10:00 ` [PATCH net-next 01/13] ipvlan: Support MACNAT mode Dmitry Skorodumov
2025-11-18 10:00 ` [PATCH net-next 02/13] ipvlan: macnat: Handle rx mcast-ip and unicast eth Dmitry Skorodumov
2025-11-18 10:00 ` [PATCH net-next 03/13] ipvlan: Forget all IP when device goes down Dmitry Skorodumov
2025-11-18 10:00 ` [PATCH net-next 04/13] ipvlan: Support IPv6 in macnat mode Dmitry Skorodumov
2025-11-19 1:23 ` Jakub Kicinski [this message]
2025-11-19 3:25 ` kernel test robot
2025-11-18 10:00 ` [PATCH net-next 05/13] ipvlan: Fix compilation warning about __be32 -> u32 Dmitry Skorodumov
2025-11-18 12:47 ` Eric Dumazet
2025-11-19 1:26 ` Jakub Kicinski
2025-11-20 11:15 ` Dmitry Skorodumov
2025-11-20 15:21 ` Jakub Kicinski
2025-11-18 10:00 ` [PATCH net-next 06/13] ipvlan: Make the addrs_lock be per port Dmitry Skorodumov
2025-11-18 10:00 ` [PATCH net-next 07/13] ipvlan: Take addr_lock in ipvlan_open() Dmitry Skorodumov
2025-11-18 10:00 ` [PATCH net-next 08/13] ipvlan: Don't allow children to use IPs of main Dmitry Skorodumov
2025-11-18 10:00 ` [PATCH net-next 09/13] ipvlan: const-specifier for functions that use iaddr Dmitry Skorodumov
2025-11-18 10:00 ` [PATCH net-next 10/13] ipvlan: Common code from v6/v4 validator_event Dmitry Skorodumov
2025-11-18 10:00 ` [PATCH net-next 11/13] ipvlan: common code to handle ipv6/ipv4 address events Dmitry Skorodumov
2025-11-18 10:00 ` [PATCH net-next 12/13] ipvlan: Ignore PACKET_LOOPBACK in handle_mode_l2() Dmitry Skorodumov
2025-11-18 10:00 ` [PATCH net-next 13/13] selftests: drv-net: selftest for ipvlan-macnat mode Dmitry Skorodumov
2025-11-19 1:25 ` Jakub Kicinski
2025-11-18 14:57 ` [syzbot ci] Re: ipvlan: support mac-nat mode syzbot ci
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20251118172304.0cf92242@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=andrey.bokhanko@huawei.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=skorodumov.dmitry@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).