You are not alone. I have the same problem! Unable to figure out wifi connect
I am on Windows 10. I have the Omega2+ on a mini-dock. I have the same problem with each of my two Omega2+. Have tried serial command line as well as the browser method.
EDIT: So far I was able to get wifi going on one of the Omega2+ following this guide (even though I don't see how I could have had collision):
https://docs.onion.io/omega2-docs/fix-ip-addr-collisions.html#fix-ip-addr-collisions

@Brad-Buskey
to get the nice lines, use these putty settings (for windows at least):

@Pavils-Jurjans
node-red-install-tool_0.1-1_mipsel_24kc.ipk
repo is at http://repo.onion.io/omega2/packages/

@Lazar-Demin
Not essential, as long as I can be assured that simply unplugging or switching the Omega2+ off has no risk of file corruption

@cusackph
shutdown doesn't work either. How do we turn these things off?!

@Larry-Pinney
Thank you! I've gotten used to the raspberry pi where you can back up the entire bin "all at once" - not possible with the onion?

Could someone please share how one can back up the whole Omega2+ to a bin or img file? Thanks

@Kit-Bishop
I gave up and booted to failsafe and did a factory reset. Just doesn't seem worth the trouble. I figure I'll put this onion aside for awhile until and if the bugs get cleared up................
Thanks for helping and your time!

@Kit-Bishop
Again thanks for helping.

root@Omega-XXXX:/# block detect > ~/fstab-check
/bin/ash: can't create /root/fstab-check: Read-only file system

and pardon my ignorance, I'm used to seeing /bin/bash not bin/ash

@Kit-Bishop
Thanks for helping! Here is my /etc/config/fstab:

config global
        option anon_swap '0'
        option anon_mount '0'
        option auto_swap '1'
        option auto_mount '1'
        option delay_root '5'
        option check_fs '0'

config mount
        option target '/mnt/sda1'
        option uuid 'e74b8398-1f14-44cd-b25b-d7e11f87796a'
        option enabled '1'

and the file is "unwritable"

root@Omega-8735:/# root@Omega-8735:/# block detect > /etc/config/fstab
/bin/ash: can't create /etc/config/fstab: Read-only file system

@Kit-Bishop

Thanks for your info. I first formatted the USB drive as EXT4, then set up the swap, then extroot with pivot-overlay (I failed at first when I tried to install the overlay then the swap), and after installing nodejs and npm:

root@Omega-8735:/# node -v
v4.3.1
root@Omega-8735:/# npm -v
2.14.12
root@Omega-XXXX:/# free
             total       used       free     shared    buffers     cached
Mem:        125644      73296      52348        476       5804      44188
-/+ buffers/cache:      23304     102340
Swap:       524284          0     524284
root@Omega-XXXX:/# df -k
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/root                 5632      5632         0 100% /rom
tmpfs                    62820       476     62344   1% /tmp
/dev/mtdblock6           25664     18928      6736  74% /overlay
overlayfs:/overlay       25664     18928      6736  74% /
tmpfs                      512         0       512   0% /dev
/dev/sda1             14991780    585056  13625464   4% /mnt/sda1

Wow! However.... I keep getting the following error message in attempting to npm install modules:

npm ERR! nospc ENOSPC: no space left on device, open 'npm-debug.log.8946ac5ac8ea2c880858146fc2425020'
npm ERR! nospc This is most likely not a problem with npm itself
npm ERR! nospc and is related to insufficient space on your system.

How can this be with all that additional memory and space? Is another step required?