From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jakub Kicinski Date: Mon, 09 Dec 2019 23:42:16 +0000 Subject: Re: [PATCH v2] net: introduce ip_local_unbindable_ports sysctl Message-Id: <20191209154216.7e19e0c0@cakuba.netronome.com> List-Id: References: <20191209224530.156283-1-zenczykowski@gmail.com> In-Reply-To: <20191209224530.156283-1-zenczykowski@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: Maciej =?UTF-8?B?xbtlbmN6eWtvd3NraQ==?= Cc: Maciej =?UTF-8?B?xbtlbmN6eWtvd3NraQ==?= , "David S . Miller" , Linux Network Development Mailing List , Marcelo Ricardo Leitner , Sean Tranchetti , Eric Dumazet , Linux SCTP , Subash Abhinov Kasiviswanathan On Mon, 9 Dec 2019 14:45:30 -0800, Maciej =C5=BBenczykowski wrote: > Example use cases might be: > - a port being stolen by the nic for remote serial console, remote > power management or some other sort of debugging functionality > (crash collection, gdb, direct access to some other microcontroller > on the nic or motherboard, remote management of the nic itself). This use case makes me a little uncomfortable. Could you elaborate what protocols and products are in need of this functionality? Why can't the NIC just get its own IP like it usually does with NCSI? 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 X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 8549AC43603 for ; Mon, 9 Dec 2019 23:42:22 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 4A50B2071E for ; Mon, 9 Dec 2019 23:42:22 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=netronome-com.20150623.gappssmtp.com header.i=@netronome-com.20150623.gappssmtp.com header.b="fSf1ZGmS" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727291AbfLIXmV (ORCPT ); Mon, 9 Dec 2019 18:42:21 -0500 Received: from mail-pj1-f65.google.com ([209.85.216.65]:43577 "EHLO mail-pj1-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727123AbfLIXmU (ORCPT ); Mon, 9 Dec 2019 18:42:20 -0500 Received: by mail-pj1-f65.google.com with SMTP id g4so6562570pjs.10 for ; Mon, 09 Dec 2019 15:42:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=netronome-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :organization:mime-version:content-transfer-encoding; bh=V+QMhx7ddpbkcSbPVKvyp45lyXMPmAo/pgMKOqAodfE=; b=fSf1ZGmSL3/xD1sMkMysZYFQFkGtn4G49qvt9u4+83SppEPRq/o5shJLAh1xxMujyM VC8EVKvtCCF5tXdXKNzmki+xLo2g7WdS2UrLud6KSRM2ReK0TNZDd+c8F46NbwYLI2vx hek5iKYcDWlYOAAR0OSqHN7uIbTW27q7zhQSIGmLub8HR+sjnlIoMrleANj4pX3f7/LS M/YbmE76H8VqGGw6nUDGNeHMc5bQDCTZymYFmg4cFyHlPsDIsXN+VSW/W/YA93pUJAme c4lOGrIhofDpQupdRbBxJo5Z19M7z5rFb3rGDldu2L/4gXoSmlatMo8R7D47iILS8lzr DUSw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:organization:mime-version:content-transfer-encoding; bh=V+QMhx7ddpbkcSbPVKvyp45lyXMPmAo/pgMKOqAodfE=; b=Ci9DZ/JEUwzcPDzhCXbdNgejqqO5zCzmDY56TNeP/oBPyhPu0XbMRx3RFxD20yAvCF KEx6i/qCs+QHP5wL+Ej8Kj4mXc1+S7MaShbEDbJ+lu89snEF5V0fD3SwJUFBYcT1wdP7 bYXaxPHmHKXjcqKchY/IeJp/X1r3Gg3PMzgmYnla+HgtNOGN2LEPWZ9eQYcITBA7pWzo Qj/UCmjjuA91g9u3coonJIC/mX9SWjiEY8zSTWHBxmPMtD1xBR/eyFGZaBNnLYtIfM1f QuTyPed9wRjdq0jlMzn0Kj3wySZHGwQMg08W92+/EphRNc31SMt6uLQnZcxRVEbhkns7 I7gA== X-Gm-Message-State: APjAAAU043pku6MC5S/kIQoIX0jSb8WhepNOLsUvXDX+BUxf74onbD46 aYdeuWTHhqg69RKFGg3mZphnTQ== X-Google-Smtp-Source: APXvYqyfZb7MEcnxbUPQl2yGD5rqMg8NC6Pf7z6qDPwFCvFdZjlSfWs3Vqyy3mFRXwiM+UpLFcbzCg== X-Received: by 2002:a17:902:820f:: with SMTP id x15mr32558307pln.125.1575934940114; Mon, 09 Dec 2019 15:42:20 -0800 (PST) Received: from cakuba.netronome.com ([66.60.152.14]) by smtp.gmail.com with ESMTPSA id w3sm552243pfd.161.2019.12.09.15.42.19 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 09 Dec 2019 15:42:19 -0800 (PST) Date: Mon, 9 Dec 2019 15:42:16 -0800 From: Jakub Kicinski To: Maciej =?UTF-8?B?xbtlbmN6eWtvd3NraQ==?= Cc: Maciej =?UTF-8?B?xbtlbmN6eWtvd3NraQ==?= , "David S . Miller" , Linux Network Development Mailing List , Marcelo Ricardo Leitner , Sean Tranchetti , Eric Dumazet , Linux SCTP , Subash Abhinov Kasiviswanathan Subject: Re: [PATCH v2] net: introduce ip_local_unbindable_ports sysctl Message-ID: <20191209154216.7e19e0c0@cakuba.netronome.com> In-Reply-To: <20191209224530.156283-1-zenczykowski@gmail.com> References: <20191209224530.156283-1-zenczykowski@gmail.com> Organization: Netronome Systems, Ltd. MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On Mon, 9 Dec 2019 14:45:30 -0800, Maciej =C5=BBenczykowski wrote: > Example use cases might be: > - a port being stolen by the nic for remote serial console, remote > power management or some other sort of debugging functionality > (crash collection, gdb, direct access to some other microcontroller > on the nic or motherboard, remote management of the nic itself). This use case makes me a little uncomfortable. Could you elaborate what protocols and products are in need of this functionality? Why can't the NIC just get its own IP like it usually does with NCSI?