I applied the latest update, per your instructions, then decided I'd set up my SD Card per:
For some reason, while the "block detect" command did come up with a useful output, I couldn't redirect that output to /etc/config/fstab - So I did it manually!
However, despite working through all of that, on reboot the Omega 2+ I have doesn't remember there was an SD card in the slot! I have to eject the SD Card, and reinsert it, and then the OS sees it.
Which means that I can't boot from it....
Which leads to the other problem I've been having... 
The moment I join it to my wifi, I can't connect via SSH any more, either to the 192.168.3.1 address, OR the IP allocated by the wifi network.
To clarify, this is what I see when I use a web browser to try and get to the console:
I messed up my network too badly to try and fix it, so I did a hard reset...
Index of /console/
../
modified: Tue, 31 Jan 2017 14:54:38 GMT
directory - 0.00 kbyte
lib/
modified: Tue, 31 Jan 2017 14:54:39 GMT
directory - 0.00 kbyte
How do I fix this, please?
I have the Ethernet expansion, and since I'm not using a wifi enabled laptop (I have a desktop that's hard wired!) I don't have an easy way to connect to my Omega2.
I, ideally, want to connect it to my LAN, via the ethernet interface. However, because there's a Wifi AP built in, I'm aware there must be a DHCP daemon running.
So, before I upset my network administrator, I need to ensure that the DHCP server doesn't respond to requests on the Ethernet port. It's fine if it continues to respond on the Wifi side, when it's acting as an AP... but I can't take a risk of damaging our network, if the DHCP server is still enabled.
Can anyone point me somewhere to do this easily? Command line doesn't bother me, and I know SSH to it is working fine.
Thank you!