I have a similar problem with ifupdown on my home server which has
accumulated a rather unfortunate pile of crap...
I am not sure where the problem comes from. I suspect it might be
related to the initrd raising the interfaces before ifup actually runs,
and the RTNETLINK error is about the gateway already being set.
The workaround I found was to just flush the device before the setup:
iface eth0 inet static
# fix RTNETLINK errors on boot see https://bugs.debian.org/961508
pre-up ip addr flush dev eth0 || true
address 192.168.0.3
netmask 255.255.255.0
gateway 192.168.0.1
One might argue this should be the default and that ifup should clear
interfaces before bringing them up, but I'm not familiar enough with
ifup's intricacies to be certain.
Interestingly, I found this command on the raspi forum here:
https://raspberrypi.stackexchange.com/a/51947/32186
a.
--
To understand how any society functions you must understand the
relationship between the men and the women
- Angela Davis
