@Jim-W That's good news. There could be several reasons discovery is failing, also be careful with setting a specific channel in case your router switches it on you. Channel 6 doesn't overlap with other channels, so if your router is permitting connection on multiple channels it may be that your Omega2 is connecting on a noisy channel and therefore it fails to connect reliably. Depending on your region and the region your router is designed for, the channels vary.
Group Details Private
Global Moderators
Forum wide moderators
Member List
-
RE: Omega2 not completing startup
-
RE: Omega2 not completing startup
@Jim-W Omega2 uses 2.4ghz so you need to ensure your wifi support 2.4. Next you need to ensure your wifi is broadcasting on standard channels. Check /etc/config/wireless for your configuration, also users have had issues with US configuration, here is the standard config:
config wifi-device 'radio0'
option type 'ralink'
option variant 'mt7628'
option country 'US'
option hwmode '11g'
option htmode 'HT40'
option channel 'auto'
option disabled '0'
option device_mode 'apsta'
option op_mode 'preference'Usual issues maybe you need to set the channel to the specific channel of your wifi router, or comment out "option country US"
Try those and report back your results,
-
RE: LTE connection cannot load Terminal
@JohnnyPicnic What terminal are you referring to you? Perhaps share which commands you are using and screenshot.
-
RE: Change port of OnionOS webserver
@JohnnyPicnic The issue is that the OnionOS uses UBUS to log you in but the javascript used on the pages does not refer to the configured port. So while the web server is serving pages on the port you configured, the javascript is assuming ubus is on the standard port 80. The solution would be to edit the javascript which in /www
-
RE: Ubuntu 22 SSH Error
@victoriano good information, thanks for posting. I kept my solution simple because of the controversy around enabling RSA.
-
Ubuntu 22 SSH Error
The release of Ubuntu 22.04 LTS includes an update to OpenSSH which disabled support for shh-rsa algorithm. Attempting to ssh into Omega2 device from Ubuntu 22.04 system reports:
"Unable to negotiate with <insert Omega2 ip> port 22: no matching host key type found. Their offer: ssh-rsa"
The simple solution is to specify the algorithm on the ssh command line like so:
ssh -o HostKeyAlgorithms=ssh-rsa root@192.168.1.199
or
scp -o HostKeyAlgorithms=ssh-rsa <some file> root@192.168.1.199:/<some directory>
The algorithm can be re-enabled on Ubuntu 22.04 but is disabled by default due to a long-known compromise. Please refer to OpenSSH documentation for further information
-
RE: Set pin mode at boot
@ChMsT420 @Lazar-Demin The only issue with using rc.local is that it runs last so if you have a daemon or loadable module that is dependent on the pin mode, rc.local might be too late.
Another alternative is to use a hotplug script that is triggered earlier in the boot process. Take a look in /etc/hotplug.d for some examples of these scripts, also hotplug is quite well documented.
-
RE: Installing wireguard requires kernel dependencies to be ignored
@huntc I think that any of us who use Omega2 for commercial purposes end up building our own firmware so we can tweak it to our specific needs.
-
RE: Installing wireguard requires kernel dependencies to be ignored
@huntc If you use the build system you can include wireguard in your custom firmware build.