Yay! With the LEDE image, my Omega2+ connects to my Mikrotik router. Finally I can start developing on this months after receiving it.
onion.io devs: Please fix your wireless drivers so I can come back to your images. I shouldn't have to use the LEDE images just to get wifi out of the box. You've got a great product here but it's hindered by this problem.
Yay! With the LEDE image, my Omega2+ connects to my Mikrotik router. Finally I can start developing on this months after receiving it.
onion.io devs: Please fix your wireless drivers so I can come back to your images. I shouldn't have to use the LEDE images just to get wifi out of the box. You've got a great product here but it's hindered by this problem.
@zach-Van better way: ssh-keygen -R 192.168.3.1
@Jacob-Bendicksen Make sure you aren't using a cheap USB cable; the poorly made ones can have issues. Also make sure you power cycle the Omega2; I find that if I don't access the serial port soon after a cold boot, it 'goes away'.
ETA: I saw your other post; I'm on Sierra and I don't have any issues with it - try my suggestions above, also, you may find you need to be root in order to attach via screen.
@Martin-Wiedmeyer I tried both ways; one with wireshark itself and then one using the native wifi monitor and opening the resultant packet capture in wireshark to grab anything from the Omega. As far as I can tell it never tries to associate.
@WereCatf Tried this... no change.
@Martin-Wiedmeyer All I see when I do that are beacons from the Omega advertising the Omega-76EB network.
0_1487542455135_omega.pcapng
Either I am doing something wrong (possible, I don't use wireshark much) or the Omega isn't even trying.
(EDIT: references to 'jkl-omega' is the default network it brings up; I renamed the Omega-76EB network so my roomate wouldn't freak out about something new :D)
