@Malcolm-White Checking if you have a working Yocto layer for Onion builds.

Previously, I configured the Onion OS to use 3g over PPP according to OpenWRT WAN interface protocol on v0.3.2 b232 and was successfully able to access the internet and even share this access. However, following the same process after upgrading to v0.3.3 b250, there is no internet access even though DNS resolution is successful using a PING test. Using ifconfig, I see several bytes are transmitted but 0 bytes are received. I also see a 100% packet loss with PING. I have left this running previously to allow for 3000 packets to be sent yet had no positive results: 100% loss still. Here is a photo of the ping result.

The ONLY difference between the configuration before and after the upgrade is that the former connects to the modem via serial (/dev/ttyS0) and the latter via USB (/dev/ttyUSB2). Files in /etc/config/network and /etc/ppp/options were adjusted accordingly to reflect the changed serial ports.

Content of /etc/ppp/options

debug
/dev/ttyS0
115200
noipdefault
noaccomp
nopcomp
nocrtscts
defaultroute
noipv6
receive-all
noccp
noendpoint
usepeerdns
lock
ktune
noauth
passive
persist
connect '/usr/sbin/chat -v -t 10 -f /etc/chatscripts/3g.chat'
disconnect '/usr/sbin/chat -v -t 10 -f /etc/chatscripts/3g-disconnect.chat'
maxfail 0
lcp-echo-failure 10
lcp-echo-interval 15

Content of /etc/config/network

config interface 'cellulara'       
        option defaultroute '1'                
        option device '/dev/ttyS0'  # /dev/ttyUSB2
        option apn 'tsiot'         
        option service 'umts'         
        option proto '3g'         
        option peerdns '1'         
        option auto '0'               
        option ipv6 '0'

