Ethernet device with systemd-networkd on Yocto won't work (rejects ARP replies), but does work with /etc/network/interfaces #yocto #systemd
eliranl@...
Hi,
(since this is a long post, i divided it to sections) TL;DR I have a networking issue in my Yocto dist; Somehow, my ethernet device won't work with systemd-networkd, but will work with /etc/network/interfaces. It has an eth0 device which is configured (with a config file in /etc/systemd/network) with a static IP address. The Xavier's Ethernet port is connected directly to another Ubuntu PC, which is also on the same subnet with a different static IP address. I cannot get the Xavier's network device to work with systemd-networkd; Once the device boots into the initrd, it appears as if the network device is configured correctly:
However, when I ping the Ubuntu machine on the other end of the cable, there's no response.
20:00:55.280337 ARP, Request who-has 192.168.13.10 tell 192.168.13.6, length 46
(192.168.13.0 is the address of the machine i tried to ping. as you can see its MAC address is not updated).
Using /etc/network/interface does work If i 'move' to using /etc/network/interfaces by doing: 1. Running: systemctl stop systemd-networkd.{socket,service} 2. Write an equivalent configuration in /etc/network/interfaces 3. Restart eth0: ifconfig eth0 down; ifconfig eth0 up Then, all of a sudden the ping works.
And none of it seemed to work.
---- Does anyone have an idea on how to debug this? Please accept my apologies if this isn't the right forum, i wasn't sure where to sent it to. Thanks, Eliran
|
|
On Mon, Sep 14, 2020 at 11:31 AM eliranl via lists.yoctoproject.org
<eliranl=amazon.com@lists.yoctoproject.org> wrote: Which of the meta-tegra branches is it? thud-l4t-r32.3.1? It has an eth0 device which is configured (with a config file in /etc/systemd/network) with a static IP address. The Xavier's Ethernet port is connected directly to another Ubuntu PC, which is also on the same subnet with a different static IP address.[...] The following is the non-working systemd network device configuration file:There was an issue with NVIDIA's eqos driver in older BSPs. I know it affected the TX2, with the exact same symptoms It could affect Xavier modules as well. The workaround is to disable LLDP on by adding LLDP=no to the [Network] section for the interface. See https://github.com/OE4T/meta-tegra/issues/146 The workaround didn't get back-ported to the thud-l4t-r32.3.1 branch. [...] Please accept my apologies if this isn't the right forum, i wasn't sure where to sent it to.Since this is BSP-related, opening an issue at https://github.com/OE4T/meta-tegra/issues might work better. Regards -Matt
|
|
eliranl@...
Thanks Matt!! This solved it.
And yes, the branch is thud-l4t-r32.3.1.
|
|