* ifupdown with systemd
@ 2025-02-27 15:19 info
2025-02-27 15:30 ` [yocto] " Alex Kiernan
0 siblings, 1 reply; 2+ messages in thread
From: info @ 2025-02-27 15:19 UTC (permalink / raw)
To: yocto
[-- Attachment #1: Type: text/plain, Size: 1094 bytes --]
Hello
I'm using Yocto (Scarthgap) on a Raspberry Pi CM4 with ifupdown and init-ifupdown included in my image. The system uses systemd as the init manager.
It seems that the init scripts for ifupdown are not executed in a systemd environment. My /etc/network/interfaces file is as follows:
# cat /etc/network/interfaces
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet dhcp
However, after a reboot, eth0 remains down:
# ip a show eth0
2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group
default qlen 1000
link/ether d8:3a:dd:a8:b6:52 brd ff:ff:ff:ff:ff:ff
altname end0
Checking systemctl shows:
# systemctl status networking
* networking.service - LSB: Raise network interfaces.
Loaded: loaded (/etc/init.d/networking; generated)
Active: inactive (dead)
Docs: man:systemd-sysv-generator(8)
I have to manually run ifup eth0 to bring up the interface. Is this expected behavior, or is there a service I need to enable to automate this?
Maybe also any other recommendation for a Network Manager, best with a high-level API?
Thanks
Benjamin
^ permalink raw reply [flat|nested] 2+ messages in thread* Re: [yocto] ifupdown with systemd
2025-02-27 15:19 ifupdown with systemd info
@ 2025-02-27 15:30 ` Alex Kiernan
0 siblings, 0 replies; 2+ messages in thread
From: Alex Kiernan @ 2025-02-27 15:30 UTC (permalink / raw)
To: yocto, info
On Thu, Feb 27, 2025 at 3:19 PM Benjamin Marty via
lists.yoctoproject.org <info=benjaminmarty.ch@lists.yoctoproject.org>
wrote:
>
> Hello
>
> I'm using Yocto (Scarthgap) on a Raspberry Pi CM4 with ifupdown and init-ifupdown included in my image. The system uses systemd as the init manager.
>
> It seems that the init scripts for ifupdown are not executed in a systemd environment. My /etc/network/interfaces file is as follows:
> # cat /etc/network/interfaces
> auto lo
> iface lo inet loopback
>
> auto eth0
> iface eth0 inet dhcp
>
> However, after a reboot, eth0 remains down:
> # ip a show eth0
> 2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group
> default qlen 1000
> link/ether d8:3a:dd:a8:b6:52 brd ff:ff:ff:ff:ff:ff
> altname end0
>
> Checking systemctl shows:
> # systemctl status networking
> * networking.service - LSB: Raise network interfaces.
> Loaded: loaded (/etc/init.d/networking; generated)
> Active: inactive (dead)
> Docs: man:systemd-sysv-generator(8)
>
> I have to manually run ifup eth0 to bring up the interface. Is this expected behavior, or is there a service I need to enable to automate this?
>
> Maybe also any other recommendation for a Network Manager, best with a high-level API?
>
systemd-networkd?
--
Alex Kiernan
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2025-02-27 15:30 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-02-27 15:19 ifupdown with systemd info
2025-02-27 15:30 ` [yocto] " Alex Kiernan
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.