From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from smtp2.osuosl.org (smtp2.osuosl.org [140.211.166.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 5EA75CDB483 for ; Wed, 18 Oct 2023 18:00:16 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp2.osuosl.org (Postfix) with ESMTP id 0C3B441930; Wed, 18 Oct 2023 18:00:16 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org 0C3B441930 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=osuosl.org; s=default; t=1697652016; bh=qY1RVN4kD2j5mziWMqJE/TCr/tDxJHJB3rhBdKt4bxo=; h=Date:From:To:References:In-Reply-To:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: Cc:From; b=4oUwleY6cATH1YDikJVgDI6JLz2Rlw4Veoai7KRasTKQUSMY7wYkThZkQzIGgUGTT xU7RjDNRBY1vY+bkRM+zFRDAo4ZjOUwRh9CZYrYDO+5bbtQ1VcJHEaZy+JlaPnYNkb PJI/kISGCdFyBfgucQulKXiNL3pLYDqH3cHu5xQucbnPioLqTvpnCtY03lcHXwUqIm kbaBTtb3BD8F57Uz00nzn4UTmn2QNqbjMCStQH7bJCPNq9erBI3wi1QxvUAxSIarl9 WlxCfl/eOYOdW97nbWAY5Xpbt1rvEtgx5dLZMfkDIVJiBw8IgqdXAhvQesGAvgSyEb suKXM7LdD7B+Q== X-Virus-Scanned: amavisd-new at osuosl.org Received: from smtp2.osuosl.org ([127.0.0.1]) by localhost (smtp2.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZYHcOimDQ6x1; Wed, 18 Oct 2023 18:00:15 +0000 (UTC) Received: from ash.osuosl.org (ash.osuosl.org [140.211.166.34]) by smtp2.osuosl.org (Postfix) with ESMTP id DF18B4192E; Wed, 18 Oct 2023 18:00:14 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org DF18B4192E Received: from smtp2.osuosl.org (smtp2.osuosl.org [140.211.166.133]) by ash.osuosl.org (Postfix) with ESMTP id 828071BF5D7 for ; Wed, 18 Oct 2023 18:00:13 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp2.osuosl.org (Postfix) with ESMTP id 585684192E for ; Wed, 18 Oct 2023 18:00:13 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org 585684192E X-Virus-Scanned: amavisd-new at osuosl.org Received: from smtp2.osuosl.org ([127.0.0.1]) by localhost (smtp2.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DDmLU5pdpjWY for ; Wed, 18 Oct 2023 18:00:11 +0000 (UTC) Received: from ganesha.gnumonks.org (ganesha.gnumonks.org [IPv6:2001:780:45:1d:225:90ff:fe52:c662]) by smtp2.osuosl.org (Postfix) with ESMTPS id AA8784047D for ; Wed, 18 Oct 2023 18:00:10 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org AA8784047D Received: from uucp by ganesha.gnumonks.org with local-bsmtp (Exim 4.94.2) (envelope-from ) id 1qtApx-00EjDB-RY; Wed, 18 Oct 2023 20:00:05 +0200 Received: from laforge by nataraja with local (Exim 4.97-RC2) (envelope-from ) id 1qtAnC-00000002j2L-0xli; Wed, 18 Oct 2023 19:57:14 +0200 Date: Wed, 18 Oct 2023 19:57:14 +0200 From: Harald Welte To: Jakub Kicinski Message-ID: References: <20231012060115.107183-1-hayatake396@gmail.com> <20231016152343.1fc7c7be@kernel.org> <20231017164915.23757eed@kernel.org> <20231018103703.41fd4d9b@kernel.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20231018103703.41fd4d9b@kernel.org> Subject: Re: [Intel-wired-lan] [PATCH net-next v2] ethtool: ice: Support for RSS settings to GTP from ethtool X-BeenThere: intel-wired-lan@osuosl.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Intel Wired Ethernet Linux Kernel Driver Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Willem de Bruijn , netdev@vger.kernel.org, osmocom-net-gprs@lists.osmocom.org, Jesse Brandeburg , linux-kernel@vger.kernel.org, Eric Dumazet , Tony Nguyen , takeru hayasaka , intel-wired-lan@lists.osuosl.org, Paolo Abeni , "David S. Miller" , Pablo Neira Ayuso Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: intel-wired-lan-bounces@osuosl.org Sender: "Intel-wired-lan" Hi Jakub, On Wed, Oct 18, 2023 at 10:37:03AM -0700, Jakub Kicinski wrote: > Harald went further and questioned use of the same IP addresses for > -U and -C traffic, but even within one endpoint aren't these running > on a different port? yes. > Can someone reasonably use the same UDP port for both types of traffic? I don't think so. In the entire 3GPP protocol world, the UDP port numbers for GTP-U and GTP-C are fixed. The various signaling protocols allow you to communicate the IPv4/v6 address and TEID of tunnel endpoints, but never allow you to communicate the port number - which hence must always be the well-known port (2123 for GTP-C + 2152 for GTP-U). Of course somebody could do whatever they want in some kind of internal interface not required to interoperate with any other equipment/implementation/operator, but I'd consider it not falling in your question of "reasonable use". Regards, Harald -- - Harald Welte https://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) _______________________________________________ Intel-wired-lan mailing list Intel-wired-lan@osuosl.org https://lists.osuosl.org/mailman/listinfo/intel-wired-lan