Posts made by Lazar Demin

@crispyoz We're open to suggestions on this, what kind of approach would you prefer?

The existing firewall on the OS can be used to enable/disable network traffic from specific interfaces

Taking a look at /etc/config/firewall, you'll notice it has zones that control traffic flow of the network interfaces defined in /etc/config/firewall

By default, the wan firewall zone is attached to the wwan network interface.

Looking at /etc/config/network you'll see that the wwan network interface is apcli0, the Omega's WiFi client interface

We can change the wan firewall zone configuration to enable or disable traffic through this interface.

To start, my Omega is connected to WiFi and can ping the internet:

root@Omega-F195:/# ping www.google.com
PING www.google.com (172.217.164.196): 56 data bytes
64 bytes from 172.217.164.196: seq=0 ttl=115 time=18.968 ms
64 bytes from 172.217.164.196: seq=1 ttl=115 time=22.639 ms
...

Then, I'll run these commands to REJECT input and output traffic for the wan zone:

uci set firewall.@zone[1].output='REJECT'
uci set firewall.@zone[1].input='REJECT'
uci commit firewall

Note: these changes can also be made by modifying the /etc/config/firewall file directly

And restart the firewall:

/etc/init.d/firewall restart

I can no longer access the internet. The WiFi client interface is still associated with the network, but no traffic can go through:

root@Omega-F195:/# ping www.google.com
PING www.google.com (172.217.164.196): 56 data bytes
ping: sendto: Operation not permitted
root@Omega-F195:/# ping www.google.com
PING www.google.com (172.217.164.196): 56 data bytes
ping: sendto: Operation not permitted

A few notes:

1. The default firewall configuration only has zones for the WiFi AP and WiFi Client network interfaces. You'll need to add more zones to the firewall to control the ethernet network interface, or other network interfaces like cellular modems.
2. The firewall also supports creating Rules. For a deeper dive into the firewall and rules, take a look at the openwrt firewall documentation: https://openwrt.org/docs/guide-user/firewall/firewall_configuration

@IOTrav @crispyoz Spent a little time experimenting and found the existing firewall on the OS can be used to enable/disable network traffic from specific interfaces

Taking a look at /etc/config/firewall, you'll notice it has zones that control traffic flow of the network interfaces defined in /etc/config/firewall

By default, the wan firewall zone is attached to the wwan network interface.

Looking at /etc/config/network you'll see that the wwan network interface is apcli0, the Omega's WiFi client interface

We can change the wan firewall zone configuration to enable or disable traffic through this interface.

To start, my Omega is connected to WiFi and can ping the internet:

root@Omega-F195:/# ping www.google.com
PING www.google.com (172.217.164.196): 56 data bytes
64 bytes from 172.217.164.196: seq=0 ttl=115 time=18.968 ms
64 bytes from 172.217.164.196: seq=1 ttl=115 time=22.639 ms
...

Then, I'll run these commands to REJECT input and output traffic for the wan zone:

uci set firewall.@zone[1].output='REJECT'
uci set firewall.@zone[1].input='REJECT'
uci commit firewall

Note: these changes can also be made by modifying the /etc/config/firewall file directly

And restart the firewall:

/etc/init.d/firewall restart

I can no longer access the internet. The WiFi client interface is still associated with the network, but no traffic can go through:

root@Omega-F195:/# ping www.google.com
PING www.google.com (172.217.164.196): 56 data bytes
ping: sendto: Operation not permitted
root@Omega-F195:/# ping www.google.com
PING www.google.com (172.217.164.196): 56 data bytes
ping: sendto: Operation not permitted

A few notes for your application @IOTrav :

1. You'll need to add more zones to the firewall to control the ethernet and cellular network interfaces. But after that, you can programmatically control which interfaces act as the main connection to the internet
2. Adjusting the zones manually may or may not be the best way of achieving what you're looking for. The firewall also supports creating Rules but I'm not too familiar with how they work. For a deeper dive into the firewall and rules, I suggest taking a look at the openwrt firewall documentation: https://openwrt.org/docs/guide-user/firewall/firewall_configuration

@lzapata pls try to make your topic title more descriptive in the future

Our mistake! We were cleaning up our GitHub repos and removed this one by accident.
It's back now and compiles should work fine.

