On Mi, 25 mar 20, 18:52:25, Andrei POPESCU wrote: > On Mi, 25 mar 20, 12:21:49, Felix Miata wrote: > > Andrei POPESCU composed on 2020-03-25 17:45 (UTC+0200): > > > > > $ cat /proc/cmdline > > > ip=192.168.1.64::192.168.1.1::a64p:eth0:off root=LABEL=a64p rootwait rw rootflags=noatime > > > > > The interface is not even up after start and if I bring it up manually > > > with 'ip' it doesn't have any IPv4 address configured (only IPv6, which > > > is to be expected here). > > > > eth0 isn't kernel native any more, is it? > > It is on this device (PINE A64+). > > > Maybe add net.ifnames=0 and/or change 192.168.1.64 to 192.168.1.64/24? > > According to my understanding of the docs it must be an IP, the netmask > (if necessary) can be specified in the 4th field (already tried that). Apparently I have been using an older version of the docs (kernel is 5.4 from backports), the current one allows specifying also DNS and NTP servers. The updated command line looks like this: $ cat /proc/cmdline ip=192.168.1.64::192.168.1.1:255.255.255.0:a64p:eth0:off:192.168.1.1:: root=LABEL=a64p rootwait rw rootflags=noatime It still won't work and there's nothing in the logs, even with 'debug' on the kernel command line. As this was more of a curiosity than necessity I won't be pursuing it further, systemd-networkd is for me easier to configure. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser
Attachment:
signature.asc
Description: PGP signature