IPv4 mobile data connection not possible

Bug Reports
, ,
#1

REPRODUCIBILITY: 100%
OS VERSION: 4.4.0.64
HARDWARE: Xperia 10 III
Android Version before flashing Sailfish: 62.0.A.9.11
VOLTE: Disabled
UI LANGUAGE: German
REGRESSION: (compared to previous public release: Yes, No, ?): No
IPv4 and IPv6 mobile data connection works as expected on Xperia X (F5121), SFOS 4.4.0.64, with the same SIM card and same APN settings.

DESCRIPTION:

No IPv4 mobile data connection with MNO Telekom Deutschland possible.

PRECONDITIONS:

SIM card from MNO Telekom Deutschland (e.g. MVNO Congstar)
A.) Set up mobile data access point for dualstack (e.g. Congstar APN: internet.telekom, Protocol: Dual, Auth: PAP, User: congstar, Password: cs)
or
B.) Set up mobile data access point for IP(v4) (e.g. Congstar APN: internet.telekom, Protocol: IP, Auth: PAP, User: congstar, Password: cs)

STEPS TO REPRODUCE:

Turn off WLAN
Turn on mobile data
Ping a IPv4 address (e.g. ping 9.9.9.9)
Read output: “ping: sendto: Network is unreachable”

EXPECTED RESULT:

A.) Dualstack mobile data connection (IPv4 and IPv6) established
B.) IPv4 mobile data connection established

ACTUAL RESULT:

A.) Only IPv6 mobile data connection established
B.) No mobile data connection

ADDITIONAL INFORMATION:

(Please ALWAYS attach relevant data such as logs, screenshots, etc…)

A.) Protocol setting: DUAL:

Jun 11 10:53:59 Xperia10III connmand[5393]: ipconfig state 2 ipconfig method 1
Jun 11 10:53:59 Xperia10III ofonod[3324]: Activating context: 1
Jun 11 10:53:59 Xperia10III kernel: qcom_rpmh DRV:apps_rsc TCS Busy, retrying RPMH message send: addr=0x30010
Jun 11 10:53:59 Xperia10III kernel: qcom_rpmh DRV:apps_rsc TCS Busy, retrying RPMH message send: addr=0x30010
Jun 11 10:53:59 Xperia10III kernel: qcom_rpmh DRV:apps_rsc TCS Busy, retrying RPMH message send: addr=0x30010
Jun 11 10:53:59 Xperia10III kernel: qcom_rpmh DRV:apps_rsc TCS Busy, retrying RPMH message send: addr=0x30010
Jun 11 10:53:59 Xperia10III kernel: qcom_rpmh DRV:apps_rsc TCS Busy, retrying RPMH message send: addr=0x30010
Jun 11 10:53:59 Xperia10III kernel: qcom_rpmh DRV:apps_rsc TCS Busy, retrying RPMH message send: addr=0x30010
Jun 11 10:53:59 Xperia10III kernel: qcom_rpmh DRV:apps_rsc TCS Busy, retrying RPMH message send: addr=0x30010
Jun 11 10:53:59 Xperia10III kernel: qcom_rpmh DRV:apps_rsc TCS Busy, retrying RPMH message send: addr=0x30010
Jun 11 10:53:59 Xperia10III kernel: HTB: quantum of class 10001 is big. Consider r2q change.
Jun 11 10:53:59 Xperia10III kernel: HTB: quantum of class 10010 is big. Consider r2q change.
Jun 11 10:53:59 Xperia10III kernel: HTB: quantum of class 10020 is big. Consider r2q change.
Jun 11 10:53:59 Xperia10III ofonod[3324]: setting up data call
Jun 11 10:53:59 Xperia10III connmand[5393]: ofono: 0x93c22e0 DUAL no IPv4 address set
Jun 11 10:53:59 Xperia10III connmand[5393]: ofono: 0x93c22e0 DUAL no IPv4 address set
Jun 11 10:53:59 Xperia10III connmand[5393]: ofono: 0x93c22e0 DUAL no IPv4 address set
Jun 11 10:53:59 Xperia10III connmand[5393]: ofono: 0x93c22e0 DUAL no IPv4 address set
Jun 11 10:53:59 Xperia10III connmand[5393]: ofono: 0x93c22e0 DUAL no IPv4 address set
Jun 11 10:54:00 Xperia10III connmand[5393]: ofono: 0x93c22e0 DUAL no IPv4 address set
Jun 11 10:54:00 Xperia10III connmand[5393]: ofono: 0x93c22e0 DUAL no IPv4 address set
Jun 11 10:54:00 Xperia10III connmand[5393]: ofono: 0x93c22e0 DUAL no IPv4 address set
Jun 11 10:54:00 Xperia10III connmand[5393]: ofono: 0x93c22e0 DUAL no IPv4 address set
Jun 11 10:54:00 Xperia10III connmand[5393]: ofono: 0x93c22e0 DUAL no IPv4 address set
Jun 11 10:54:00 Xperia10III connmand[5393]: ofono: 0x93c22e0 DUAL no IPv4 address set
Jun 11 10:54:00 Xperia10III connmand[5393]: ofono: 0x93c22e0 DUAL no IPv4 address set
Jun 11 10:54:00 Xperia10III connmand[5393]: ofono: 0x93c22e0 DUAL no IPv4 address set
Jun 11 10:54:00 Xperia10III connmand[5393]: ofono: 0x93c22e0 DUAL no IPv4 address set
Jun 11 10:54:00 Xperia10III connmand[5393]: ofono: 0x93c22e0 DUAL no IPv4 address set
Jun 11 10:54:01 Xperia10III connmand[5393]: ofono: 0x93c22e0 DUAL no IPv4 address set
Jun 11 10:54:01 Xperia10III connmand[5393]: ofono: 0x93c22e0 DUAL no IPv4 address set
Jun 11 10:54:01 Xperia10III connmand[5393]: ofono: 0x93c22e0 DUAL no IPv4 address set
Jun 11 10:54:01 Xperia10III connmand[5393]: ofono: 0x93c22e0 DUAL no IPv4 address set
Jun 11 10:54:01 Xperia10III connmand[5393]: ofono: 0x93c22e0 DUAL no IPv4 address set
Jun 11 10:54:01 Xperia10III connmand[5393]: ofono: 0x93c22e0 DUAL no IPv4 address set
Jun 11 10:54:01 Xperia10III connmand[5393]: ofono: 0x93c22e0 DUAL no IPv4 address set
Jun 11 10:54:01 Xperia10III connmand[5393]: cellular setup was not completed in time
Jun 11 10:54:01 Xperia10III connmand[5393]: ipconfig state 3 ipconfig method 1
Jun 11 10:54:01 Xperia10III kernel: qcom_rpmh DRV:apps_rsc TCS Busy, retrying RPMH message send: addr=0x30010
Jun 11 10:54:02 Xperia10III systemd[5698]: selinux: Unknown permission start for class system
Jun 11 10:54:02 Xperia10III systemd[5698]: selinux: Unknown permission start for class system

