[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f0dbd495-5d27-46e5-a615-3e6bdcd0948b@openvpn.net>
Date: Wed, 6 Mar 2024 16:51:47 +0100
From: Antonio Quartulli <antonio@...nvpn.net>
To: Andrew Lunn <andrew@...n.ch>
Cc: netdev@...r.kernel.org, Jakub Kicinski <kuba@...nel.org>,
Sergey Ryazanov <ryazanov.s.a@...il.com>, Paolo Abeni <pabeni@...hat.com>,
Eric Dumazet <edumazet@...gle.com>
Subject: Re: [PATCH net-next v2 02/22] net: introduce OpenVPN Data Channel
Offload (ovpn)
On 04/03/2024 21:47, Andrew Lunn wrote:
>> + IN_DEV_CONF_SET(dev_v4, SEND_REDIRECTS, false);
>> + IPV4_DEVCONF_ALL(dev_net(dev), SEND_REDIRECTS) = false;
>
> Wireguard has the same. How is Linux getting confused? Maybe we should
> consider fixing this properly?
>
I wanted to reply to this point individually.
The reason for requiring this setting lies in the OpenVPN server acting
as relay point for hosts in the same subnet.
Example: given the a.b.c.0/24 IP network, you will have .2 that in order
to talk to .3 must have its traffic relayed by .1 (the server).
When the kernel sees this traffic it will send the ICMP redirects,
because it believes that .2 should directly talk to .3 without passing
through .1.
It of course makes sense in a normal network with a classic broadcast
domain, but this is not the case in a VPN implemented as a start topology.
Does it make sense?
The only way I see to fix this globally is to have an extra flag in the
netdevice signaling this peculiarity and thus disabling ICMP redirects
automatically.
Regards,
--
Antonio Quartulli
OpenVPN Inc.
Powered by blists - more mailing lists