Nanopi Neo 2 - network at boot / wait for network at boot -anyone else seeing this ?

HI,

I have the following

NanoPi Neo 2 boards, hardware v 1.1, model 1711 with 1Gb RAM

Linux 4.19.13-sunxi64 #5.70 SMP Sat Jan 12 17:41:57 CET 2019 aarch64 GNU/Linux

I have noticed that various network related tasks fail at boot apparently at eth0 is not yet ready

This includes network mounts via /etc/fstab and disabling IPv6 via /etc/sysctl.conf

My current solution (which I feel is a complete bodge) is to have extra commands in /etc/rc.local that after a 5 second sleep issue a 'mount -a' and 'sysclt -p'

I have tried solutions for 'wait for network' on boot but neither work.

systemctl enable NetworkManager-wait-online.service

systemctl enable systemd-networkd-wait-online.service

Looking at the armbianmonitor output I see this.

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000

link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

inet XXX.XXX.0.1/8 scope host lo

valid_lft forever preferred_lft forever

2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000

link/ether 02:01:43:0c:2e:f7 brd ff:ff:ff:ff:ff:ff

I have not edited the network config and /etc/network/interfaces is the standard

# Network is managed by Network manager
auto lo
iface lo inet loopback

IP address allocation is via DHCP, however these have pihole installed which I believe change this to static, albeit to match whatever they were getting via DHCP.

Is anyone else seeing this, have any thoughts or have a 'better' solution ?
 

edit: just spotted this at the bottom of the log

[    9.905128] RTL8211E Gigabit Ethernet 0.2:07: attached PHY driver [RTL8211E Gigabit Ethernet] (mii_bus:phy_addr=0.2:07, irq=POLL)
[    9.907509] dwmac-sun8i 1c30000.ethernet eth0: No Safety Features support found
[    9.907527] dwmac-sun8i 1c30000.ethernet eth0: No MAC Management Counters available
[    9.907535] dwmac-sun8i 1c30000.ethernet eth0: PTP not supported by HW
[    9.907998] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   15.011046] dwmac-sun8i 1c30000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[   15.011101] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   15.107488] FS-Cache: Loaded
[   15.176939] FS-Cache: Netfs 'cifs' registered for caching
[   15.177411] Key type cifs.spnego registered
[   15.177427] Key type cifs.idmap registered
[   15.178533] No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount.
[   15.611651] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[   15.648915] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[   15.655164] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[   15.655183] cfg80211: failed to load regulatory.db
[   20.150078] No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount.
 

It would be interesting to know what is happening between 9.907 and 15.01 where the network finally comes up.

I would guess that the CIFS mount at 15.17 is the OS reading fstab, which appears to fail, then the second mount at 20.15 is rc.local running mount -a but I'm not 100% sure.

I can't tell / don't know enough to see where in the boot sequence /etc/sysctl or /etc/fstab are invoked.