<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<br>
<div class="moz-cite-prefix">On 2/21/22 01:05, Heyi Guo wrote:<br>
</div>
<blockquote type="cite"
cite="mid:13769f21-e6c3-5550-909a-fa0893c1c32a@linux.alibaba.com">Hi
all,
<br>
<br>
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:
<br>
<br>
[DHCPv4]
<br>
SendRelease=false
<br>
<br>
Does it make sense to disable DHCP release? Or is there any reason
for the current default configuration in phosphor-network?
<br>
<br>
Thanks,
<br>
<br>
Heyi
<br>
<br>
</blockquote>
<br>
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.<br>
<br>
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.<br>
<br>
<br>
<div class="moz-signature">-- <br>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<title></title>
<font color="#1F497D"><font face="Century Gothic">Johnathan Mantey<br>
<small>Senior Software Engineer</small><br>
<big><font color="#555555"><small><b>azad te</b><b>chnology
partners</b></small><br>
<small><font color="#1F497D"><small>Contributing to
Technology Innovation since 1992</small></font><small><br>
<font color="#1F497D">Phone: (503) 712-6764<br>
Email: <a href="mailto:johnathanx.mantey@intel.com"
class="moz-txt-link-freetext">johnathanx.mantey@intel.com</a></font></small><br>
<br>
</small></font></big></font></font> </div>
</body>
</html>