@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.
@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,
@JohnnyPicnic What terminal are you referring to you? Perhaps share which commands you are using and screenshot.
@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
@victoriano good information, thanks for posting. I kept my solution simple because of the controversy around enabling RSA.
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
@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.
@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.
@huntc If you use the build system you can include wireguard in your custom firmware build.
@huntc run modprobe wireguard to confirm the module is loaded. Check the logs using logread | grep wireguard to check for any errors, it should just report the module is loaded and the copyright.
Then use the wg command to configure as usual.
@teddylambert I am no expert on this, but if you check out the DTSi files in the build source and perhaps search the forums, I think you can default the pin registers using this method.
@jonione Have you tried cleaning the contacts on the SIM slot? A couple of years ago I spent weeks trying to diagnose an issue with SDCards not being recognised, or sometimes working and sometimes failing. Just before I reached for the Zanex I traced the issue to a little piece of matmus on one of the contacts.
@jasoneer For some reason I missed this question, but as a general rule force-depends is a good place to start but won't always work.
@vrinda-nair-0 From the Omega2S Data sheet:
https://github.com/OnionIoT/Omega2/raw/master/Documents/Omega2S Datasheet.pdf
2.5.6 Ethernet
The Omega2 has a single 10/100M Ethernet integrated PHY.
It is recommended that typical ethernet magnetics be used, however for very short runs (<5m) a
simpler approach using capacitive decoupling is possible. See the Omega2S reference schematic for
details.
@Antony The language you use is not relevant, you are simply writing to a file, I suspect your code returning an error writing to the file, what response codes is your code reporting for the file open and write functions?
@somnathavhad I was able to duplicate your issue, it appears there is a mismatch with node and npm. I took a new Omega2Pro out of the box. Run oupgrade so to be on the latest stable firmware. Next follow the document link I sent.
Now if you run the command "npm i" to get the npm information, this will tell you that you should upgrade npm to a new version. If I do upgrade npm then your error will occur, if I do not upgrade npm then npm has no error and can install the azure-iot-device-mqtt
From this I conclude you have installed an incompatible npm. I don't think you can upgrade node because Onion Team produced a custom version of node so it could work on Omega2.
@rajvigneshtn please run make again with -j 1 V=s. Parameters and post the log.
@somnathavhad if you re-run:
node --max_old_space_size=512 $(which npm) install azure-iot-device-mqtt
What is the output?
