Hi,

not sure if this problem is related to Armbian, but in my case it occurs only on an Armian system.
I have mainline kernel (4.7.x) running on a Banana Pro. wlan is configured as access point and works without any problems. eth0 is configured as client with static IP. The Banana is running 24/7, but the ethernet port is used only sporadically. The switch where eth0 is connected to is powered down most time. The problem is that eth0 forgets its IP configuration after a while, ifconfig then reports no IP address for eth0. I have to login via wlan and then ifdown/ifup eth0, then it works again. After a couple of hours (I dont know exactly how long), the IP is lost again. What is going wrong here?
 

Sorry, I forgot to mention two things.

 

First, a snippet from dmesg:

 

[146505.927251] sun7i-dwmac 1c50000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[158802.546876] sun7i-dwmac 1c50000.ethernet eth0: Link is Down
[231079.235691]  RX IPC Checksum Offload disabled
[231079.235726]  No MAC Management Counters available
[231578.280995] sun7i-dwmac 1c50000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
 

 

Second, this behavior did not occur with legacy kernel.

What about removing eth0 from /etc/network/interfaces and then as root

apt-get --no-install-recommends install network-manager
systemctl start network-manager
nmcli con add con-name Ethernet ifname eth0 type eth autoconnect yes ip4 192.168.1.101/24 gw4 192.168.1.1

You can then immediately change settings in an intuitive way using 'nmtui'. Network-manager should react on link state changes correctly otherwise what happens is non-deterministic (kernel dependant)

Thanks tkaiser,

 

I will try your suggestion. Can I be sure that network-manager does not interfere with the AP configuration of wlan0?

Can I be sure that network-manager does not interfere with the AP configuration of wlan0?

 

Network-manager doesn't touch any interfaces defined in /etc/network/interfaces or blacklisted in /etc/NetworkManager/NetworkManager.conf (unmanaged-devices=). Simply check using 'nmcli device show' and please report back.

Hm, there is no systemctl on my system. Did you mean sysctl?

But 'sudo sysctl start network-manager' reports

 

sysctl: cannot stat /proc/sys/start: No such file or directory
sysctl: cannot stat /proc/sys/network-manager: No such file or directory
 

Ok, I used 'sudo service start network-manager' and network-manager is up now.

 

However, 'nmcli con add con-name..' complains

 

Error: 'con' command 'add' is not valid.
 

Error: 'con' command 'add' is not valid.

 

Ok, you're using either Wheezy or Trusty (I'm testing only with Jessie or Xenial any more). Does setting up the Ethernet connection with 'nmtui' work?

nmtui is also not available here. I will find out how to install and then get back to you. Standby... :-)