We see it scanned the SSID properly and you chose the WiFi-JYB8 ap so to confirm your security on the ap is indeed WPA2?
Is the password correct? CAPS LOCK on by chance? How is the WiFi setup? There could be so many things here that could be wrong but until you've ruled out the ones that you have control over; we can't help on the things you don't.
I have also seen, not on the Omega2's, where a 5ghz N Channel will get picked up by a scan but the 2.4ghz radio won't connect to it. It depends if the channel for 5ghz is locked or will downgrade for a 2.4ghz connection.
Again, many things that you can check and if you gave more info on what you've tried already; it would help. Just posting what you have with no real description doesn't help anyone.
Well, bad news, it broke again. After I rebooted the newly installed b162 running on the Ω2+, the orange light flashed slowly for a few seconds as if booting normally, then turned off. It didn't broadcast any SSID.
I then tried to put it on the small expansion board, same result.
Tried pressing the reset button while turning it on, same result, no light and no SSID.
@T-NT %This thread is now marked [Resolved]. You will have wider support if you start a new thread for your problem. About your questions - hardware support of 5.4Ghz band on Omegas would be news to me - haven't seen that yet. Why the 2.4Ghz wifi isn't appearing in the polling result - confirm that the wifi SSID isn't hidden or the protocol is TKIP-encrypted, as TKIP isn't currently "automatically supported" as posted by Onion here.
Hi to all. A had the same problem, but change the router password and set only alpha numeric password (without expecual characters) and the connection work. I don't know how but I expend a Lot of time trying to connect. i made a lot of test on the router (CISCO Linksys Smart WIFI EA2700) change bandwidth, wifi type, channels and does'nt work. The last test was change the password and works.
@Chris-Stratton I did briefly flash the newest official firmware earlier today and it did the same thing, ie. showing up as Omega-0000. The MAC-address is fine when I use my own image. So no, it's not the mtd2-partition that's messed up, it's in the firmware-image that the bug is in.