[root@Xperia10III defaultuser]# connmanctl services cellular_xxx-congstar-xxx_context1
/net/connman/service/cellular_xxx-congstar-xxx_context1
  Type = cellular
  Security = [  ]
  State = online
  Strength = 67
  Favorite = True
  Immutable = False
  AutoConnect = True
  Name = congstar
  Roaming = False
  Ethernet = [ Method=auto, Interface=rmnet_data2, Address=00:00:00:00:00:00, MTU=1500 ]
  IPv4 = [  ]
  IPv4.Configuration = [ Method=off ]
  IPv6 = [ Method=fixed, Address=2a01:0598:92b4:cfa2:813e:7a68:0323:b9fa, PrefixLength=64, Gateway=fe80:0000:0000:0000:7858:2b86:e0a6:5079, Privacy=disabled ]
  IPv6.Configuration = [ Method=fixed, Address=2a01:0598:92b4:cfa2:813e:7a68:0323:b9fa, PrefixLength=64, Gateway=fe80:0000:0000:0000:7858:2b86:e0a6:5079, Privacy=disabled ]
  Nameservers = [ 2a01:0598:07ff:0000:0010:0074:0210:0221, 2a01:0598:07ff:0000:0010:0074:0210:0222 ]
  Nameservers.Configuration = [  ]
  Timeservers = [  ]
  Timeservers.Configuration = [  ]
  Domains = [  ]
  Domains.Configuration = [  ]
  Proxy = [  ]
  Proxy.Configuration = [  ]
  Provider = [  ]
  Available = True
  Saved = True
  Access = 
  DefaultAccess = sailfish:1;ClearProperty(*)|Connect()|Disconnect()|Remove()|ResetCounters()=deny;group(privileged)=allow

B.) Protocol setting: IP(v4):

