From: Jakub Kicinski <jakub.kicinski@netronome.com>
To: "Maciej Żenczykowski" <zenczykowski@gmail.com>
Cc: "Maciej Żenczykowski" <maze@google.com>,
"David S . Miller" <davem@davemloft.net>,
"Linux Network Development Mailing List" <netdev@vger.kernel.org>,
"Marcelo Ricardo Leitner" <marcelo.leitner@gmail.com>,
"Sean Tranchetti" <stranche@codeaurora.org>,
"Eric Dumazet" <edumazet@google.com>,
"Linux SCTP" <linux-sctp@vger.kernel.org>,
"Subash Abhinov Kasiviswanathan" <subashab@codeaurora.org>
Subject: Re: [PATCH v2] net: introduce ip_local_unbindable_ports sysctl
Date: Mon, 9 Dec 2019 15:42:16 -0800 [thread overview]
Message-ID: <20191209154216.7e19e0c0@cakuba.netronome.com> (raw)
In-Reply-To: <20191209224530.156283-1-zenczykowski@gmail.com>
On Mon, 9 Dec 2019 14:45:30 -0800, Maciej Żenczykowski 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?
WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <jakub.kicinski@netronome.com>
To: "Maciej Żenczykowski" <zenczykowski@gmail.com>
Cc: "Maciej Żenczykowski" <maze@google.com>,
"David S . Miller" <davem@davemloft.net>,
"Linux Network Development Mailing List" <netdev@vger.kernel.org>,
"Marcelo Ricardo Leitner" <marcelo.leitner@gmail.com>,
"Sean Tranchetti" <stranche@codeaurora.org>,
"Eric Dumazet" <edumazet@google.com>,
"Linux SCTP" <linux-sctp@vger.kernel.org>,
"Subash Abhinov Kasiviswanathan" <subashab@codeaurora.org>
Subject: Re: [PATCH v2] net: introduce ip_local_unbindable_ports sysctl
Date: Mon, 09 Dec 2019 23:42:16 +0000 [thread overview]
Message-ID: <20191209154216.7e19e0c0@cakuba.netronome.com> (raw)
In-Reply-To: <20191209224530.156283-1-zenczykowski@gmail.com>
On Mon, 9 Dec 2019 14:45:30 -0800, Maciej Żenczykowski 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?
next prev parent reply other threads:[~2019-12-09 23:42 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-27 0:13 [PATCH] net: introduce ip_local_unbindable_ports sysctl Maciej Żenczykowski
2019-11-27 0:13 ` Maciej Żenczykowski
2019-11-27 2:10 ` subashab
2019-11-27 13:14 ` Marcelo Ricardo Leitner
2019-11-27 13:14 ` Marcelo Ricardo Leitner
2019-11-27 20:50 ` Maciej Żenczykowski
2019-11-27 20:50 ` Maciej Żenczykowski
2019-11-27 22:33 ` David Miller
2019-11-27 22:33 ` David Miller
2019-11-27 23:00 ` Marcelo Ricardo Leitner
2019-11-27 23:00 ` Marcelo Ricardo Leitner
2019-11-29 20:00 ` Maciej Żenczykowski
2019-11-29 20:00 ` Maciej Żenczykowski
2019-12-04 18:27 ` Marcelo Ricardo Leitner
2019-12-04 18:27 ` Marcelo Ricardo Leitner
2019-12-09 22:43 ` Maciej Żenczykowski
2019-12-09 22:43 ` Maciej Żenczykowski
2019-12-09 22:45 ` [PATCH v2] " Maciej Żenczykowski
2019-12-09 22:45 ` Maciej Żenczykowski
2019-12-09 23:42 ` Jakub Kicinski [this message]
2019-12-09 23:42 ` Jakub Kicinski
2019-12-10 0:02 ` Maciej Żenczykowski
2019-12-10 0:02 ` Maciej Żenczykowski
2019-12-10 0:18 ` Jakub Kicinski
2019-12-10 0:18 ` Jakub Kicinski
2019-12-10 7:00 ` subashab
2019-12-10 11:46 ` Maciej Żenczykowski
2019-12-10 11:46 ` Maciej Żenczykowski
2019-12-10 17:31 ` Jakub Kicinski
2019-12-10 17:31 ` Jakub Kicinski
2019-12-13 0:16 ` Lorenzo Colitti
2019-12-13 0:16 ` Lorenzo Colitti
2019-12-13 0:47 ` Jakub Kicinski
2019-12-13 0:47 ` Jakub Kicinski
2019-12-13 0:57 ` Lorenzo Colitti
2019-12-13 0:57 ` Lorenzo Colitti
2019-12-13 1:53 ` subashab
2019-12-13 1:53 ` subashab
2019-12-13 2:04 ` Jakub Kicinski
2019-12-13 2:04 ` Jakub Kicinski
2019-12-10 19:28 ` David Miller
2019-12-10 19:28 ` David Miller
[not found] ` <0101016eee9bf9b5-f5615781-f0a6-41c4-8e9d-ed694eccf07c-000000@us-west-2.amazonses.com>
2019-12-10 17:12 ` Jakub Kicinski
2019-12-10 17:12 ` Jakub Kicinski
2019-12-10 18:12 ` subashab
2019-12-13 0:25 ` [PATCH] " Lorenzo Colitti
2019-12-13 0:25 ` Lorenzo Colitti
2019-12-13 11:49 ` Neil Horman
2019-12-13 11:49 ` Neil Horman
2019-12-19 9:35 ` Lorenzo Colitti
2019-12-19 9:35 ` Lorenzo Colitti
2019-12-19 13:17 ` Neil Horman
2019-12-19 13:17 ` Neil Horman
2019-12-19 14:02 ` Lorenzo Colitti
2019-12-19 14:02 ` Lorenzo Colitti
2019-12-19 16:57 ` Neil Horman
2019-12-19 16:57 ` Neil Horman
2019-12-19 17:52 ` David Miller
2019-12-19 17:52 ` David Miller
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=20191209154216.7e19e0c0@cakuba.netronome.com \
--to=jakub.kicinski@netronome.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=linux-sctp@vger.kernel.org \
--cc=marcelo.leitner@gmail.com \
--cc=maze@google.com \
--cc=netdev@vger.kernel.org \
--cc=stranche@codeaurora.org \
--cc=subashab@codeaurora.org \
--cc=zenczykowski@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.