Bug: data mobile interface looses ip

pparent

@domubpkm said in Bug: data mobile interface looses ip:

The simplest solution is to turn off the cellular data and turn it back

Yes I know but this is a workaround not a real solution, it's not convenient at all, especially if you expect to receive notifications Internet needs to run always in background without manual action. Especially in the context of VoLTE I wonder what impact it has on incoming calls.

domubpkm

@pparent said in Bug: data mobile interface looses ip:

this is a workaround not a real solution

totally agree

I don't know if this currently has an impact on telephone communications since I can call and receive calls with disconnected cellular data. And for 4G calls, Volte is not working for me currently.

pparent

By the way I've just noticed something else strange in the logs:
sometimes I have 2 interfaces called "ccmni1" and "ccmni2". But sometimes I have "ccmni0" and "ccmni2" . I'm not sure if it is related to this bug or not, as both possibilities seem to be able to work if the interface has proper IP.

pparent

Actually I have had the bug once again, and this time the interface holding the IP "ccmni0" was down, but forcing it up did not restore the connexion, I could ping the gateway but nothing more.

pparent

I'm wondering about something, as this problem is an IP loss problem, I think it should be noted that by defualt NetworkManager uses it's internal dhcp handler. But it is also possible to configure it to use dhclient. And I wonder if the later would not be more reliable.

So I think I will test to change the configuration of my NetworkManager to use dhclient, and see if it has any impact on this bug.

domubpkm

Any news about this annoying issue ?

pparent

@domubpkm

I will soon try to write a workaround script, but when I have time.

domubpkm

@pparent THANKS. I still linked this post to NotKit from the Volla team. This is still a big problem for the Volla 22 which will have to be fixed. In addition, network loss is almost systematic each time the volla 22 is restarted.

pparent

@domubpkm

I've written a workaround script that I'm currently testing, that detects an IP loss on the interface and automatically reinitialize the modem when it happens. For now it seems to work quite well, and even seems to have a positive impact on VoLTE connexion. I will test it for a few days, and if everything goes well, I will publish it here.

domubpkm

@pparent Great.
A good test is to see if the connection is still lost after reboot or complete shutdown and startup.

pparent

@domubpkm said:

A good test is to see if the connection is still lost after reboot or complete shutdown and startup.

This is not really the purpose of the script for now. The purpose of the script is that, when you keep the phone up, and you travel, Internet remain accessible at any moment, without needing to manualy go in the settings to restart the connection.

domubpkm

@pparent ok. Thanks for the clarification. I just said that because it is a behavior i noticed very frequently.

gpatel-fr

@pparent

For the record I never commented on this problem because I had not yet seen it but I recently observed something that looked like it: I did pass in an area without cellular support and when going back to civilization, the cellular data did come back but no routing it seems, as you describe.
I'd need a Faraday cage to confirm.

pparent

Here is the script that I currently use, it improves greatly the usability of my phone, because it reduces dramatically the need to go in the settings to restart cellular connexion, in order to get access to the Internet.

Though it's not perfect and might have side effects, use at your own risks!

#!/bin/bash

MODEM="/ril_0"
HOST_TO_PING="8.8.8.8 www.google.com ubports.com 1.1.1.1 9.9.9.9 cloudflare.com amazon.com microsoft.com wikipedia.org apple.com"