Jun 11 11:07:22 Xperia10III ofonod[3324]: Activating context: 1
Jun 11 11:07:22 Xperia10III ofonod[3324]: Unexpected data call status 51
Jun 11 11:07:22 Xperia10III connmand[5393]: [ofono] ERROR! GDBus.Error:org.ofono.Error.Failed: Operation failed

[root@Xperia10III defaultuser]# connmanctl services cellular_xxx-congstar-xxx_context1
/net/connman/service/cellular_xxx-congstar-xxx_context1
  Type = cellular
  Security = [  ]
  State = idle
  Error = connect-failed
  Strength = 62
  Favorite = True
  Immutable = False
  AutoConnect = True
  Name = congstar
  Roaming = False
  Ethernet = [ Method=auto, Interface=rmnet_data2, Address=00:00:00:00:00:00, MTU=1500 ]
  IPv4 = [  ]
  IPv4.Configuration = [ Method=dhcp ]
  IPv6 = [  ]
  IPv6.Configuration = [ Method=fixed, Privacy=disabled ]
  Nameservers = [  ]
  Nameservers.Configuration = [  ]
  Timeservers = [  ]
  Timeservers.Configuration = [  ]
  Domains = [  ]
  Domains.Configuration = [  ]
  Proxy = [  ]
  Proxy.Configuration = [  ]
  Provider = [  ]
  Available = True
  Saved = True
  Access = 
  DefaultAccess = sailfish:1;ClearProperty(*)|Connect()|Disconnect()|Remove()|ResetCounters()=deny;group(privileged)=allow

For comparison:
Xperia X, SFOS 4.4.0.64 with same SIM card and same settings (Case A)

[root@Sailfish nemo]# connmanctl services cellular_xxx-congstar-xxx_context1
/net/connman/service/cellular_xxx-congstar-xxx_context1
  Type = cellular
  Security = [  ]
  State = online
  Strength = 67
  Favorite = True
  Immutable = False
  AutoConnect = True
  Name = congstar
  Roaming = False
  Ethernet = [ Method=auto, Interface=rmnet_data0, Address=00:00:00:00:00:00, MTU=1500 ]
  IPv4 = [ Method=fixed, Address=10.19.204.200, Netmask=255.255.255.240, Gateway=10.19.204.201 ]
  IPv4.Configuration = [ Method=fixed, Address=10.19.204.200, Netmask=255.255.255.240, Gateway=10.19.204.201 ]
  IPv6 = [  ]
  IPv6.Configuration = [ Method=fixed, Address=2a01:0598:9185:be0f:87e2:1b91:ce15:4730, PrefixLength=64, Gateway=fe80:0000:0000:0000:4825:a521:5116:c2f2, Privacy=disabled ]
  Nameservers = [ 10.74.210.210, 10.74.210.211 ]
  Nameservers.Configuration = [  ]
  Timeservers = [ 0.sailfishos.pool.ntp.org, 1.sailfishos.pool.ntp.org, 2.sailfishos.pool.ntp.org, 3.sailfishos.pool.ntp.org ]
  Timeservers.Configuration = [  ]
  Domains = [  ]
  Domains.Configuration = [  ]
  Proxy = [ Method=direct ]
  Proxy.Configuration = [  ]
  Provider = [  ]
  Available = True
  Saved = True
  Access = 
  DefaultAccess = sailfish:1;ClearProperty(*)|Connect()|Disconnect()|Remove()|ResetCounters()=deny;group(privileged)=allow

For further comparison:
Xperia 10 III, SFOS 4.4.0.64 with another SIM card from MNO O2 Deutschland (MVNO MEDIONmobile) (Case A)

