From: Paul Fertser <fercerpav@gmail.com>
To: Alexander Amelkin <a.amelkin@yadro.com>
Cc: raviteja bailapudi <raviteja28031990@gmail.com>,
Ratan Gupta <ratankgupta31@gmail.com>,
OpenBMC Maillist <openbmc@lists.ozlabs.org>,
Sunitha Harish <sunithaharish04@gmail.com>,
"johnathanx.mantey@intel.com" <johnathanx.mantey@intel.com>,
"wak@google.com" <wak@google.com>
Subject: Re: Add network RoutingPolicyRules at OpenBMC Networkd
Date: Fri, 13 Oct 2023 15:04:27 +0300 [thread overview]
Message-ID: <ZSkySyyLSmmonxiW@home.paul.comp> (raw)
In-Reply-To: <c0dc4e1ff3904a9c8f34c951611d3992@yadro.com>
Hello,
A short clarification inline.
On Fri, Oct 13, 2023 at 11:18:33AM +0000, Alexander Amelkin wrote:
> I may be missing some use-cases, but I gather link-local addresses are primarily
> needed for discovery of newly installed OpenBMC
>
> machines before they are properly integrated into a DHCP-based or statically
> configure network. Taking that into account, in my
>
> humble opinion, the best way would be to have link-local addressing enabled for
> just eth0.
To avoid potential of confusion it's important to note that the
reasoning applies to legacy IP only, for IPv6 every interface normally
has a link-local address at all times.
--
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercerpav@gmail.com
next prev parent reply other threads:[~2023-10-13 12:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-11 8:26 Add network RoutingPolicyRules at OpenBMC Networkd raviteja bailapudi
2023-10-13 11:18 ` Alexander Amelkin
2023-10-13 12:04 ` Paul Fertser [this message]
2023-10-13 13:17 ` Sunitha Harish
2023-10-14 18:29 ` Alexander Amelkin
2023-10-18 5:24 ` raviteja bailapudi
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=ZSkySyyLSmmonxiW@home.paul.comp \
--to=fercerpav@gmail.com \
--cc=a.amelkin@yadro.com \
--cc=johnathanx.mantey@intel.com \
--cc=openbmc@lists.ozlabs.org \
--cc=ratankgupta31@gmail.com \
--cc=raviteja28031990@gmail.com \
--cc=sunithaharish04@gmail.com \
--cc=wak@google.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.