Skip to content
Snippets Groups Projects
Commit 236136a3 authored by GitBot's avatar GitBot Committed by Tobias Kahlki
Browse files

Integrate meta-seconorth-machine/kirkstone-stabilize-ip-for-edgehog

--

Commit: seco-ne/yocto/layers/meta-seconorth-machine@48a0f29e



systemd-conf:wired.network: do not send DHCP release on service stop

Fix the problem with floating IP addresses after first reboot in Edgehog
image.

Even when a stable MAC is assigned to device via device-tree, an IP address
may change after the first reboot.
This is due to default implementation of built-in DHCP client provided by
systemd-network daemon - DHCP RELEASE packet is sent to the DHCP server
during reboot by this daemon. So, next time a new IP address is allocated
to the same DHCP client (device).

To change this behavior of the DHCP client, a
"KeepConfiguration=dhcp-on-stop" option is enabled in configuration file
for systemd-networkd.

Signed-off-by: default avatarMikhail Vanyulin <mikhail.vanyulin@rtsoft.de>
parent eb38e76e
No related branches found
No related tags found
No related merge requests found
...@@ -21,7 +21,7 @@ ...@@ -21,7 +21,7 @@
<project name="meta-qt5.git" revision="5b71df60e523423b9df6793de9387f87a149ac42" remote="qt5-github" path="sources/meta-qt5" /> <project name="meta-qt5.git" revision="5b71df60e523423b9df6793de9387f87a149ac42" remote="qt5-github" path="sources/meta-qt5" />
<project name="meta-freescale.git" revision="dd98526300937450d741c9b3403799632f417226" remote="fslc" path="sources/meta-freescale" /> <project name="meta-freescale.git" revision="dd98526300937450d741c9b3403799632f417226" remote="fslc" path="sources/meta-freescale" />
<project name="meta-freescale-distro.git" revision="fc15f5003043da23212596be7366ae2547c308ad" remote="fslc" path="sources/meta-freescale-distro" /> <project name="meta-freescale-distro.git" revision="fc15f5003043da23212596be7366ae2547c308ad" remote="fslc" path="sources/meta-freescale-distro" />
<project name="layers/meta-seconorth-machine" revision="71ffe532ac72507334f30de1737f752ddaf7c667" remote="seco-ne" path="sources/meta-seconorth-machine" /> <project name="layers/meta-seconorth-machine" revision="48a0f29eac1102d1cdc15d272ab0c00e9e21c2fb" remote="seco-ne" path="sources/meta-seconorth-machine" />
<project name="layers/meta-seconorth-distro" revision="debd9eac6efcbf00da8a4c26a5a604b058c8da20" remote="seco-ne" path="sources/meta-seconorth-distro" /> <project name="layers/meta-seconorth-distro" revision="debd9eac6efcbf00da8a4c26a5a604b058c8da20" remote="seco-ne" path="sources/meta-seconorth-distro" />
<project name="layers/meta-seconorth-nogplv3" revision="d6150e648f3e094064a6283ee656522127f090b0" remote="seco-ne" path="sources/meta-seconorth-nogplv3" /> <project name="layers/meta-seconorth-nogplv3" revision="d6150e648f3e094064a6283ee656522127f090b0" remote="seco-ne" path="sources/meta-seconorth-nogplv3" />
<project name="config" revision="ce985857de627421fa088d65facb4ce35636407b" remote="seco-ne" path=".conf" > <project name="config" revision="ce985857de627421fa088d65facb4ce35636407b" remote="seco-ne" path=".conf" >
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment