From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jiri Benc Subject: Re: [PATCH net-next 00/11] ICMP error handling for UDP tunnels Date: Wed, 7 Nov 2018 12:09:51 +0100 Message-ID: <20181107120951.2a9af149@redhat.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: "David S. Miller" , Sabrina Dubroca , Xin Long , netdev@vger.kernel.org To: Stefano Brivio Return-path: Received: from mx1.redhat.com ([209.132.183.28]:37258 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726266AbeKGUjs (ORCPT ); Wed, 7 Nov 2018 15:39:48 -0500 In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: On Tue, 6 Nov 2018 22:38:56 +0100, Stefano Brivio wrote: > - patch 1/11 adds a socket lookup for UDP tunnels that use, by design, > the same destination port on both endpoints -- i.e. VxLAN and GENEVE This is not necessarily true with lwtunnels (collect_md mode of VXLAN and GENEVE). While any sane setup will use the same dst ports, there's really nothing that enforces it. Of course, in that case we have no way to map the ICMP error back to the tunnel. Generally speaking, I'm not sure how ICMP error handling should work for external control planes. Are we sure they want PMTU discovery and route redirection done by the kernel? (I am not sure, neither way.) Jiri