OH YEAH!

MAC                IP              hostname       valid until         manufacturer        
===============================================================================================
00:13:20:fe:2f:1d  10.0.0.6        minnow         2020-06-17 12:31:46 -NA-                
00:1e:06:42:30:d0  10.0.0.4        odroid-buster6 2020-06-17 12:32:14 -NA-                
70:b3:d5:92:f2:e0  10.0.0.7        freedom-u540   2020-06-17 12:36:53 -NA-                
b8:27:eb:b9:81:e4  10.0.0.2        raspberrypi    2020-06-17 12:30:10 -NA-                
d0:31:10:ff:73:17  10.0.0.5        ci20           2020-06-17 12:32:59 -NA-    

Dev board setup update

Three of the five dev boards are now running – ARM64, ARM32, MIPS32. I built the SD card image for RISC-V yesterday and this morning (actually involves building an entire Linux distro!) but it looks like the power button on the SBC is broken so I can’t power the board up right now!

The Intel x86 (actual 32-bit only) SBC I tried powering up a few days ago but it didn’t play ball – that’s next to investigate, while I figure out what to do with the power button on the RISC-V.

Finally, my laptop is working (go figure 🙂 so x86_64 is working.

Green shoots!

Astoundingly, I have begun to make some progress bringing the dev board fleet back on its feet.

I bought a decent little ethernet hub ages ago, and now a few days ago a set of little U/FTP flat ethernet cables (I had some S/FTP which were way too inflexible, because about half the dev boards have their ethernet sockets one way up, the others the other way up), and I’ve hooked up all the cabling and – now the difficult bit – I need to bring each dev board back to life.

My first problem was getting an IP to the dev board. Setting up a static IP on a headless dev board is a huge pain in the ass, because although configuring /etc/interfaces is trivial turning off DHCP when you can’t boot the sdcard is problematic, far as I know.

In the end I finally understood why the recommended method to configure static IP is to use a DHCP server to do it – the boards can all be configured with DHCP, and then they’ll work if they go into a router or into a local subnet hanging off your laptop.

My setup is that my laptop runs a Tor proxy and blocks all outbound access except that through the proxy. So I run a DHCP server now, on the ethernet port, which hooks to the hub, and the five dev boards are plugged into that, the dev boards IP from the DHCP server, and they’re all configured to proxy via the Tor proxy on my machine – beautiful. Nice and secure – the dev boards don’t even *know* my public IP, let alone have an ability to access the internetwebs (except via Tor proxy, which is fine for apt, but wget didn’t want to work first time so I need to look at that).

That’s the plan anyway – and right now I’ve got almost all of it working for the old Raspberry Pi 3. I only need to set up the static DHCP address – everything else is fine.

There is an enormous cost to this though.

Only more modern apts can proxy via socks, so I needed to move from I think it was Jessie (it’s been a while!) to the latest, Buster (and, tragically, Raspbian is now called Raspios – those whom the Gods would destroy, first they make mad).

This means all the GCCs I built natively on the devices will no longer run, because the clib has changed. I spent many month building as many GCC versions as I could – and it could take days to build a single GCC.