Clearfog Pro 4.14.14 Network Manager fails

[Technicavolous]

I have Armbian 5.38 Debian Stretch Default running 4.4.115-mvebu and it is working fine. If I try to use either Debian or Ubuntu with the Next kernel (4.14.14) Network Manager always fails to start with a long wait (1 - 1.5 mins).

 

Both Debain and Ubuntu images behave the same with their respective kernels. (4.4 yes, 4.14 no)

 

Is this fixed in 4.15? Am I missing anything using the Default kernel? I've read in other posts where Igor and Mr Kaiser state the Next kernel is more 'mature.' I'm starting a fairly ambitious project with this board so I kinda want to make sure everything will run.

 

Thanks!!

[zador.blood.stained]

According to my tests this will be fixed in 4.16. Or it can be fixed right now by removing NM and using a different way for configuring networking (ifupdown, systemd-networkd)

 

Edit: Though I don't have the Pro model so not sure if DSA will still be an issue with NM.

[Technicavolous]

Thanks, I'll watch for this. I've started a fairly intense project (for me) with this board and the learning curve is amazing.

 

Is there anything we might be missing with a classroom apt-mirror, tftp boot server and caching webserver with this kernel? We've put a Marvell 4 port sata card and an ac wireless adapter on the mpci ports and intend to have a LOT of removable / permanent storage on this device so the classroom can operate without an internet connection.

 

Thanks again

[zador.blood.stained]

14 minutes ago, Technicavolous said:

Is there anything we might be missing with a classroom apt-mirror, tftp boot server and caching webserver with this kernel?

With this kernel - probably nothing, all mentioned protocols and services are handled by userspace so they should not depend on kernel features.

 

16 minutes ago, Technicavolous said:

intend to have a LOT of removable / permanent storage on this device

If by "removable storage" you mean USB storage then watch out for static discharges and overcurrents if anyone decides to plug in a USB HDD. Also a USB3 connector is not the most reliable thing to constantly plug connectors in and out so it's good to have a powered USB3 hub for external devices.

[Technicavolous]

When the project is completed the unit will be housed in a cabinet from circuit-specialists. Grounding will be thoroughly considered!

 

We will have a USB3 hub in the box, but most 'storage' will be SATA through this little baby and a four slot removable drivebay system. Also have an m.2 ssd through a small extender ribbon so it can be physically installed behind a removable panel for switchout if necessary. 

The two antenna version of this card shows as supported on the Armbian download page.

 

As long as that hardware is working we should be fine.

 

The point is to have as much SBCsupport in one box as possible so 'apt-get upgrade' doesn't take hours on a lousy classroom internet connection. We lose kids when things go too slow ...

[Technicavolous]

apt-get purge --auto-remove network-manager

worked a champ.

 

All the instructions I can find for manually setting up networking in Debian 9 require packages that I  can't find for arm - is there a package in the repo I can install via dpkg that would give me the necessary requirements? I've never set up networking manually ... if I'm missing something simple I apologize in advance.

 

We decided to go with the 4.4.115 kernel for now but I'm really wanting to learn how to set up networking on Armbian.

 

Thanks a bunch we're way ahead now!

[zador.blood.stained]

26 minutes ago, Technicavolous said:

All the instructions I can find for manually setting up networking in Debian 9 require packages that I  can't find for arm - is there a package in the repo I can install via dpkg that would give me the necessary requirements? I've never set up networking manually ... if I'm missing something simple I apologize in advance.

I don't think you need any additional packages. For configuring network in /etc/network/interfaces you need the "ifupdown" package (should be installed already), for systemd-networkd you also don't need to install anything but you need to activate several systemd units to make it work.

[Heisath]

You don't need additional packages (except ifupdown) for a manual network configuration.

 

Just edit /etc/network/interfaces, you can check here for reference https://wiki.debian.org/NetworkConfiguration
Or have a look at my config attached to this post.

 

Greets,

count-doku

 

 

# Bring up automatically: 
auto lo
auto eth0
auto eth1 lan1 lan2 lan3 lan4 lan5 lan6 br0

# Configure loopback interface
iface lo inet loopback

# Configure eth0, my outgoing public interface
allow-hotplug eth0
iface eth0 inet dhcp
        post-up iptables-restore < /etc/iptables.up.rules
        post-up ip6tables-restore < /etc/ip6tables.up.rules

# Bring up eth1 manual w/o ip config. This is neccessary to communicate with the switch / dsa
iface eth1 inet manual
#       address 169.254.100.100
#       netmask 255.255.255.255

# Do with the SFP Port whatever you want
iface eth2 inet manual

# Set all switched lan ports to manual
iface lan1 inet manual
iface lan2 inet manual
iface lan3 inet manual
iface lan4 inet manual
iface lan5 inet manual
iface lan6 inet manual

# Create bridge over all lanports and ip config them
iface br0 inet static
        bridge_ports lan1 lan2 lan3 lan4 lan5 lan6
                address 192.168.1.1
                netmask 255.255.255.0
                network 192.168.1.0
                broadcast 192.168.1.255

 

[Technicavolous]

This is turning out to be a better education anyway - thank you @zador.blood.stained for clarifying.  For some reason I'm compelled to use the newer kernel so I'm going to try this tonight.

 

@count-doku I have that link bookmarked but thanks a bunch for your example. Even with NM the switch ports have to be set up so that was a good reminder to go learn even more ;]