f-log

Raspberry Pi 3 HiRes
(past half way)

[X]Board in Blender
-[X]Measure board
-[X]Model
-[X]Texture
-[X]Components on the bottom
-[ ]Components on the top
--[X]GPIO pins
--[X]Camera connector
--[X]Display connector (identical to the camera connector)
--[X]Broadcom chip
--[X]Other chip (networking and USB, I think)
--[X]USB power connector
--[X]HDMI connector
--[X]Headphone jack
--[ ]Ethernet connector
--[ ]USB connector pair x2 (making four)
--[ ]Micro components, like capacitors (loads of these)

The HDMI connector is a plane with Mirror and Solidify modifiers. I also used the Knife tool to create the geometry allowing the holes, rather than using booleans that can ruin the topology.
The Audio connector is much more a hodge podge of what worked. With Boolean modifiers for the tubes, Solidify modifiers for any panels and Mirror used where ever possible.

Added DoF(Deep of Field) for this pic. F-stop = 1.0 and F-stop = 1.0, not sure why you have to do it twice.

We have a Netgear WNR2200 that has operated flawless for many years ,but about a month ago it start going a bit wobbly.

I have to use the word "wobbly" because there is no access to any logs and it did not consistently fail in any one way.

The Wifi would drop, the web interface would say nothing was wrong and restarting the router fixed the problem. This only happened a couple of times and I upgraded the Firmware but then it happened couple of more times.

Then it would drop Internet and sometimes to only certain devices. So the Now TV box would be happily streaming from the internet but a PC or phone would lose connectivity, sometimes losing Wifi completely.

It was decided that the WNR2200 was a bit long in the tooth and had been bought cheap. I started looking at commercial offerings and came across Ubiquiti and after some careful consideration bought a Unifi AP AC Pro.

It came with no cables but a PoE(Power over Ethernet) injector. I rustled up some CAT5 and plugged in the injector and my switch and then into the Unifi AP(Access Point) unit. Happily it just powered up after a tense few seconds.

Downloaded the Unifi app from the Google Play store and it immediately found the AP asked for a username and password and I was able to, from the app, setup a basic WPA2 Wifi access point. It just worked!

But I wanted to the setup a guest network and generally poke around a bit. First I found I could ssh into the box directly COOL! Sadly there is not much there. I needed to install the "controller".

I have my LUbunut VM for web browsing so I thought I could use it as a guinea pig.

Downloaded .deb file from for linux
https://www.ubnt.com/download/unifi/

Installed with
sudo apt-get install ./unifi_sysvinit_all.deb
Which installed all the dependencies including Java 8-openjdk and skips a whole load of setting up sources and keys that was required in the past.

To run the service I tried
sudo /etc/init.d/unifi start
but always failed and nothing in the logs :(
/var/log/unifi/server.log

Finally found the command was
sudo service unifi start

Connected with firefox to localhost:8443
gave me a few Unicode characters but nothing else so I tried
localhost:8080
that then redirected to
https://localhost:8443/manage/wizard/
But
No Devices Found

Drat, I had checked that although the VM was on a different separate sub-net it could ping the AP, so I know it can work ...

Ah, I can just click Next and Skip ...

and eventually I get the nice, but empty, dashboard and whatever I do I get
No Devices Found

Seems the Controller cannot create connections to AP units but must wait for them to try and talk to it. This will not work very well with a VM in VirtualBox unless I manually setup all the ports to forward...

Sound painful, but there might be something else I can do.

No maybe this is the only way and serves me right from trying to run a controller from a VM ;)

Luckily I found https://www.stevejenkins.com/blog/2016/05/diy-cloud-hosting-ubiquiti-ubnt-unifi-controller/ blog post detailing the ports required.

What? You can run a Controller on a Raspberry Pi Intriguing!