@Martin-Vana No need to modify feeds.
From my experience make kernel_menuconfig sets up how kernel modules should be treated - whether they should be built-in to the kernel, or can be loaded as kernel modules.

Once you've done your configuration in make kernel_menuconfig, you'll need to enable the kernel module for compilation in make menuconfig.

Then run make, and you'll get an ipk.

PRs have been merged! Thanks for contributing!

How to update your Omega2 LTE

Option 1: Update a Software Package

To get the updates, you can update just the omega2-lte-base package to install the latest 1.0.2 version. Make sure you're connected to the internet and run:

opkg update
opkg upgrade omega2-lte-base_1.0.0

Option 2: Firmware Update

Or you can update the firmware of your Omega2 LTE.

Make sure you're connected to the internet and run:

oupgrade -l -f

What does this fix?

Two things:

1. Can properly disable GNSS scanning (current consumption will drop about 20~30mA @ 5V)

2. When the lted service is stopped, the modem will actually stop the cellular data connection

@Marko-Lukat re the Omega2 LTE Guide:
This guide is hosted on our website, it's not on GitHub.
Let us know if there are any changes that you would like us to make!

@Martin-Vana This guide might be helpful: https://community.onion.io/topic/2830/building-kernel-modules-for-the-omega2

Asking for Help

If you're still having issues connecting to a WiFi network and would like to ask the community for help, running

wifisetup debug

will create a log file, /tmp/wifidebug.log, with information helpful for troubleshooting the issue.

Adding a -v flag will include a detailed scan of WiFi networks in the surrounding networking in the log file:

wifisetup -v debug

More information is always helpful when debugging issues.

Share this file when posting on the community (of course, you can filter out sensitive information like network passwords).

More Useful Resources

A few more useful resources on the Omega's WiFi:

• https://docs.onion.io/omega2-docs/connecting-to-wifi-networks-command-line.html
• https://onion.io/2bt-brand-new-os-release/

3 - ap_client logs

Running logread | grep ap_client will list the output of the WiFi driver middleware. The output will let you know if the Omega is associated, and if so, the MAC address of the AP:

Fri Oct 19 19:58:58 2018 kern.info ap_client: 'apcli0' assoc: no, mac: 00:00:00:00:00:00
Fri Oct 19 19:58:58 2018 kern.info ap_client: Scanning for networks...
Fri Oct 19 19:59:00 2018 kern.info ap_client: network 0:  3 myNetwork 00:35:9d:13:9b:6d WPA2PSK (AES) -60
Fri Oct 19 19:59:00 2018 kern.info ap_client: network 1:  6 notMyNetwork 00:26:50:9e:3e:09 WEP () -62
Fri Oct 19 19:59:00 2018 kern.info ap_client: network 2:  9 NopeNotMe 8c:68:c8:a7:49:3c WPA2PSK (AES) -63
Fri Oct 19 19:59:00 2018 kern.info ap_client: network 3:  3   fa:8f:ca:31:e1:64 NONE () -64
Fri Oct 19 19:59:00 2018 kern.info ap_client: Found configured network, trying to associate (essid: myNetwork, bssid: 00:35:9d:13:9b:6d,)
Fri Oct 19 19:59:01 2018 kern.info ap_client: 'apcli0' assoc: no, mac: 00:00:00:00:00:00
Fri Oct 19 19:59:02 2018 kern.info ap_client: 'apcli0' assoc: no, mac: 00:00:00:00:00:00
Fri Oct 19 19:59:03 2018 kern.info ap_client: 'apcli0' assoc: yes, mac: 00:35:9d:13:9b:6d
Fri Oct 19 19:59:03 2018 kern.info ap_client: Interface 'apcli0' successfully associated to network (3 checks)
Fri Oct 19 19:59:11 2018 kern.info ap_client: 'apcli0' assoc: yes, mac: 00:35:9d:13:9b:6d
Thu Nov 22 00:21:26 2018 kern.info ap_client: 'apcli0' assoc: yes, mac: 00:35:9d:13:9b:6d
Thu Nov 22 00:21:26 2018 kern.info ap_client: 'apcli0' assoc: yes, mac: 00:35:9d:13:9b:6d
Thu Nov 22 00:21:26 2018 kern.info ap_client: 'apcli0' assoc: yes, mac: 00:35:9d:13:9b:6d
Thu Nov 22 00:21:26 2018 kern.info ap_client: 'apcli0' assoc: yes, mac: 00:35:9d:13:9b:6d
Thu Nov 22 00:21:26 2018 kern.info ap_client: 'apcli0' assoc: yes, mac: 00:35:9d:13:9b:6d