[root@Xperia10III defaultuser]# connmanctl services cellular_x-medionmobile-x_context1
/net/connman/service/cellular_x-medionmobile-x_context1
  Type = cellular
  Security = [  ]
  State = online
  Strength = 37
  Favorite = True
  Immutable = False
  AutoConnect = True
  Name = MEDIONmobile
  Roaming = False
  Ethernet = [ Method=auto, Interface=rmnet_data2, Address=00:00:00:00:00:00, MTU=1500 ]
  IPv4 = [ Method=fixed, Address=10.134.11.52, Netmask=255.255.255.248, Gateway=10.134.11.53 ]
  IPv4.Configuration = [ Method=fixed, Address=10.134.11.52, Netmask=255.255.255.248, Gateway=10.134.11.53 ]
  IPv6 = [ Method=fixed, Address=2a02:3035:0c0a:421b:f5aa:442e:ade0:4e48, PrefixLength=64, Gateway=fe80:0000:0000:0000:70a7:709f:b4da:89b5, Privacy=disabled ]
  IPv6.Configuration = [ Method=fixed, Address=2a02:3035:0c0a:421b:f5aa:442e:ade0:4e48, PrefixLength=64, Gateway=fe80:0000:0000:0000:70a7:709f:b4da:89b5, Privacy=disabled ]
  Nameservers = [ 62.109.121.17, 62.109.121.18, 2a02:3018:0000:40ff:0000:0000:0000:aaaa, 2a02:3018:0000:40ff:0000:0000:0000:bbbb, 2a02:3018:0:40ff::aaaa, 2a02:3018:0:40ff::bbbb, 2a02:3018:0:40ff::aaaa, 2a02:3018:0:40ff::bbbb ]
  Nameservers.Configuration = [  ]
  Timeservers = [  ]
  Timeservers.Configuration = [  ]
  Domains = [  ]
  Domains.Configuration = [  ]
  Proxy = [ Method=direct ]
  Proxy.Configuration = [  ]
  Provider = [  ]
  Available = True
  Saved = True
  Access = 
  DefaultAccess = sailfish:1;ClearProperty(*)|Connect()|Disconnect()|Remove()|ResetCounters()=deny;group(privileged)=allow
7 Likes
Help: IPv4 on mobile data Sony Xperia 10 III 4.4.0.68 Vanha Rauma
Use of mobile data (IPv6) although a WLAN connection (IPv4) is active
Kernel module support 4.4 - on the phone
[Release notes] Vanha Rauma 4.4.0.68
Help: IPv4 on mobile data Sony Xperia 10 III 4.4.0.68 Vanha Rauma
Community meeting on IRC 18th August 2022
Hotspot not working 10 III
Use of mobile data (IPv6) although a WLAN connection (IPv4) is active
Data counters not working for SIM
Hotspot not working 10 III
Kernel module support 4.4 - on the phone
I can’t get the VPN to work
Bug report:mobile internet on new devices
Mobile Data not working under COOPVOCE Sim carrier
GPS stopped working
Hotspot not working 10 III
Sailfish Community News, 23rd February, CLAT
Community meeting on IRC 23rd June 2022
Talk about SailfishOS in German - Unterhalte dich über SailfishOS auf Deutsch
Hotspot not working 10 III
#2

Many thanks @akikyo!
akikyo had a similar problem and the solution works for this issue as well:

On this basis, here is the procedure which functioned for me:

  • Flash to Android 62.0.A.3.109 with EMMA
  • Do not relock the bootloader and do not receive any further Android updates
  • Test IPv4 mobile data connection with Telekom DE SIM
  • After I was sure it worked with Android as expected, I flashed to SFOS

Now IPv4 mobile data connection with Telekom DE SIM works also perfectly on Xperia 10 III SFOS 4.4.0.64

2 Likes
Community meeting on IRC 18th August 2022
#3

Doesn’t work on my Phone :frowning:

#4

After Update to 4.4.0.68 the bug is back.
Seems like the issue needs further investigation.

@Gorden:
Which SFOS Version did you flash?

#5

Had flashed the 4.4.0.68 too

#6

I will try to flash back to version 4.4.0.64 tomorrow.
If the IPv4 mobile data connection works in SFOS 4.4.0.64, there is probably a new bug in version 4.4.0.68.

#7

Had with 4.4.0.64 the same issue.

1 Like
#8

Have you tried flashing from Android 62.0.A.3.109 to SFOS 4.4.0.64?

The first two times I flashed SFOS 4.4.0.64 I was on Android 62.0.A.9.11. Both times the IPv4 mobile data connection under SFOS did not work.
Only when I flashed to Android 62.0.A.3.109 and then to SFOS 4.4.0.64 did the IPv4 mobile data connection work.
After today’s update to 4.4.0.68, the IPv4 mobile data connection no longer works.
Maybe just a coincidence, but I’ll test it again tomorrow with SFOS 4.4.0.64.

#9

Yes and try the same with 4.4.0.68

#10

Weird, I had the opposite experience:

  • installed Sailfish ontop of which ever Android 11 / 62.0.A.3.xx was out-of-the-box, and got troubles with connection, mostly when roaming abroad (stuck at “2G” level, and unreachable network)
  • flashing Android 11 / 62.0.A.9.11, running the checklist (including testing internet connection), then reflashing Sailfish OS from a dd backup, solved the problem for me.