Although logs seen using logread show that the modem began a data session succesfully, on probing the command line arguments of pppd, I discovered that they were slightly different between v0.3.2-b232 (that works) and v0.3.3-b250 (that doesn't work).

Pppd command line from v0.3.2-b232

/usr/sbin/pppd nodetach ipparam cellulara ifname 3g-cellulara lcp-echo-interval 1 lcp-echo-failure 5 lcp-echo-adaptive set PEERDNS=1 nodefaultroute usepeerdns maxfail 1 connect USE_APN=tsiot DIALNUMBER=*99***1# /usr/sbin/chat -t5 -v -E -f /etc/chatscripts/3g.chat ip-up-script /lib/netifd/ppp-up ipv6-up-script /lib/netifd/ppp6-up ip-down-script /lib/netifd/ppp-down ipv6-down-script /lib/netifd/ppp-down noaccomp nopcomp novj nobsdcomp noauth set EXTENDPREFIX=1 lock crtscts 115200 /dev/ttyS0

Pppd command line from v0.3.3-b250

/usr/sbin/pppd nodetach ipparam cellulara ifname 3g-cellulara set PEERDNS=1 nodefaultroute usepeerdns maxfail 1 connect USE_APN=tsiot DIALNUMBER=*99***1# /usr/sbin/chat -t5 -v -E -f /etc/chatscripts/3g.chat ip-up-script /lib/netifd/ppp-up ipv6-up-script /lib/netifd/ppp6-up ip-down-script /lib/netifd/ppp-down ipv6-down-script /lib/netifd/ppp-down noaccomp nopcomp novj nobsdcomp noauth set EXTENDPREFIX=1 lock crtscts 115200 /dev/ttyUSB2

Actually, the difference is just that lcp-echo-interval 1 lcp-echo-failure 5 lcp-echo-adaptive is present in the first but absent in the second.

What I wish to now understand is why I do not have internet access. What do I need to do to ensure internet access via pppd on the v0.3.3 b250?

For your information, there is a package called mwan3 that can carry out load balancing (auto switch to modem if WiFi not available) on OpenWRT. Sadly, it doesn't seem to be compatible with Onion's build. I hacked around this by modifying the default route of the Onion to whatever gateway the modem connects to for internet on the cellular network. I did not have the Omega2 LTE but rather Omega2 Pro with a modem connected via serial port (3g over PPP).

@crispyoz

I'd go through o2-pro-init and see if I can spot possible break points. Then I'd update here. Thanks.

@crispyoz
Strangely, I powered on device today and discovered the issues were gone. This is scary because Onion may go into production and this sort of unpredictable behaviour is most certainly unsettling.

I have copied the content of /etc/config/fstab . Does anything look out-of-place?

root@Omega-345A:~# oupgrade -v
> Device Firmware Version: 0.3.3 b251
root@Omega-345A:~# df -hT
Filesystem           Type            Size      Used Available Use% Mounted on
/dev/root            squashfs        7.8M      7.8M         0 100% /rom
tmpfs                tmpfs          60.9M    108.0K     60.8M   0% /tmp
/dev/mmcblk0p1       ext4            7.1G    417.0M      6.3G   6% /overlay
overlayfs:/overlay   overlay         7.1G    417.0M      6.3G   6% /
tmpfs                tmpfs         512.0K         0    512.0K   0% /dev
/dev/mmcblk0p1       ext4            7.1G    417.0M      6.3G   6% /mnt/mmcblk0p1
/dev/mtdblock6       jffs2           6.6M    420.0K      6.2M   6% /mnt/mtdblock6

config global
        option anon_swap '0'
        option auto_swap '1'
        option auto_mount '1'
        option delay_root '5'
        option check_fs '0'
        option anon_mount '1'

config mount
        option target '/mnt/mmcblk0p1'
        uuid '01c33c4d-234e-4961-9a15-3db2b9ab4231'
        option enabled '0'

config mount
        option target '/mnt/sda1'
        option uuid '02A9-DEF5'
        option enabled '0'

@crispyoz Sorry, I don't understand what I'm upgrading to after a factory reset when I'm already running the latest version. I'd previosly done a factory reset yet this problem persisted.

@crispyoz Hi there. You should note that v0.3.3-b251 is the latest firmware as of 30th June 2021, which is also what I was upgrading my Omega2 Pro to.

Hi,

I can't seem to install more than a few packages on the Omega2 Pro. After boot, Onion complained with this:

Your JFFS2-partition seems full and overlayfs is mounted read-only.
Please try to remove files from /overlay/upper/... and reboot!

When I use df -hT , this is what I get below. I also found that /usr/bin/o2-pro-init does not exit as I can still see it running with top . All these began after an upgrade from v0.3.2-b232 to v0.3.3-b251 using the command sysupgrade -n omega2pro-v0.3.3-b251.bin. I had previously downloaded the firmware into the device while it was on v0.3.2-b232 with wget.

I'm very comfortable with relevant technical materials.

Thank you.

Filesystem        Type          Size   Used    Available   Use%    Mounted on
/dev/root         squashfs      7.8M   7.8M     0          100%    /rom
tmpfs             tmpfs         60.9M  88.0K    60.8M      0%      /tmp
/dev/mtdblock6    jffs2         6.6M  380.0K    6.2M       6%      /overlay
overlayfs:/overlay overlay      6.6M  380.0K    6.2M       6%      /
tmpfs             tmpfs         512.0K  0       512.0K     0%      /dev
/dev/mmcblk0p1    ext4          7.1G  426.5M    6.3G       6%  /mnt/mmcblk0p1

@Lazar-Demin Hi. How do we get the exact changes that followed a particular build? For example, finding whats's different between b251 and b250, both v0.3.3. I did not find this in your Github page here

@Lazar-Demin
Curious. I run v0.3.3 b250 on Omega2Spro yet I'm unable to install a few packages; firstly, when only Onion package repo is in use; secondly, when the OpenWRT larger repo is uncommented in /etc/opkg/distfeeds.conf

I'm unable to install kmod-usb-net-cdc-mbim and few others because of the error below.

root@Cortex-2004:~# opkg install kmod-usb-serial-option
Installing kmod-usb-serial-option (4.14.206-1) to root...
Downloading http://downloads.openwrt.org/releases/18.06-SNAPSHOT/targets/ramips/mt76x8/packages/kmod-usb-serial-option_4.14.206-1_mipsel_24kc.ipk
Collected errors:
 * satisfy_dependencies_for: Cannot satisfy the following dependencies for kmod-usb-serial-option:
 * 	kernel (= 4.14.206-1-da4f999cff891c50c6d11774cc24f4e2) * 
 * opkg_install_cmd: Cannot install package kmod-usb-serial-option.
root@Cortex-2004:~# uname -r
4.14.81
root@Cortex-2004:~#