For embedded systems, I would recommand connman over networkd
exactly for that sort of reasons.
networkd has been designed mainly for the datacenter use-cases with
lots of interfaces appearing and disapearing dynamically (dynamic
containers)
for the embedded case where we have only a few network interfaces
but the network itself changes a lot, connman might be a better
choice.
On 22/11/2018 08:21, Benjamin Wozniak
wrote:
Hi,
we are developing an embedded device that can only be accessed via network.
If DHCP is used for network configuration we need a plan B if for some reason
no lease can be obtained. Our idea is to have a static IP as fallback.
In systemd I didn't find any hooks to react to a lease fail. The files in
/var/run/systemd/netif apparently should not be used ("# This is private data.
Do not parse.").
Is the idea of a fallback IP address just not a good one, is such functionality
just not implemented in networkd or am I missing something here?
Thanks in advance,
Benjamin
_______________________________________________
systemd-devel mailing list
systemd-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
![SMILE]()
20 rue des Jardins
92600 Asnières-sur-Seine
|
Jérémy
ROSEN
Architecte technique
Responsable de l'expertise Smile-ECS
|
![eco]() Pour la planète,
n'imprimez ce mail que si c'est nécessaire
|
_______________________________________________
systemd-devel mailing list
systemd-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