2 - ifconfig

Running ifconfig will also print many lines, but there will be a section for apcli0 that looks something like this:

apcli0    Link encap:Ethernet  HWaddr 42:A3:6B:00:F0:4F
          inet addr:192.168.1.103  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::40a3:6bff:fe00:f04f/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:882 errors:0 dropped:0 overruns:0 frame:0
          TX packets:304 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:133372 (130.2 KiB)  TX bytes:24022 (23.4 KiB)

You can also run ifconfig apcli0 to just get this output.

This will output data related to the Omega's connection with the WiFi network, here you'll be able to see if an IP address is assigned or not.
Note that the statistics displayed here are not accurate.

• If the inet addr part is not blank, then the Omega has successfully connected to the wifi network and has been given an IP address. In the case above, that IP address is 192.168.1.103.
• If the inet addr part is blank, the Omega has not connected to the WiFi network.

We've taken some time to look into this. It turns out a mix of two different MicroUSB port parts was used in the first Omega2 Dash production run.

Here's the part with support tabs - used in many other Onion products:

And here's the tab-less (legless?) part:

But no cause for concern

From what we can tell, @Sarah-Clark's experience with the tab-less MicroUSB port is not the norm. The failure of the port was likely due to a manufacturing defect specific to that board. This board will be replaced

Your Omega2 Dash will work as expected regardless of the MicroUSB port type, and will withstand MicroUSB cables being plugged in and unplugged.

If you have an Omega2 Dash with a tab-less MicroUSB port and are feeling nervous, we suggest taking extra care when plugging in or unplugging cables. For example, holding down the port with a finger and taking care not to place upward pressure on the cable/port.

Going Forward

We've talked with our CM to adjust which parts are ok to use. Going forward, we will only use the part with support tabs. That goes for all Onion products, not just the Dash!

@Radek perhaps there's a NMEA string parsing issue in the code. You can take a closer look at the code here: https://github.com/OnionIoT/ogps

Always open to PRs

@user5456 yep, every Omega2 device has 3 unique MAC addresses.

If you don't end up following @crispyoz's suggestion and use MAC addresses after all, here is an application note on the topic: https://onion.io/2bt-apr2-2019/

@Marko-Lukat We'll take a look.
Submitting a Pull Request will definitely result in a quicker turnaround time! Please submit a Pull Request for the proposed lted changes!

And can you clarify which NMEA reading issue you're referring to?

Update!

The current version of micropython + lvgl for the Omega2 platform has been published as a package!

You can install it on your Omega2 Dash by running:

opkg update
opkg install lv_micropython

The binary will be installed to /usr/bin/micropython.

You can launch the REPL by running micropython or run a script micropython <SCRIPT FILE>

All of this info and more is available in the OnionIoT/lv_micropython README on Github

For those interested in tackling the issue with touch input: We've also added instructions to the README on how to modify the code and build your own version of micropython
See https://github.com/OnionIoT/lv_micropython#build-instructions-for-openwrt and https://github.com/OnionIoT/lv_micropython#compiling-local-code

Don’t worry, the Omega2 family is still in production.
The Onion online store runs out of stock from time to time. It should be replenished in a few weeks.

We can still accept and ship volume orders when the store is out of stock. Learn more by filling out the form here: https://onion.io/quote/

If you need a small quantity in the meantime, you can order from our distributors and resellers, full list available here: https://onion.io/where-to-buy/
We recommend using Mouser or Digikey since they're known for their fast and reliable shipping.

A helpful tip: you can use opkg to list out all of the packages available to install. Then you can use grep to search the list for packages you're interested in.

More on this under the Finding packages to install heading here: http://docs.onion.io/omega2-docs/using-opkg.html#how-to-use-the-package-manager

@David-Kerr Good to hear! Would love to see the final product when it's done!