function get_modem_iface()
{
/usr/share/ofono/scripts/list-contexts |awk -v target="$1" '
/^\[ \/ril_/ { r=$2 }

/Type = internet/ { i=1 }

/Interface=ccmni/ && r==target && i {
    sub(/^.*Interface=/, "")
    sub(/ .*/, "")
    print
    exit
}
'
}

IFACE=$(get_modem_iface $MODEM)

i=0;

while true; do
    if [ "$IFACE" = "" ]; then
        IFACE=$(get_modem_iface $MODEM)
    fi
    ifconfig $IFACE | grep -v inet6 | grep inet > /dev/null 2>&1
    if [ "$?" -ne "0" ]; then
        gdbus call --system --dest org.ofono --object-path "$MODEM" --method org.ofono.NetworkRegistration.GetProperties | grep "'Technology': <'lte'>" > /dev/null 2>&1
        if [ "$?" -eq "0" ]; then
            date
            echo "IFACE: $IFACE";
            echo "IP loss detected"
            /usr/share/ofono/scripts/offline-modem $MODEM
            /usr/share/ofono/scripts/online-modem $MODEM
            sleep 5;
            IFACE=$(get_modem_iface $MODEM)
        fi
    else
        route=$(ip route show default)
        if [ "$route" = "" ]; then 
            gdbus call --system --dest org.ofono --object-path "$MODEM" --method org.ofono.NetworkRegistration.GetProperties | grep "'Technology': <'lte'>" > /dev/null 2>&1
            if [ "$?" -eq "0" ]; then
                date
                echo "IFACE: $IFACE";
                echo "Route loss detected"
                /usr/share/ofono/scripts/offline-modem $MODEM
                /usr/share/ofono/scripts/online-modem $MODEM
                sleep 5;
                IFACE=$(get_modem_iface $MODEM)
            fi
        fi
    fi
    
    i=$((i+1))
    if [ "$i" -gt "15" ]; then
        i=0;
        gdbus call --system --dest org.ofono --object-path "$MODEM" --method org.ofono.NetworkRegistration.GetProperties | grep "'Technology': <'lte'>" > /dev/null 2>&1
        if [ "$?" -eq "0" ]; then
            internetaccess=0;
            for host in $HOST_TO_PING ; do
                ping -W 1 -c 1 $host >/dev/null 2>&1
                if [ "$?" -eq "0" ]; then
                    internetaccess=1;
                    break;
                else
                    echo "Ping to $host failed, trying next one in 4s ...."
                    sleep 4;
                fi
            done
            if [ "$internetaccess" -eq "0" ]; then
                    date
                    echo "IFACE: $IFACE";
                    echo "Internet access loss detected"
                    /usr/share/ofono/scripts/offline-modem $MODEM
                    /usr/share/ofono/scripts/online-modem $MODEM
                    sleep 5;
                    IFACE=$(get_modem_iface $MODEM)
            fi
        fi
    fi
    sleep 20;
done

lduboeuf

did you reported the issue to the porter ?.
i personaly have some issues on FP4 regrding network too:
e.g Noticed that QNetworkConfigurationManager doesn't report isOnline properly

pparent

@lduboeuf said:

did you reported the issue to the porter ?.

I plan to do so when I have time.

jojumaxx

I just read through this post and want to add that lately, I have that exact issue on my Volla X (24.04-1.2 stable).
I'll test the script and report back.

In my case this goes hand in hand with not being able to receive calls. I can initiate calls, but it takes around a minute until a call is established (until the ring sound).

domubpkm

@pparent Hello. Thanks for the script. Did you notice side effects (you said that, i have a Volla 22 too) ?
May you please suggest a complete procedure to test (as done here https://forums.ubports.com/topic/6211/howto-alternate-way-of-saving-battery-when-using-4g-lte ) ?
Thanks in advance.

pparent

@domubpkm said:

Did you notice side effects (you said that, i have a Volla 22 too) ?

The only thing that I've noted so far, is that If I enable airplane mode with a wrong timing (bad luck), it might go into a loop of disabling / re-eabling the modem. But then I switch off and on, the airplane mode it goes fine.

pparent

@domubpkm said:

May you please suggest a complete procedure to test

1°) With adb create the script with

nano /home/phablet/backup-ip.sh

and paste the content

2°) Give execution rights:

chmod +x /home/phablet/backup-ip.sh

3°) Start the script with:

sudo su -c "/home/phablet/backup-ip.sh > /home/phablet/log-backupip 2>&1 &"

It will then be running until next reboot.