# Issues with systemd-networkd **URL:** \ **Category:** General Discussions\ **Created:** [August 10, 2020, 1:08pm UTC](https://hub.mender.io/t/issues-with-systemd-networkd/2302 "2020-08-10T13:08:56Z")\ **Posts on this page:** 13\ **Page:** 2
**Author:** ![drewmoseley](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/drewmoseley/32/47_2.png) [@drewmoseley](https://hub.mender.io/u/drewmoseley)\ **Post date:** [August 12, 2020, 1:19pm UTC](https://hub.mender.io/t/issues-with-systemd-networkd/2302/21 "2020-08-12T13:19:17Z")
Yeah, that’s a good troubleshooting step. I always try to maintain a build without Mender integrated to use as a testing step. Good luck. Drew ---
**Author:** ![neuberfran](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/neuberfran/32/369_2.png) [@neuberfran](https://hub.mender.io/u/neuberfran)\ **Post date:** [August 12, 2020, 5:23pm UTC](https://hub.mender.io/t/issues-with-systemd-networkd/2302/22 "2020-08-12T17:23:56Z")
@dellgreen @drewmoseley Works in Yocto 2.0 by technexion using interfaces file and not systemd.networkd: root@pico-imx7:~# **cat /etc/network/interfaces** auto lo iface lo inet loopback iface wlan0 inet dhcp wireless\_mode managed wireless\_essid any wpa-driver wext wpa-conf /etc/wpa\_supplicant.conf iface atml0 inet dhcp # Wired or wireless interfaces auto eth0 iface eth0 inet dhcp iface eth1 inet dhcp iface usb0 inet static address 192.168.7.2 netmask 255.255.255.0 network 192.168.7.0 gateway 192.168.7.1 iface bnep0 inet dhcp ![Yocto2.0TechnexionOkUhu](https://canada1.discourse-cdn.com/flex036/uploads/mender/original/1X/17b60a7be68f07f1b2054b66fe69f9a4beb3fedc.png) ---
**Author:** ![dellgreen](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/dellgreen/32/85_2.png) [@dellgreen](https://hub.mender.io/u/dellgreen)\ **Post date:** [August 12, 2020, 7:35pm UTC](https://hub.mender.io/t/issues-with-systemd-networkd/2302/23 "2020-08-12T19:35:50Z")
that good news, given that is a totally different image, i would guess the problem was caused by how the previous image was put together. I would be less likely to be a systemd-networkd issue given how heavily and widespread it is used. Does technexion have newer yocto versions to test as 2.0 is end-of-life? (2.6, 2.7 etc) ---
**Author:** ![neuberfran](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/neuberfran/32/369_2.png) [@neuberfran](https://hub.mender.io/u/neuberfran)\ **Post date:** [August 12, 2020, 8:32pm UTC](https://hub.mender.io/t/issues-with-systemd-networkd/2302/24 "2020-08-12T20:32:23Z")
@dellgreen Did you notice some differences in the output of the **ip route show** commands from before and now, mainly in the inclusion of the line below: **192.168.1.1 dev eth1 scope link**??? **richard-hu** said:: _Actually, our next milestone will be Yocto 2.5(Sumo) which is based on NXP official linux 4.14.78\_1.0.0\_ga._ _At least, we don’t have clear plan to upgrade to Yocto 2.6(Thud) in the first half of 2019._ _PICO-IMX7D is already supported in mainline kernel._ _[https://patchwork.kernel.org/patch/10720779/](https://patchwork.kernel.org/patch/10720779/)_ _It means PICO-IMX7D is supported by [Yocto community](http://freescale.github.io/#documentation) ._ _It might not too difficult to add meta-qt support for Yocto community._ _I think it might be the quickest way to get Yocto 2.6 with QT 5.12 on PICO-IMX7D._ ---
**Author:** ![dellgreen](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/dellgreen/32/85_2.png) [@dellgreen](https://hub.mender.io/u/dellgreen)\ **Post date:** [August 12, 2020, 9:38pm UTC](https://hub.mender.io/t/issues-with-systemd-networkd/2302/25 "2020-08-12T21:38:24Z")
ip routes whilst subtly different look fine for both, albeit i’m not a iptables expert. I think the “proto kernel” bit is a tag to show how and what added the rule. Might be worth comparing the kernel versions between the image that now works and the one that didn’t to see if this sheds any light on the problem. ( uname -a) The technexion stuff looks really old, and worryingly that their rocko branch (2.4 EOL) is maintained whist their sumo (2.5 EOL) is unmaintained. I had similar issues with my board and in the end went with using poky from the main site and added uboot and kernel from fscl community supported layers that were well maintained. However i am not advocating this for you unless you enjoy a challenge as its challenging work and not something that can be talked through via a forum. 🙂 ---
**Author:** ![neuberfran](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/neuberfran/32/369_2.png) [@neuberfran](https://hub.mender.io/u/neuberfran)\ **Post date:** [August 13, 2020, 3:22pm UTC](https://hub.mender.io/t/issues-with-systemd-networkd/2302/26 "2020-08-13T15:22:41Z")
@dellgreen If you could send me 1 email with the steps for me to have an image (Yocto 2.5 (Sumo) or 2.4 - codename Rocko: \*_…sdimg_), based on what richard-ru said, I would like to thank: [neuberfran@gmail.com](mailto:neuberfran@gmail.com) ---
**Author:** ![dellgreen](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/dellgreen/32/85_2.png) [@dellgreen](https://hub.mender.io/u/dellgreen)\ **Post date:** [August 13, 2020, 4:44pm UTC](https://hub.mender.io/t/issues-with-systemd-networkd/2302/27 "2020-08-13T16:44:14Z")
I think at this point it would be worth going back to the reading material and build your own image from first principles so you can, not be restricted/dependent on the manufacturer for your entire build but just on one or two layers that relate to them or not at all if your device is supported in mainline Uboot and kernel. The learning outcomes from that will be very beneficial to in the long term as embedded is complex [https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html](https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html) ---
**Author:** ![neuberfran](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/neuberfran/32/369_2.png) [@neuberfran](https://hub.mender.io/u/neuberfran)\ **Post date:** [August 17, 2020, 3:20am UTC](https://hub.mender.io/t/issues-with-systemd-networkd/2302/28 "2020-08-17T03:20:50Z")
@drewmoseley @dellgreen Now I can ping to 192.168.1.1. After change [Match] to [match]. I have issue in **ping 8.8.8.8** and **udhcpc -i eth0** > root@imx7d-pico:/etc# **networkctl** > IDX LINK TYPE OPERATIONAL SETUP > 1 lo loopback routable configured > 2 can0 n/a off pending > 3 can1 n/a off pending > 4 eth0 ether routable configuring > 5 sit0 sit routable configuring > 6 wlan0 wlan no-carrier configuring ![issue151](https://canada1.discourse-cdn.com/flex036/uploads/mender/original/1X/b715747eacbb11d3659368f36e401221882f1c16.png) ---
**Author:** ![dellgreen](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/dellgreen/32/85_2.png) [@dellgreen](https://hub.mender.io/u/dellgreen)\ **Post date:** [August 17, 2020, 7:57am UTC](https://hub.mender.io/t/issues-with-systemd-networkd/2302/29 "2020-08-17T07:57:40Z")
Changing Match to match is invalid, which means your network file apply to all interfaces. " A network file is said to match a network interface if all matches specified by the [Match] section are satisfied. When a network file does not contain valid settings in [Match] section, then the file will match all interfaces and **systemd-networkd** warns about that" ---
**Author:** ![neuberfran](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/neuberfran/32/369_2.png) [@neuberfran](https://hub.mender.io/u/neuberfran)\ **Post date:** [August 18, 2020, 12:12am UTC](https://hub.mender.io/t/issues-with-systemd-networkd/2302/30 "2020-08-18T00:12:20Z")
@dellgreen this link is very cool. I can wifi with Yocto 2.6-thud: [https://patchwork.kernel.org/patch/10066323/](https://patchwork.kernel.org/patch/10066323/) **But I need do three commands below, before restart** : wpa\_passphrase test 12345678 \> /etc/wpa\_supplicant.conf wpa\_supplicant -B -i wlan0 -c /etc/wpa\_supplicant.conf -D nl80211 & udhcpc -i wlan0 ![I can wirelessUhu](https://canada1.discourse-cdn.com/flex036/uploads/mender/original/1X/52e9cbb07700361a5c51d3987524c64116846cd0.png) ---
**Author:** ![neuberfran](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/neuberfran/32/369_2.png) [@neuberfran](https://hub.mender.io/u/neuberfran)\ **Post date:** [August 18, 2020, 2:47am UTC](https://hub.mender.io/t/issues-with-systemd-networkd/2302/31 "2020-08-18T02:47:52Z")
I need mii info in my u-boot Hit any key to stop autoboot: 0 =\> **mii info** Unknown command ‘mii’ - try ‘help’ [https://community.nxp.com/thread/453629](https://community.nxp.com/thread/453629) ---
**Author:** ![neuberfran](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/neuberfran/32/369_2.png) [@neuberfran](https://hub.mender.io/u/neuberfran)\ **Post date:** [October 4, 2020, 2:49am UTC](https://hub.mender.io/t/issues-with-systemd-networkd/2302/32 "2020-10-04T02:49:41Z")
mii info ![Screenshot_20200825-123137_Chrome](https://canada1.discourse-cdn.com/flex036/uploads/mender/original/1X/d0697ab1420627474900aa652ecad4f0ae9a8b67.jpeg) ---
**Author:** ![TheYoctoJester](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/theyoctojester/32/1444_2.png) [@TheYoctoJester](https://hub.mender.io/u/TheYoctoJester)\ **Post date:** [January 18, 2023, 3:11pm UTC](https://hub.mender.io/t/issues-with-systemd-networkd/2302/33 "2023-01-18T15:11:12Z")
A post was split to a new topic: [Systemd-networkd: static IP device not able to reach non-local addresses](https://hub.mender.io/t/systemd-networkd-static-ip-device-not-able-to-reach-non-local-addresses/5560) [Previous page](https://hub.mender.io/t/issues-with-systemd-networkd/2302.md?page=1)