Package: ifupdown
Version: 0.8.41
On Orange Pi Zero 3, when using ifup to configure the Ethernet adapter,
after doing a (soft) reboot, the interface is not present anymore. With
NetworkManager, this is not the case. It is a bug in the vendor kernel
build/driver for sure, just triggered by something "ifup" does. To debug
the issue, we run "ifup -v eth0" or "ifup -nv eth0" to print the actual
iproute2 commands performed and get something like this:
-------
ifup: configuring interface eth0=eth0 (inet)
/bin/run-parts --exit-on-error --verbose /etc/network/if-pre-up.d
/sbin/ip addr add 192.168.1.15/255.255.255.0 broadcast 192.168.1.255
dev eth0 label eth0
/sbin/ip link set dev eth0 up
/sbin/ip route add default via 192.168.1.1 dev eth0 onlink
/bin/run-parts --exit-on-error --verbose /etc/network/if-up.d
-------
When we run those exact commands manually, the interface does not
disappear on reboot. We tested this several times to rule out randomness
and tested with/without DHCP/static IP/gateway, and it can be
consistently replicated that the issue appears as fast as an IP address
is assigned by "ifup", but not by any of the "ip" commands run
"run-parts" (we removed all hooks to rule out issues with them as well),
but by something "ifup" additionally does.
So my question is whether someone has an idea what "ifup" does on top of
the commands printed by the "verbose" flag, which might bring the
adapter into a stage, that is not reset correctly on a soft reboot,
causing the driver to fail?
I hope I derived it correctly that there is no (external) ifupdown
project/source code, but that this is a Debian internal implementation?
Else, it would be great if you can give me a hint, so I can ask this at
the right place.
For reference: https://github.com/orangepi-xunlong/linux-orangepi/issues/54
Best regards,
Micha
