Not a sausage?

So, I reburnt the SD with the distro.

I gave up on nmcli/nmtui and I went back to the good ole /etc/network/interfaces edit, or at least I created:


Set the contents to:

auto eth0
allow-hotplug eth0
iface eth0 inet static
dns-nameservers …

When I set up I now happily get:

root@OrangePizero:~# ip addr show
2: eth0: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether f6:78:ae:aa:0a:d8 brd ff:ff:ff:ff:ff:ff
inet brd scope global eth0
inet6 fe80::f478:aeff:feaa:ad8/64 scope link
valid_lft forever preferred_lft forever

So, board seems to setup the eth0 as I want it to.

However, my network simply does not see the board.

I have a bag of short ethernet jumpers from aliexpress … hmmmm … nope.  I swap a few out so unless they have sent me a dozen dud ethernet cables it isn’t the ethernet cable.

So, it looks like the problem might have been that I had the following

auto eth0
allow-hotplug eth0
iface eth0 inet static

I commented out the hotplug line, rebooted then voila!  My OPiZ was “seen” on my local lan again.

But …

… still can’t get out to the world???

Well, apt-get doesn’t resolve.  A ping to fails.  A ping to succeeds ???

root@OrangePizero:~# route -n
Kernel IP routing table

Destination Gateway Genmask Flags Metric Ref Use Iface UG 0 0 0 eth0 UG 1024 0 0 eth0 U 0 0 0 eth0

So, why am I not getting out?

root@OrangePizero:~# ifconfig eth0
eth0 Link encap:Ethernet HWaddr f6:78:ae:aa:0a:d8
inet addr: Bcast: Mask:
inet6 addr: fe80::f478:aeff:feaa:ad8/64 Scope:Link
RX packets:1559 errors:0 dropped:172 overruns:0 frame:0
TX packets:489 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:246564 (240.7 KiB) TX bytes:37710 (36.8 KiB)

So, I note I can ping from my PC and I can ping the OPiZ from my PC.

I can ping my PC from my OPiZ.

Ah ha.


is set to:

#the following is set by network manager

So, that won’t work on my network given the ISP router provides two nameserver addresses before you would bother with the free nameservers. Not to mention my gateway is and so the dns requests were getting nowhere.

So I manually set up resolve.conf to two name servers given by my ISP and the two free ones (to be sure, to be sure).

Happily now pinging

I have run apt-get update again.

Ready to start all over again … again.

All this as the node-red was running fine but the network went kaput on the OPiZ somewhere in the middle of the emqttd install.

I can’t put my finger on when during the emqttd install, but there were all the problems with wget and then I did twiddle with certificates. However, why on earth would that blow away my network configuration???

No useful hypothesis as yet so I will check regularly during the emqttd install steps if see if/when the connection breaks.

I also installed a watchdog node into node-red and set up a 10 minute timer to reboot the OPiZ to stress it.  If it is up on Sunday after all those reboots we can likely discount the node-red and I guess the npm as the culprits.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: