Group Details Private

administrators

Member List

  • RE: Omega2+ Wifi API

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

    posted in Omega Talk
  • FAQ: How can I control which network interface is used for network traffic? Like use WiFi in some cases but ethernet in others

    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
    posted in Technical FAQs
  • RE: Looking for input managing network connection interfaces

    @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
    posted in Omega Talk
  • RE: Question on capacitors for ethernet circuit [RESOLVED]

    @lzapata pls try to make your topic title more descriptive in the future šŸ™‚

    posted in Omega Talk
  • RE: error while build from source on shellinabox

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

    posted in Omega Talk
  • RE: Building kernel driver.

    @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.

    posted in Omega Talk
  • RE: problems with the o2lte command

    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!

    posted in Omega Talk
  • RE: Building kernel driver. posted in Omega Talk
  • RE: FAQ: How do I check if I'm successfully connected to a WiFi network?

    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).

    posted in Technical FAQs
  • RE: FAQ: How do I check if I'm successfully connected to a WiFi network? posted in Technical FAQs

Looks like your connection to Community was lost, please wait while we try to reconnect.