Posts made by crispyoz

@Pavel-Negrobov please post the JSON response for the restart command. If it is returning 0 ie success, instead send network stop, pause 10 seconds, then send network start. I have seen similar issue on non-omega device where connection is maintained despite network restart when connecting to Netgear router.

@Radek I think we all appreciate your passion and we look forward to your future contributions.

@Pavel-Negrobov I'm not clear on what you mean by connect/disconnect to AP. Are you referring to bring up the interface and bring it down? Or are you referring to connecting to a new AP and adding it to your network wireless setup?

I'll assume you want to connect to a new WiFi AP you selected from the results of the iwinfo scan. UBUS gives you access to the UCI configuration functionality and we can use UCI to update the wireless configuration to add a new AP configuration. You can see the configuration file in /etc/config/wireless.

To use UBUS you would send a JSON request as follows, to add a new wifi configuration section to the wireless config file, note that the first parameter is your ubus_rpc_session you received when you executed the login request from my previous comments. Notice we are calling UCI instead of iwinfo now:

{
"jsonrpc": "2.0",
"id": 1,
"method": "call",
"params": ["c47f70c98fe4a145288d214ce12214fb", "uci", "add", {
"config": "wireless",
"type": "wifi-config"
}]
}

Next we need to add the AP details to the section:

{
"jsonrpc": "2.0",
"id": 1,
"method": "call",
"params": ["c47f70c98fe4a145288d214ce12214fb", "uci", "set", {
"config": "wireless",
"type": "wifi-config",
"values": {
"key": "eac0cc123d3f81e39a4e48d9da",
"ssid": "MY-NETWORK-SSID",
"encryption": "psk2"
}
}]
}

Then you send a commit to tell UCI to save these changes:

{
"jsonrpc": "2.0",
"id": 1,
"method": "call",
"params": ["c47f70c98fe4a145288d214ce12214fb", "uci", "commit", {
"config": "wireless"
}]
}

Now look at your /etc/config/wireless and you will see the new entries.

You will need to either restart the network to make this have effect, or you can reboot. Here is the reboot JSON:

{
"jsonrpc": "2.0",
"id": 1,
"method": "call",
"params": ["c47f70c98fe4a145288d214ce12214fb", "system", "reboot", {}]
}

You will see this time we are not using iwinfo nor uci, we are using "system". This is the great thing about utilising the ubus system, you can interact with many areas of OpenWrt in a consistent manner. You just need to get your head around the ubus JSON requirements.

You can also secure ubus by adding new users that can be given limited access to ubus functionality.

@Radek it is a breach of the terms of use. I edited it out rather than apply any penalty.

@Radek Do you mean you want to install OpenWrt under Docker? Or you want to install Docker on OpenWrt?

@Pavel-Negrobov Omega OOTB uses uhttpd, the /ubus context is provided by the ubus uhttpd plugin.

Make sure you have the latest firmware installed and installed uhttpd-mod-ubus

Great stuff @Lazar-Demin can we put that in the FAQ?

This how you would login using curl:

curl -d '{ "jsonrpc":"2.0", "id":1, "method": "call", "params": [ "00000000000000000000000000000000", "session", "login", { "username":"root", "password":"onioneer" } ] }' http://192.168.1.126/ubus

The response would be like this:

{
"jsonrpc": "2.0",
"id": 1,
"result": [0, {
"ubus_rpc_session": "aaea539f7d0f5d5a14fe6067caefc78f",
"timeout": 300,
"expires": 299,
etc etc etc

You use the ubus_rpc_session value in your next request to scan for wifi

curl -d '{ "jsonrpc": "2.0", "id": 1, "method": "call", "params": ["aaea539f7d0f5d5a14fe6067caefc78f", "iwinfo", "scan", { "device": "apcli0" }] }' http://192.168.1.126/ubus

@Pavel-Negrobov In my opinion ubus is your best option however rather than using the command line you can use JSON request/response which will provide you a response code and any applicable error message. Using this method you can code in C/C++/Python or use it in PHP etc.

This a sample JSON to scan for available wifi:

{
"jsonrpc": "2.0",
"id": 1,
"method": "call",
"params": ["27c3cfb79f367b6ab2a8e46dd6049788", "iwinfo", "scan", {
"device": "apcli0"
}]
}

@IOTrav Take a look at this thread, Lazar points the user to a thread on the OpenWrt forum which may assist you.

https://community.onion.io/topic/3709/making-ethernet-as-primary-connectivity/12?_=1593441015731

@Nagarjuna-Reddy It seems like it is not being detected which I suspect it needs a kmod to detect it. Do you see the device identified in the console when booting? Can you post the log and details of the flash, part # etc so we can see exactly what it is and what kmod it may require. I recall kmod_spi_mmc (off the top of my head) is required for one of my boards.

@Marko-Lukat This seems like classic buffer overrun behaviour which would make sense since you're feeding the terminal at double the rate.

@Radek I updated the code to set baud rate to 9600, you can see if it works or not, I can't test as I don't have an LTE device.

I built it for you to try, you can find the binary here:

https://github.com/crispyoz/ogps.git

@Radek @Marko-Lukat From the code we can see the device is opened at 4800:

if (nmea_open(device, &stream, B4800) < 0)

I'm not sure why this is the case.

@Nagarjuna-Reddy If the memory is functioning it should be visible as a device, and typically would be mounted. Please post the out put of these commands:

df -hT
mount

@CoffeeCat here is distfeeds.conf you can compare with yours, if it still does not work please post the output of opkg update. You don't ned python installed to install this package it doesn't have a python dependency.

You can see what packages are available using opkg list

@CoffeeCat did you run opkg update? Unless you do so opkg won't check the uncommented repository. The package is still available I installed it a moment ago on a new device.

@Suman-kumar-Jha I think by now you should know that you need to provide. It is exhausting continually asking for the most basic of details.

1. Firmware version
2. The log of the error

@liamski I can't answer for the technical reason, only my experiences with high temperatures and Omega2S+ (and Pro). However a few decades ago when we were building custom PCs for some high traffic security software we would regularly overclocking CPUs. A pattern quite clearly developed that the maximum clock speed varied quite significantly between batches of SIMM modules. In fact OS/2 (if anyone remembers that) was quite unreliable if you used SIMM modules from different batches. So your experience is not that surprising to me.

I think it has something to do with gravity or sun spots or maybe a combination of the two.

@CoffeeCat edit /etc/opkg/distfeeds.conf. Remove the # from lines 2 and 5, then run opkg update, then run opkg install python3-adc-exp