From: Johnathan Mantey <johnathanx.mantey@intel.com>
To: Heyi Guo <guoheyi@linux.alibaba.com>, openbmc <openbmc@lists.ozlabs.org>
Cc: Ratan Gupta <ratankgupta31@gmail.com>,
Nagaraju Goruganti <ngorugan@in.ibm.com>,
Adriana Kobylak <anoo@us.ibm.com>,
William Kennington <wak@google.com>
Subject: Re: phosphor-network: does it make sense to disable systemd-networkd sending DHCP release?
Date: Wed, 2 Mar 2022 07:50:05 -0800 [thread overview]
Message-ID: <f392c47a-76d2-c9f5-44f4-07f127f8e928@intel.com> (raw)
In-Reply-To: <13769f21-e6c3-5550-909a-fa0893c1c32a@linux.alibaba.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 1082 bytes --]
On 2/21/22 01:05, Heyi Guo wrote:
> Hi all,
>
> Now systemd-networkd will send DHCP release packet when BMC reboots.
> This may cause BMC to lose its original aquired IP after next boot up.
> I see this feature can be disabled by adding below lines to the
> configuration file of systemd-networkd:
>
> [DHCPv4]
> SendRelease=false
>
> Does it make sense to disable DHCP release? Or is there any reason for
> the current default configuration in phosphor-network?
>
> Thanks,
>
> Heyi
>
FWIW, users within Intel get very cranky when their IPv4 addresses
change. I'm presently working on a defect related to the IP address
being altered.
As it is unclear there is a run-time mechanism for changing this value,
I'd at least like to see a compile time control. I expect Intel will
choose to block sending a DHCP release request for when the BMC reboots.
--
Johnathan Mantey
Senior Software Engineer
*azad te**chnology partners*
Contributing to Technology Innovation since 1992
Phone: (503) 712-6764
Email: johnathanx.mantey@intel.com
[-- Attachment #1.1.2: Type: text/html, Size: 2302 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
next prev parent reply other threads:[~2022-03-02 15:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-21 9:05 phosphor-network: does it make sense to disable systemd-networkd sending DHCP release? Heyi Guo
2022-03-02 15:50 ` Johnathan Mantey [this message]
2022-03-06 1:54 ` Heyi Guo
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=f392c47a-76d2-c9f5-44f4-07f127f8e928@intel.com \
--to=johnathanx.mantey@intel.com \
--cc=anoo@us.ibm.com \
--cc=guoheyi@linux.alibaba.com \
--cc=ngorugan@in.ibm.com \
--cc=openbmc@lists.ozlabs.org \
--cc=ratankgupta31@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.