I also use Mojave (latest release) and I have not had trouble connecting to Onion. Perhaps, though, there is an issue in a driver for a specific WiFi device that was released in Mojave 10.14.6. What macs do you have?

@Andrew-Walker Unfortunately I can't try / reproduce your problem now. I guess you should modify these sections of the 'wireless' file config wifi-device 'radio0' (???) and config wifi-iface 'sta'. If I were you I would read "every" wireless howto on OpenWrt - for example at least this one: Wireless Utilities Maybe this tutorial also helps you Connecting to School Wifi (MSCHAPv2 Auth Type) (As you know '/etc/config/wireless' changed after FW version v0.1.10 b160.)

@Alexey-Avdyukhin Confirmed ... Warp Core. WiFi works but pings are very high ... Omega2+ 0.1.10 b160 AP 192.168.3.1 ST 192.168.100.7 Omega2+ 0.1.10 b160 AP 192.168.5.1 ST 192.168.3.102 ping -c 600 192.168.3.1 --- 192.168.3.1 ping statistics --- 600 packets transmitted, 600 packets received, 0% packet loss round-trip min/avg/max = 0.768/1.966/18.315 ms Omega2+ 0.1.10 b160 AP 192.168.3.1 ST 192.168.100.7 Omega2+ 0.2.0 b188 AP 192.168.5.1 ST 192.168.3.101 ping -c 600 192.168.3.1 --- 192.168.3.1 ping statistics --- 600 packets transmitted, 586 packets received, 2% packet loss round-trip min/avg/max = 3.794/26.820/113.421 ms --- 192.168.3.1 ping statistics --- 600 packets transmitted, 590 packets received, 1 duplicates, 1% packet loss round-trip min/avg/max = 1.973/26.459/65.752 ms --- 192.168.3.1 ping statistics --- 600 packets transmitted, 585 packets received, 2% packet loss round-trip min/avg/max = 1.622/26.249/55.146 ms Omega2+ 0.1.10 b160 AP 192.168.3.1 ST 192.168.100.7 Omega2+ 0.2.0 b191 AP 192.168.5.1 ST 192.168.3.101 ping -c 600 192.168.3.1 --- 192.168.3.1 ping statistics --- 600 packets transmitted, 600 packets received, 0% packet loss round-trip min/avg/max = 1.445/19.812/121.962 ms --- 192.168.3.1 ping statistics --- 600 packets transmitted, 599 packets received, 0% packet loss round-trip min/avg/max = 1.454/27.444/54.659 ms --- 192.168.3.1 ping statistics --- 600 packets transmitted, 581 packets received, 1 duplicates, 3% packet loss round-trip min/avg/max = 2.904/27.380/106.859 ms Omega2+ 0.1.10 b160 AP 192.168.3.1 ST 192.168.100.7 Omega2+ 0.2.0 b192 AP 192.168.5.1 ST 192.168.3.101 ping -c 600 192.168.3.1 --- 192.168.3.1 ping statistics --- 600 packets transmitted, 600 packets received, 0% packet loss round-trip min/avg/max = 2.622/19.594/73.165 ms --- 192.168.3.1 ping statistics --- 600 packets transmitted, 597 packets received, 0% packet loss round-trip min/avg/max = 2.369/26.993/64.590 ms --- 192.168.3.1 ping statistics --- 600 packets transmitted, 600 packets received, 1 duplicates, 0% packet loss round-trip min/avg/max = 2.644/20.972/66.077 ms @Lazar-Demin I think more details are not necessary.

These two Docs articles would be the best place to start: https://docs.onion.io/omega2-docs/running-a-command-on-a-schedule.html https://docs.onion.io/omega2-docs/transferring-files.html - while this talks about transferring files TO the Omega, the same concepts with rsync and scp apply

Solved. Not exactly sure what fixed it, but after trying to connect again it gave me the option to skip, after spiking it connected to the Wi-Fi and downloaded & installed the firmware update. All working now.

@Ilya-Mordasov There is no Vdd25 pin in Omega2.

@Anthony-Kelly You might try unplugging the omega from the dock and putting a small piece of jumper wire between the receive and transmit connectors of the connector the omega sits in (just be careful to get those and not power lines - a 1k resistor would work too, and be more tolerant of mistakes). With the wire in place whatever you type in a serial terminal should echo back, without it the echo should stop. That would test the USB-serial distinctly from the Omega 2.

@Don-DeGregori said in Can't change Wi-Fi: Is there a better way to get to someone more direct? The chat only, if you have a technical question to a program you can try over github. fresh-desk seams to be a other platform. If you make a whois to onion.io then you see that they are behind a aws cloud and not more.

According to (and surely many other sources): https://en.wikipedia.org/wiki/Wi-Fi_Protected_Setup All WPS methods are vulnerable Laziness is a sorry excuse when your system is being hacked by criminals. What is recommended to this day is WPA2 (AES) encryption with a really complex passphrase (at least 20 characters+numbers long). And if you are not using the WiFi network, turn the feature OFF.

@Carlo-Oldani First step needed is grab the MAC address once this solved i think to be able to manage other aspect, but need help in catching address and data of signal, strenght and so on ... BR and thanks a lot for reading CArlo

Here is the explanation: https://community.onion.io/topic/341/access-point-mode-not-activated-when-failed-to-connect-to-wifi