(10-14-2017, 03:29 AM)skipper Wrote: Running:
https://github.com/ayufan-rock64/linux-build/releases/download/0.5.15/stretch-minimal-rock64-0.5.15-136-arm64.img.xz

Controlling the rock64 via Putty - SSH

When first connecting:
apt update
apt upgrade
Then I change /etc/hostname and in /etc/hosts I add my fixed public IP with the hostname from /etc/hostname.

I then do:
apt remove --purge network-manager
make sure resolvconf is not installed
then:
rm /etc/resolv.conf
then make a new resolv.conf:
nano resolv.conf adding my 2 nameservers IP addresses and save.

then (I want to have complete control of the IP of the rock64 with no odd interference from other files/scripts that I don't know about):
systemctl disable dhcpcd
systemctl enable networking (in order to get back to the "oldfashioned way")

then:
nano /etc/network/interfaces.d/eth0 (I use only the wired rock64 LAN port)
I enter:

allow-hotplug eth0
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet static
     address XX.XX.XX.XX
     netmask XXX.XXX.XXX.XXX
     gateway XX.XX.XX.XX
     
The IP addr and mask are not on the same network as my local network.
It is created as a 2nd static IPv4 route on the router (fritzbox 7490) with 5 fixed IP addresses. I am not able to add the external IP and MAC as it is not on the same network as the fritzbox.

I then reboot the rock64.
When looking at the network connections tab in the fritzbox I don't see the rock64 (with it's new hostname and external IP) - tried several reboots of the rock64 and the router.

FYI when I do all this from a Rpi, Bpi, odroid or olimex I always see each of them on the fritzbox, with their hostname and external IP.

What can/could cause the missing fritzbox entry from the rock64?
It puzzles me and is annoying, as I need to create port permissions for the rock64 through the fritzbox from outside.

(10-15-2017, 11:48 PM)skipper Wrote: Howdy good folks,

After having messed with this issue for days (having pulled several of my grey hair out) - I started to look for other reasons than the rock64 itself, and started to look at my intranet environment.
I have several switches on it, so I decided to be "tough" on them, by switching off everything from the router to all switches. The switches I took 1-by-1 and reset them to factory defaults.
Router on again, then switches online again, one after the other.
After several reboots of the rock64's they finally showed up on the LAN as supposed, with the IP addresses I had given them.
So, I'm happy to report that everything works.
If someone else should encounter similar issue, I just want this post to be a hint of looking outside the SDB. But I think most of you guys would have already done this