Hello everyone,

I am currently experiencing a network configuration problem.

This concerns a project based on an ODROID C2 board with a Linux Debian 9 stretch 5.73 / Kernel 3.16.57

the board is equipped with a USB 3.0 hub + RJ45 powered.

The ultimate goal is to have the WAN on eth0 in DHCP (odroid LAN)
an eth1 LAN in static (HUB LAN)
A wifi key RALINK RT5572 in access point with a static ip, hosting the bridge of the eth0 if necessary.

What works so far:
Everything is "ok" on boot, however it was necessary to disable some services at startup, and some behavior is strange:

Services disabled:

Wpasupplicant (disabled and hidden) otherwise impossible to pass the wifi key in MASTER
NetworkManager-wait-online (otherwise go round on boot and fail)

Installed services:
hostapd (for the access point)
dnsmaq
openvpn (not used yet)

My configuration is :

/etc/network/interfaces

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto wlan0
iface wlan0 inet static
        address 10.3.141.1
        network 10.3.141.0
        netmask 255.255.255.0
        #gateway 10.3.141.1

auto eth1
iface eth1 inet static
  address 10.240.77.10
  network 10.240.77.0
  netmask 255.255.0.0
  #gateway 10.240.77.1

hostapd.conf:

 

# Wi-Fi wlan interface
interface = wlan0

# nl80211 with all Linux drivers mac80211
driver = nl80211

# Name of the Wi-Fi spot
ssid = MonSSID

# Wi-Fi mode (a = IEEE 802.11a, b = IEEE 802.11b, g = IEEE 802.11g)
hw_mode = g

# frequency channel Wi-Fi (1-14)
channel = 6

# WPA
macaddr_acl = 0
auth_algs = 1
wpa = 2
wpa_passphrase = MonMDPSECRET
wpa_key_mgmt = WPA-PSK
wpa_pairwise = TKIP
rsn_pairwise = CCMP

has been uncommented: the hostapd default for the daemon's auto launch (the link to the hostapd.conf is good)

DNSMAQ (at the end of the file):

#CONFIG

interface = wlan0
domain-needed
bogus-priv
filterwin2k
 
locates-queries
Local = / lan /
domain = local.local
expand-hosts
no-negcache
resolv-file = / tmp / resolv.conf.auto
dhcp-authoritative
DHCP-leasefile = / tmp / dhcp.leases
 
# use / etc / ethers for static hosts; same format as --dhcp-host
# read-ethers
 
# DHCP range
dhcp-range = 10.3.141.10,10.3.141.100,12h
# Netmask
dhcp-option = 1,255.255.255.0
# Road
dhcp-option = 3,10.3.141.1

Network Manager is configured to handle interfaces in /etc/network/interfaces file (ifupdown = true)

reboot, interfaces eth0 and 1 jump up well, dhcp for 0 and static for 1. However, several things are strange:
 

- "Failed to start Raise network interfaces" (at the boot).
A systemctl status networking sends me a total fail of the service. That does not prevent networks from functioning.

- Random behavior of the Wlan0 interface. once on 4 or 5 reboot it is up but no IP address assigned. However, It always passes MASTER, sometimes it passes Manage first and then MASTER after a few seconds.

If necessary I bridge the net on the access point wlan0

I use for this the time to test this commands:

sysctl -w net.ipv4.ip_forward = 1
iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE

 

ip a returns me :

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 00:1e:06:35:69:57 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.56/24 brd 192.168.1.255 scope global dynamic eth0
       valid_lft 70201sec preferred_lft 70201sec
    inet6 fe80::21e:6ff:fe35:6957/64 scope link
       valid_lft forever preferred_lft forever
3: bond0: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noop state DOWN group default
    link/ether 1e:48:20:5a:68:17 brd ff:ff:ff:ff:ff:ff
4: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 00:0e:c6:ad:d7:66 brd ff:ff:ff:ff:ff:ff
    inet 10.240.77.10/16 brd 10.240.255.255 scope global eth1
       valid_lft forever preferred_lft forever
    inet6 fe80::20e:c6ff:fead:d766/64 scope link
       valid_lft forever preferred_lft forever
5: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 08:80:05:bb:11:04 brd ff:ff:ff:ff:ff:ff
    inet 10.3.141.1/16 brd 10.3.255.255 scope global wlan0
       valid_lft forever preferred_lft forever

systemctl status networking

 

● networking.service - Raise network interfaces
   Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Thu 2019-02-28 17:41:41 CET; 15h ago
     Docs: man:interfaces(5)
  Process: 324 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1/FAILURE)
  Process: 301 ExecStartPre=/bin/sh -c [ "$CONFIGURE_INTERFACES" != "no" ] && [ -n "$(ifquery --read-environment --list --exclude=lo)" ] && udevadm settle (code=exited, status=0/SUCCESS)
 Main PID: 324 (code=exited, status=1/FAILURE)

Feb 28 17:41:40 odroidc2 ifup[324]: RTNETLINK answers: File exists
Feb 28 17:41:40 odroidc2 ifup[324]: /etc/resolvconf/update.d/libc: Warning: /etc/resolv.conf is not a symbolic link to /etc/resolvconf/run/resolv.conf
Feb 28 17:41:40 odroidc2 dhclient[624]: bound to 192.168.1.56 -- renewal in 40936 seconds.
Feb 28 17:41:40 odroidc2 ifup[324]: bound to 192.168.1.56 -- renewal in 40936 seconds.
Feb 28 17:41:41 odroidc2 ifup[324]: RTNETLINK answers: File exists
Feb 28 17:41:41 odroidc2 ifup[324]: ifup: failed to bring up eth1
Feb 28 17:41:41 odroidc2 systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
Feb 28 17:41:41 odroidc2 systemd[1]: Failed to start Raise network interfaces.
Feb 28 17:41:41 odroidc2 systemd[1]: networking.service: Unit entered failed state.
Feb 28 17:41:41 odroidc2 systemd[1]: networking.service: Failed with result 'exit-code'.

Since the project node goes through this access point, how to make it reliable? and why these facts?

Thank for our feedback!

Edited March 4, 20197 yr by odroidodroid

Armbian is essentially a build system, that compiles u-boot, kernel and put it together with Debian or Ubuntu user space. We do sort some bugs on the way, but we don't change it much. If you use Debian based image, go to Debian forums or hire some Debian consultant https://www.debian.org/consultants/

 

Network settings are users problem and in case there is a bug in Network manager, systemd, dnsmasq or any other package ... you have to contact their authors/mail to Debian/Ubuntu bug lists. We don't maintain those packages.

If on-board network card is making problems, we will try to help, everything else is generic, the same as everywhere else.

Just a few hints. You are trying some strange mixture of three different networking suites: ifupdown, network-manager and systemd networking. Its hard and stupid to combine all three at once. If it is random behaviour then you have to double check services dependencies. It can be one of systemd problems.