I still needed to systemctl restart ofono.service every now and then when losing the connection, but eventually it’s stable now (some OTA update downloaded by the modem’s firwmare or the SIM itself and stored on one of the zillion Android partitions?).

#11

Temporarily the same here.
I don’t remember if it was the “keep the 2nd SIM slot turned on” tick or simply forcing connection with systemctl restart ofono (or even more trivially: the SIM or modem firmware doing their own thing and fetching some OTA update for themselves).
But eventually it resolved, I have 4G connectino while roaming abroad again.

#12

I flashed SFOS version 4.4.0.64 and also version 4.4.0.68 several times without flashing back to Android.
I could not get the mobile IPv4 internet connection to work.
Interestingly, there were different behaviors.

Sometimes I didn’t get an IPv4 address at all.
ofono: 0x93c22e0 DUAL no IPv4 address set
(see log in bug report)

After the next flashing, I got an IPv4 address and the route was entered correctly, but no internet connection was possible.

[root@Xperia10III defaultuser]# ifconfig
...
rmnet_data0 Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  
          inet addr:10.28.99.243  Mask:255.255.255.248
          inet6 addr: fe80::f972:149c:9c45:5c3a/64 Scope:Link
          inet6 addr: 2a01:59f:918b:7360:f972:149c:9c45:5c3a/64 Scope:Global
...

[root@Xperia10III defaultuser]# ip -4 route | grep default & ip -6 route | grep default
default via fe80::2091:ad45:2f36:5d45 dev rmnet_data0  proto ra  metric 1024  expires 65509sec
default via 10.28.99.244 dev rmnet_data0 

[root@Xperia10III defaultuser]# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes

--- 8.8.8.8 ping statistics ---
24 packets transmitted, 0 packets received, 100% packet loss

I also tried the SIM switch, but in slot 2 my SIM card doesn’t work at all at first.
The SIM was recognized and the PIN was requested, but no connection could be established.
Neither telephony nor data (network search runs forever).
After further flash attempts, the card worked in Slot 2, but also without an IPv4 connection.

Also I tried restarting ofono but that didn’t change anything.

Only after I flashed Android 62.0.A.3.109 again with Emma, tested the IPv4 connection and flashed SFOS 4.4.0.64 from there did I have an IPv4 internet connection again.

[root@Xperia10III defaultuser]# ifconfig
...
rmnet_data1 Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  
          inet addr:10.46.151.212  Mask:255.255.255.248
          inet6 addr: 2a01:598:a902:10bb:40e1:52ba:9bdc:36bc/64 Scope:Global
          inet6 addr: fe80::40e1:52ba:9bdc:36bc/64 Scope:Link
...

[root@Xperia10III defaultuser]# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: seq=0 ttl=112 time=198.151 ms
64 bytes from 8.8.8.8: seq=1 ttl=112 time=37.438 ms
64 bytes from 8.8.8.8: seq=2 ttl=112 time=27.022 ms
64 bytes from 8.8.8.8: seq=3 ttl=112 time=27.786 ms
^C
--- 8.8.8.8 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 27.022/72.599/198.151 ms

Then I made an update to SFOS 4.4.0.68 via the GUI and after that no IPv4 connection is possible anymore.
ofono: 0x9a07b70 DUAL no IPv4 address set
(see log in bug report)

Maybe i have to Flash Android 62.0.A.3.109 again with Emma and then directly SFOS 4.4.0.68?
Maybe i need another Android Baseband Version for SFOS 4.4.0.68?
Maybe there is a bug in SFOS 4.4.0.68?
Does anyone have a hint?

I gave it one more try and it worked for me as follows:
I flashed Android 62.0.A.3.109 again with Emma,
tested the IPv4 connection on Android,
flashed directly to SFOS 4.4.0.68.

[root@Xperia10III defaultuser]# version
Sailfish OS 4.4.0.68 (Vanha Rauma)
[root@Xperia10III defaultuser]# ip -4 route | grep default & ip -6 route | grep default
default via 10.120.51.105 dev rmnet_data2 
default via fe80::998d:4125:59b0:fe29 dev rmnet_data2  proto ra  metric 1024  expires 65174sec hoplimit 255
[root@Xperia10III defaultuser]# ping -4 dns.google.com
PING dns.google.com (8.8.4.4): 56 data bytes
64 bytes from 8.8.4.4: seq=0 ttl=112 time=26.221 ms
64 bytes from 8.8.4.4: seq=1 ttl=112 time=25.940 ms
64 bytes from 8.8.4.4: seq=2 ttl=112 time=30.579 ms
^C
--- dns.google.com ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 25.940/27.580/30.579 ms

