Any visible wifi network is bound to get attacks and WPA/2 crack attacks, which is an attack vector into your home or office network. Especially since OpenWRT is set up by default as an access point, which forwards traffic to the wwan network, i.e. your main network.
I've set up firewall rules for the VLAN my iot devices are on, but still, less than optimal.
Would you rather have an extra door or a solid wall in your bank vault?
Cheers.
@crispyoz Oh wow. I have not even seriously looked into that issue, first-things-first, so to speak.
I did notice nothing worked when I simply tried to remove the 'ap', or set the mode option to 'sta' instead of 'apsta'.
Thanks for the enlightenment. There are already 40 access points visible on my laptop, so I will just need to think of a funny name.
A Raspberry-Pi Zero is also starting to look more and more enticing for this project, but alas, I bought three of these Onion Omega2s and they should be put to good use.
@crispyoz
In that I respectfully disagree, as it is a default value for only 5% of the world's population. Furthermore, it is only documented for people well versed in OpenWRT setups, which is not the target audience of this 'user friendly' device, and the feature is completely undocumented on Onion's website. So I would call that a defect.
If they spent 10% of the money on the beautiful packaging on proper testing, we might not have had this issue.
Just my $0.02 opinion.
Also just installed haveged, thanks, but I don't know if the better random generator will help here.
OMG, this worked! I have been working on this for days. Tried your 'remove option US' all the time, but the devil is in the details.
I connected using the ethernet dock, as the AP wifi would disconnect every 30 seconds.
My steps
firstboot -ysyncrebootreboot, againwifisetup add -ssid MyNetwork -encr WPA2 -password MyPasswordwifisetup list shows a disabled network)wifisetup add -ssid MySecond -encr WPA2 -password MyPasswordwifisetup list shows the first network enabled)ifconfig shows the Omega connected to apcli0, eth0 and br-wlan!Even better: my UniFi AP-AC-LR router shows the Omega in its client list.
Hurray!
This was all on BusyBox v1.28.3 () built-in shell (ash), with Ω-ware: 0.3.2 b230
Disconnected the ethernet cable and reset the Omega, and it keeps connecting to the wifi. Incredible.
Now I just want to know how I can safely remove the default Access Point (ap) network, as that is a big security issue? Nothing about that in the Onion documentation of course...
@crispyoz Thank you for this tech insight.
I do wonder with @Stephen-Tunney why no-one from Onion is remotely looking and solving this issue, after TWO years!
Luckily I have an ethernet dock, otherwise I would go bonkers.
@crispyoz Thanks for the tip to turn off Automatically Optimize Network. I will try that.
However, it took me 10 minute to find the setting. For future reference: it is in the top "Site" tab, not any of the 30 other pages in the 'Settings'.
@Stephen-Tunney Ah! A fellow Ubiquity networks user. I have been getting grey hairs trying to get my Onion Omega2 to connect to my Unify Ap-AC-Lite and Pro. Latests firmwares on APs.
Tried Omega2 firmware 0.2.2 and 0.3.2 to no avail.
The Omegas can scan the network fine, but they simply will never-ever connect to it. Unify logs show no trials whatsoever, neither is my DHCP server.
Good to know there is at least some --very old-- firmware which works.
What else I did: tried to connect the Omega2 to an ssid on an Fritzbox router, very widely used in Germany: Nothing as well.
I will try @Ganescu-Theodor 's suggestion next (have already disabled the US option, but perhaps I should do it directly after 'firstboot -y'