Maybe just until the next update?

Lost mobile data - Can make calls but only get data on wifi - "3G" displayed - 4G calling = "Not Registered" and flashing
#13

On my phone it doesn’t work with flashing Android 11, testing ip4 and than flashing SFOS

#14

I followed exactly the described procedure but it doesn’t work for me neither! In consequence no telegram usage is possible over mobile network because telegram seems to rely on IPV4. Android app firefox instead works.
Edit: This thread could(!) be a double post / duplicate to Unable to use mobile data on Sony Xperia 10 III 4.4.0.64 - #49 by akikyo
Edit: … or [4.4.0.64][Xperia 10 III}VoLTE conflicts with mobile data

#15

After a few days with no IPv4 issues, I decided to turn on VOLTE.

But VOLTE could not be registered. I knew it had worked on 4.4.0.64 so I rebooted the phone.
After restart, VOLTE was successfully registered, but since then IPv4 mobile connection again, is no longer possible.

Jul 24 16:17:39 Xperia10III connmand[5336]: ofono: 0x6a0b370 DUAL no IPv4 address set

I switched the SIM to Slot 2 and there i have my ipv4 back again.
But no matter what I try in slot 2, VOLTE cannot register.
I also need the SD card and who knows how long it will work in slot 2.
Therefore, it is not a permanent solution for me to occupy slot 2 with the SIM card.

Since this doesn’t work for others either, I no longer believe that flashing to Android 62.0.A.3.109 is really the solution.
The fact that it worked for me twice can’t be a coincidence either.
But I’m slowly running out of ideas and would be grateful for any hints as to what else I could try.

PS: Could someone with proper rights please remove the ‘fixed’ tag

#16

I’ve the same problem. Updated to 4.4.0.68 and my IPv4 adress is gone when using mobile data. Sim Slot 2 only asks for PIN but never connects.

Seems i have to reflash again…

#17

I also think it is not relate to the flashed Android base. I never got an ipv4 adress with .109. It worked with an even older Android version once, but after updating to 4.4.0.68 ipv4 was one an also hotspot functionality. Now im tired of reflashing until it works. hopefully Jolla fixes this in the next update.

1 Like
#18

I’m also tired of re-flashing over and over again just to get it working for a short time.
At least I’m not the only one with this problem.
I think it affects far more users, but unless they rely on pure IPv4 services, they usually won’t even notice the problem.
However, I am afraid that as long as only a few users notice and report this problem, it will not be taken seriously enough.

#19

When using sim slot2 i’ll get an IPv4 adress, but VoLTE is failing and i can’t connect to the net.

#20

Have the same problem now.
After i deactivated SIM slot 1, only limited connection with mobile data on slot 2.
IPv4 and IPv6 address is assigned, but no internet connection possible.

[root@Xperia10III defaultuser]# ifconfig
...
rmnet_data1 Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  
          inet addr:10.25.152.250  Mask:255.255.255.252
          inet6 addr: fe80::b05d:a509:8007:1ea/64 Scope:Link
          inet6 addr: 2a01:59f:a810:a080:b05d:a509:8007:1ea/64 Scope:Global
          UP RUNNING  MTU:1500  Metric:1
          RX packets:11 errors:0 dropped:0 overruns:0 frame:0
          TX packets:220 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:1272 (1.2 KiB)  TX bytes:15956 (15.5 KiB)
...

[root@Xperia10III defaultuser]# ip -4 route | grep default & ip -6 route | grep default
default via 10.25.152.249 dev rmnet_data1 
default via fe80::bd9e:6812:c963:e4cb dev rmnet_data1  proto ra  metric 1024  expires 65487sec

[root@Xperia10III defaultuser]# ping -4 dns.google.com
ping: bad address 'dns.google.com'

[root@Xperia10III defaultuser]# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
--- 8.8.8.8 ping statistics ---
27 packets transmitted, 0 packets received, 100% packet loss

[root@Xperia10III defaultuser]# ping -6 dns.google.com
ping: bad address 'dns.google.com'

[root@Xperia10III defaultuser]# ping 2001:4860:4860::8888
PING 2001:4860:4860::8888 (2001:4860:4860::8888): 56 data bytes
--- 2001:4860:4860::8888 ping statistics ---
21 packets transmitted, 0 packets received, 100% packet loss

Unfortunately, reactivating slot 1 doesn’t help.

After hours of testing, the only certain result is that sooner or later the mobile data connection will stop working properly or break off completely.