Hotspot not working 10 III

Bug Reports
,
#20

Okay, I made some more tests.

I have two SIM Cards, both Telekom DE and as such the same mobile network as @senders - maybe the the first thing cause we both have the same problem.

I have/had several devices - with my main SIM I had no problem with Internet sharing so far. I used this SIM over the years in different iPhones (3G, 4, 4S, Xr), two Windows Phones (Lumia 920, Lumia 950), two android phones (Xperia XZ3, Xperia 5 II) without any problems and could share my connection.
I also tried this SIM in the Xperia 10 III, but that leads to the problem like my secondary card also does.
I tried to get a connection wit my Jolla C too (but don’t remember which of both cards I used) where sharing works like expected as I already described in my initial post.

I tried the https://8.8.8.8 thing with both SIMs in Xperia 5 II (Android 12) and Xperia 10 III (SFOS 4.4.0.64). Did work with both SIMS on Android, but didn’t work on SFOS.

I also tried to manually restrict the data connection to IP oder IPV& instead of Dual, but all thsi had no effect - no internet access possible while the connection between two devices (SFOS as host) itself works.

So to my mind this must be a bug especially with the Xperia 10 III build that maybe just occurs with specific providers/mobile networks.

I could give that a try with Xperia XA2 in the next days…

@rainemak If you need some more information to dive into your ideas please give me some hints what exactly to do to get and deliver that.

#21

Hi @reinemak,

thanks for your answer.
Here the outputs you ask for:

First for a mobile internet connection only IPv6 established (Incorrect behavior on Xperia 10 III, see my mentioned bug report)
Xperia 10 III with Constar (MNO Telekom DE) SIM card, settings: APN: internet.telekom, Protocol: Dual, Auth: PAP, User: congstar, Password: cs

rmnet_data1 is assigned to mobile data:

[root@Xperia10III defaultuser]# connmanctl services cellular_xxx-congstar-xxx_context1 | grep Ethernet
  Ethernet = [ Method=auto, Interface=rmnet_data1, Address=00:00:00:00:00:00, MTU=1500 ]

[root@Xperia10III defaultuser]# ifconfig
lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:34947 errors:0 dropped:0 overruns:0 frame:0
          TX packets:34947 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:3634766 (3.4 MiB)  TX bytes:3634766 (3.4 MiB)

rmnet_data0 Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  
          inet6 addr: fe80::7266:8d1d:bdbd:3ceb/64 Scope:Link
          UP RUNNING  MTU:1500  Metric:1
          RX packets:30 errors:0 dropped:0 overruns:0 frame:0
          TX packets:32 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:1524 (1.4 KiB)  TX bytes:1672 (1.6 KiB)

rmnet_data1 Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  
          inet6 addr: fe80::5a67:258:59ee:45da/64 Scope:Link
          inet6 addr: 2a01:598:d84b:2084:5a67:258:59ee:45da/64 Scope:Global
          UP RUNNING  MTU:1500  Metric:1
          RX packets:3742 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4374 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:726554 (709.5 KiB)  TX bytes:410208 (400.5 KiB)

rmnet_ipa0 Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  
          UP RUNNING  MTU:9216  Metric:1
          RX packets:12501 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12152 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:7039754 (6.7 MiB)  TX bytes:2691224 (2.5 MiB)

rndis0    Link encap:Ethernet  HWaddr 3E:55:96:D6:66:F2  
          inet addr:192.168.10.1  Bcast:192.168.10.255  Mask:255.255.255.0
          inet6 addr: fe80::3c55:96ff:fed6:66f2/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST DYNAMIC  MTU:1500  Metric:1
          RX packets:374 errors:0 dropped:0 overruns:0 frame:0
          TX packets:193 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:35302 (34.4 KiB)  TX bytes:38011 (37.1 KiB)

tether    Link encap:Ethernet  HWaddr 3C:01:EF:F1:22:1C  
          inet addr:172.28.172.1  Bcast:172.28.172.255  Mask:255.255.255.0
          inet6 addr: fe80::90ca:88ff:fea4:c4fc/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST DYNAMIC  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:11 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:1026 (1.0 KiB)

wlan0     Link encap:Ethernet  HWaddr 3C:01:EF:F1:22:1C  
          inet6 addr: fe80::3e01:efff:fef1:221c/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST DYNAMIC  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:96112 overruns:0 frame:0
          TX packets:17 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:3000 
          RX bytes:0 (0.0 b)  TX bytes:1482 (1.4 KiB)

[root@Xperia10III defaultuser]# ip route | grep default & ip -6 route | grep default
default via fe80::79fe:4c70:e2d:2eb8 dev rmnet_data1  proto ra  metric 1024  expires 64054sec
[1]+  Done(1)                    ip route | grep default

IPv6 works as expected:

[root@Xperia10III defaultuser]# traceroute -6 dns.google.com
traceroute to dns.google.com (2001:4860:4860::8888), 30 hops max, 72 byte packets
 1  *  *  *
 2  *  *  *
 3  *  *  *
 4  *  *  *
 5  *  *  *
 6  *  *  *
 7  *  *  *
 8  *  *  *
 9  *  *  *
10  2003:0:1304:8013::2 (2003:0:1304:8013::2)  63.536 ms  26.073 ms  22.638 ms
11  *  2a00:1450:814c::1 (2a00:1450:814c::1)  36.718 ms  2a00:1450:8154::1 (2a00:1450:8154::1)  26.956 ms
12  dns.google (2001:4860:4860::8888)  28.276 ms  34.169 ms  26.493 ms

[root@Xperia10III defaultuser]# ping -6 -w 4 dns.google.com
PING dns.google.com (2001:4860:4860::8844): 56 data bytes
64 bytes from 2001:4860:4860::8844: seq=0 ttl=114 time=54.033 ms
64 bytes from 2001:4860:4860::8844: seq=1 ttl=114 time=33.556 ms
64 bytes from 2001:4860:4860::8844: seq=2 ttl=114 time=24.154 ms
64 bytes from 2001:4860:4860::8844: seq=3 ttl=114 time=28.760 ms

--- dns.google.com ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 24.154/35.125/54.033 ms

Since there is no mobile IPv4 internet connection, traceroute -4 and ping -4 can not work. But for the record:

[root@Xperia10III defaultuser]# traceroute -4 dns.google.com
traceroute: can't connect to remote host (8.8.8.8): Network is unreachable

[root@Xperia10III defaultuser]# ping -4 -w 4 dns.google.com
PING dns.google.com (8.8.8.8): 56 data bytes
ping: sendto: Network is unreachable

On the device that joined the Hotspot:

senders@xrog:~$ ifconfig
enp4s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        ether 50:eb:f6:48:d7:6e  txqueuelen 1000  (Ethernet)
        RX packets 29116  bytes 10843925 (10.8 MB)
        RX errors 0  dropped 3682  overruns 0  frame 0
        TX packets 10303  bytes 1837573 (1.8 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Lokale Schleife)
        RX packets 2900  bytes 273922 (273.9 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 2900  bytes 273922 (273.9 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

usb0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.10.2  netmask 255.255.255.0  broadcast 192.168.10.255
        inet6 fe80::d878:3d0d:a8f4:6b8b  prefixlen 64  scopeid 0x20<link>
        ether xx:xx:xx:xx:xx:xx  txqueuelen 1000  (Ethernet)
        RX packets 935  bytes 107985 (107.9 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1611  bytes 208964 (208.9 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlp5s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 172.28.172.2  netmask 255.255.255.0  broadcast 172.28.172.255
        inet6 fe80::d290:3635:c42b:142d  prefixlen 64  scopeid 0x20<link>
        ether xx:xx:xx:xx:xx:xx  txqueuelen 1000  (Ethernet)
        RX packets 276  bytes 34263 (34.2 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1843  bytes 140972 (140.9 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

senders@xrog:~$ ip route | grep default & ip -6 route | grep default
[1] 8590
default via 172.28.172.1 dev wlp5s0 proto dhcp metric 20600 
[1]+  Fertig                  ip route | grep --color=auto default

Since there is no IPv6 connection to the Xperia 10 III, traceroute -6 and ping -6 can not work. But for the record:

senders@xrog:~$ traceroute -6 dns.google.com
traceroute to dns.google.com (2001:4860:4860::8844), 30 hops max, 80 byte packets
connect: Das Netzwerk ist nicht erreichbar

senders@xrog:~$ ping -6 -w 4 dns.google.com
ping: connect: Das Netzwerk ist nicht erreichbar

IPv4 also does not work, because there is no IPv4 mobile internet connection on Xperia 10 III

senders@xrog:~$ traceroute -4 dns.google.com
traceroute to dns.google.com (8.8.4.4), 30 hops max, 60 byte packets
 1  * * *
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  * * *
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  _gateway (172.28.172.1)  32.331 ms !N * *

senders@xrog:~$ ping -4 -w 4 dns.google.com
PING dns.google.com (8.8.8.8) 56(84) bytes of data.

--- dns.google.com ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3074ms

Now the same for an established IPv4 and IPv6 mobile internet connection:
Xperia 10 III with MEDIONmobile (MNO O2 DE) SIM card, settings: APN: internet, Protocol: Dual, Auth: None

rmnet_data2 is assigned to mobile data:

[root@Xperia10III defaultuser]# connmanctl services cellular_x-medionmobile-x_context1 | grep Ethernet
  Ethernet = [ Method=auto, Interface=rmnet_data2, Address=00:00:00:00:00:00, MTU=1500 ]

[root@Xperia10III defaultuser]# ifconfig
lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:35821 errors:0 dropped:0 overruns:0 frame:0
          TX packets:35821 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:3726160 (3.5 MiB)  TX bytes:3726160 (3.5 MiB)

rmnet_data0 Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  
          inet6 addr: fe80::7266:8d1d:bdbd:3ceb/64 Scope:Link
          UP RUNNING  MTU:1500  Metric:1
          RX packets:31 errors:0 dropped:0 overruns:0 frame:0
          TX packets:33 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:1572 (1.5 KiB)  TX bytes:1720 (1.6 KiB)

rmnet_data2 Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  
          inet addr:10.131.65.56  Mask:255.255.255.240
          inet6 addr: fe80::48bd:57a9:3128:d00f/64 Scope:Link
          inet6 addr: 2a02:3030:814:ef6e:48bd:57a9:3128:d00f/64 Scope:Global
          UP RUNNING  MTU:1500  Metric:1
          RX packets:17174 errors:0 dropped:0 overruns:0 frame:0
          TX packets:18771 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:7745155 (7.3 MiB)  TX bytes:2123454 (2.0 MiB)

rmnet_ipa0 Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  
          UP RUNNING  MTU:9216  Metric:1
          RX packets:13566 errors:0 dropped:0 overruns:0 frame:0
          TX packets:13119 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:7225055 (6.8 MiB)  TX bytes:2979196 (2.8 MiB)

rndis0    Link encap:Ethernet  HWaddr 3E:55:96:D6:66:F2  
          inet addr:192.168.10.1  Bcast:192.168.10.255  Mask:255.255.255.0
          inet6 addr: fe80::3c55:96ff:fed6:66f2/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST DYNAMIC  MTU:1500  Metric:1
          RX packets:1699 errors:0 dropped:0 overruns:0 frame:0
          TX packets:986 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:145134 (141.7 KiB)  TX bytes:176241 (172.1 KiB)

tether    Link encap:Ethernet  HWaddr 3C:01:EF:F1:22:1C  
          inet addr:172.28.172.1  Bcast:172.28.172.255  Mask:255.255.255.0
          inet6 addr: fe80::90ca:88ff:fea4:c4fc/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST DYNAMIC  MTU:1500  Metric:1
          RX packets:4406 errors:0 dropped:0 overruns:0 frame:0
          TX packets:813 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:296066 (289.1 KiB)  TX bytes:91435 (89.2 KiB)

wlan0     Link encap:Ethernet  HWaddr 3C:01:EF:F1:22:1C  
          inet6 addr: fe80::3e01:efff:fef1:221c/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST DYNAMIC  MTU:1500  Metric:1
          RX packets:8812 errors:0 dropped:96112 overruns:0 frame:0
          TX packets:926 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:3000 
          RX bytes:296066 (289.1 KiB)  TX bytes:104283 (101.8 KiB)

[root@Xperia10III defaultuser]# ip route | grep default & ip -6 route | grep default
default via fe80::54fb:e09b:b392:1528 dev rmnet_data2  proto ra  metric 1024  expires 65514sec
default via 10.208.95.33 dev rmnet_data2

IPv6 works as expected:

[root@Xperia10III defaultuser]# traceroute -6 dns.google.com
traceroute to dns.google.com (2001:4860:4860::8844), 30 hops max, 72 byte packets
 1  *  *  *
 2  fd46:5186:54d1:e49f::1 (fd46:5186:54d1:e49f::1)  42.234 ms  72.133 ms  119.681 ms
 3  2a02:3000:1100:102::74 (2a02:3000:1100:102::74)  40.646 ms  2a02:3000:1100:102::76 (2a02:3000:1100:102::76)  67.778 ms  2a02:3000:1100:102::74 (2a02:3000:1100:102::74)  75.401 ms
 4  *  *  *
 5  2a02:3000:1100:12f::2 (2a02:3000:1100:12f::2)  79.720 ms  62.245 ms  59.591 ms
 6  2a02:3001::13c (2a02:3001::13c)  51.882 ms  55.181 ms  40.558 ms
 7  2001:4860:1:1::a5e (2001:4860:1:1::a5e)  39.945 ms  41.131 ms  67.681 ms
 8  *  2a00:1450:8160::1 (2a00:1450:8160::1)  57.457 ms  *
 9  dns.google (2001:4860:4860::8844)  48.956 ms  48.773 ms  52.790 ms

[root@Xperia10III defaultuser]# ping -6 -w 4 dns.google.com
PING dns.google.com (2001:4860:4860::8844): 56 data bytes
64 bytes from 2001:4860:4860::8844: seq=0 ttl=115 time=47.364 ms
64 bytes from 2001:4860:4860::8844: seq=1 ttl=115 time=47.181 ms
64 bytes from 2001:4860:4860::8844: seq=2 ttl=115 time=46.733 ms
64 bytes from 2001:4860:4860::8844: seq=3 ttl=115 time=46.618 ms

--- dns.google.com ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 46.618/46.974/47.364 ms

IPv4 works as expected:

[root@Xperia10III defaultuser]# traceroute -4 dns.google.com
traceroute to dns.google.com (8.8.4.4), 30 hops max, 46 byte packets
 1  *  *  *
 2  172.21.0.97 (172.21.0.97)  46.007 ms  106.607 ms  34.163 ms
 3  10.81.108.249 (10.81.108.249)  44.879 ms  10.81.108.253 (10.81.108.253)  84.944 ms  10.81.108.249 (10.81.108.249)  63.912 ms
 4  *  10.81.85.22 (10.81.85.22)  51.645 ms  72.928 ms
 5  213.20.88.34 (213.20.88.34)  34.974 ms  72.858 ms  34.739 ms
 6  ae1-0.0001.prrx.01.ham.de.net.telefonica.de (62.53.25.59)  57.750 ms  ae0-0.0001.prrx.01.ham.de.net.telefonica.de (62.53.25.57)  44.099 ms  ae1-0.0001.prrx.01.ham.de.net.telefonica.de (62.53.25.59)  40.055 ms
 7  74.125.48.102 (74.125.48.102)  37.316 ms  68.505 ms  45.525 ms
 8  *  *  *
 9  dns.google (8.8.4.4)  57.790 ms  40.058 ms  35.751 ms
 
[root@Xperia10III defaultuser]# ping -4 -w 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=115 time=98.305 ms
64 bytes from 8.8.4.4: seq=1 ttl=115 time=57.951 ms
64 bytes from 8.8.4.4: seq=2 ttl=115 time=57.585 ms
64 bytes from 8.8.4.4: seq=3 ttl=115 time=57.244 ms

--- dns.google.com ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 57.244/67.771/98.305 ms

On the device that joined the hotspot:

senders@xrog:~$ ifconfig
enp4s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        ether 50:eb:f6:48:d7:6e  txqueuelen 1000  (Ethernet)
        RX packets 38009  bytes 11924665 (11.9 MB)
        RX errors 0  dropped 5651  overruns 0  frame 0
        TX packets 10303  bytes 1837573 (1.8 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Lokale Schleife)
        RX packets 4065  bytes 394591 (394.5 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 4065  bytes 394591 (394.5 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

usb0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.10.2  netmask 255.255.255.0  broadcast 192.168.10.255
        inet6 fe80::d878:3d0d:a8f4:6b8b  prefixlen 64  scopeid 0x20<link>
        ether xx:xx:xx:xx:xx:xx  txqueuelen 1000  (Ethernet)
        RX packets 1196  bytes 150241 (150.2 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 2022  bytes 260032 (260.0 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlp5s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 172.28.172.2  netmask 255.255.255.0  broadcast 172.28.172.255
        inet6 fe80::d290:3635:c42b:142d  prefixlen 64  scopeid 0x20<link>
        ether xx:xx:xx:xx:xx:xx  txqueuelen 1000  (Ethernet)
        RX packets 1076  bytes 169885 (169.8 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 5340  bytes 443877 (443.8 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

senders@xrog:~$ ip route | grep default & ip -6 route | grep default
[1] 10318
default via 172.28.172.1 dev wlp5s0 proto dhcp metric 600 
[1]+  Fertig                  ip route | grep --color=auto default

Since there is no IPv6 connection to the Xperia 10 III, traceroute -6 and ping -6 can not work. But for the record:

senders@xrog:~$ traceroute -6 dns.google.com
traceroute to dns.google.com (2001:4860:4860::8888), 30 hops max, 80 byte packets
connect: Das Netzwerk ist nicht erreichbar

senders@xrog:~$ ping -6 -w 4 dns.google.com
ping: connect: Das Netzwerk ist nicht erreichbar

IPv4 and thus Internet sharing works perfectly:

senders@xrog:~$ traceroute -4 dns.google.com
traceroute to dns.google.com (8.8.4.4), 30 hops max, 60 byte packets
 1  _gateway (172.28.172.1)  2.112 ms  2.222 ms  2.378 ms
 2  * * *
 3  172.21.0.97 (172.21.0.97)  75.801 ms  75.773 ms  77.515 ms
 4  10.81.108.249 (10.81.108.249)  76.865 ms 10.81.108.253 (10.81.108.253)  80.336 ms  86.717 ms
 5  * * *
 6  213.20.88.34 (213.20.88.34)  86.655 ms  52.613 ms  113.165 ms
 7  ae0-0.0001.prrx.01.ham.de.net.telefonica.de (62.53.25.57)  113.131 ms ae1-0.0001.prrx.01.ham.de.net.telefonica.de (62.53.25.59)  113.083 ms  113.068 ms
 8  74.125.48.102 (74.125.48.102)  113.030 ms  113.017 ms  112.992 ms
 9  * * *
10  dns.google (8.8.4.4)  112.883 ms  112.937 ms  112.898 ms

senders@xrog:~$ ping -4 -w 4 dns.google.com
PING dns.google.com (8.8.4.4) 56(84) bytes of data.
64 bytes from dns.google (8.8.4.4): icmp_seq=1 ttl=114 time=74.6 ms
64 bytes from dns.google (8.8.4.4): icmp_seq=2 ttl=114 time=73.0 ms
64 bytes from dns.google (8.8.4.4): icmp_seq=3 ttl=114 time=70.9 ms
64 bytes from dns.google (8.8.4.4): icmp_seq=4 ttl=114 time=69.2 ms

--- dns.google.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3005ms
rtt min/avg/max/mdev = 69.160/71.906/74.614/2.068 ms

Internet sharing only works when an IPv4 mobile internet connection is established on Xperia 10 III.

3 Likes
#22

Since this bug seems to appear in the x10ii and x10iii exclusively, it may be 64bit-related?
Just my 2 cent…

1 Like
#23

Thanks for the analysis. It makes a lot of sense that an IPv4 client can’t access the Internet via IPv6 gateway.

Should the device then do 4-to-6 magic? I vote for no, but providing an IPv6 address instead - with proper IPv4 and/or IPv6 routes given.

#24

Hi, on my Xperia 10 III the hotspot works (with O2) and VoLTE enabled.

#25

I agree with you. 4-to-6 voodoo where also not my favorit. But a hotspot with IPv4 and/or IPv6 support, depending on the mobile internet connection established, would be nice to see and one step ahead of Android.

Meanwhile I was able to fix the issue for myself and here is the summary of my experiences so far:

In my opinion, the fact that internet sharing only works with an ipv4 mobile data connection is not the actual problem.
By the way, Android also only relies on an existing IPv4 mobile data connection for Internet sharing.
But this behavior must be known so that the possible underlying problem can be identified.

In my case, the original problem was, that an IPv4 mobile data connection could not be established, which caused the following side effects I observed:

(The first two problems also occur if you normally can connect to a mobile IPv4 data connection, but your APN protocol is set to IPv6.)

For some, the missing IPv4 mobile connection might be the real reason why certain things related to mobile data are not working as expected. So maybe it’s worth paying attention to.

If there are one or more of the above mentioned problems then I recommend to check first if there is an IPv4 mobile data connection.
If not, then one should look into the APN settings if protocol is set to IPv6.
Is this the case then set it to DUAL.
If it is already set to DUAL, there might be a similar problem I had. Then a look into this bug report may be helpful:(IPv4 mobile data connection not possible)

Data counters not working for SIM
#26

Today i successfully used the hotspot with the 10 ii and VoLTE enabled. Using a German Vodafone SIM card, I had no problems (I did not check with congstar (Telekom) yet)

#27

Can I add a quick “me too” to this list? I’ve just tried using the hotspot functionality on my Xperia 10 III and have tried a number of devices connecting to its hotspot to no avail. I’m on Three (UK network) and have two sim cards with them, one a PAYG and one a Pay Monthly. Neither seem to allow me to hotspot correctly. Both sim cards allow the hotspot correctly in my Cosmo Communicator running Android so I guess it’s not a problem with the sim/provider.

I have set the APN settings protocol to DUAL (in fact they were already set as such) and have also tried the other two options just in case. I’m still unable to get hotspot functionality no matter what I set it to (Have also tried turning off and on VoLTE as a test to no avail).

If anyone has this working with Three please let me know!

EDIT: I changed the APN protocol to ‘IP’ and restarted the phone and it now seems to be working - hopefully that helps others!

1 Like
#28

Let me add another “me too”. I am experiencing exactly the same issues as describes by the original poster. (Xperia 10 III device, Sailfish OS 4.4.0.68, SIM from Congstar (German Telekom)). Mobile data access does not work at all with APN protocol set to “IP” with this provider.

Kernel module support 4.4 - on the phone
#29

Seems you are affected by this bug: IPv4 mobile data connection not possible

#30

Quick me too on this, it has worked in the past, but after a trip to Germany stopped working even after returning to Sweden. Phone (10 III 4.4.072) has connection, hotspot is connectable, but no internet on the laptop (Manjaro 5.19.16).

EDIT:
Changing the protocol from dual to IP and a reboot seems to work.

#31

Maybe this is the same issue as the roaming problem?
My hotspot works fine in.Germany with Vodafone Germany and dual ip v4 and v6.
Roaming did not work in Poland until I changed to ipv4.
Back again although hotspot is still working.

Setting your data access for mobile networks to ip solves some issues.

1 Like
#32

Yet another “mee too”! Again with the telekom-reseller “congster” on a 10 iii, no hotspot-internet-sharing possible, but the mobile-data-connection on the phone itself works fine :confused:
The same contract and SIM-Card worked fine in my old XA2 with the same SFOS 4.04… though.

#33
Hotspot not working in Xperia X II SalfilshOs 4.5.0.24
#35

I use my hotspot daily. Often, when I start the hotspot, I can tether but no internet connection. My workaround is:

  • Enable Airplane mode
  • Load Sailfish Utilities (install from Jolla store)
  • Restart network subsystem (click 2x for good measure)
  • Disable Airplane mode
  • Restart hotspot
  • Test browser connectivity on phone first

It almost always connects after I do this.

3 Likes
#36

Thanks for the information, but doesn’t work for me.

1 Like
#37

I have no problem at all using my Xperia 10 III as hotspot. Tested with Android 9 handy and Linux laptop. Vanha Rauma 4.4.0.72.

1 Like
#38

You are a so right! I forgot I also set “Mobile network / Data access point / Protocol” to “IP”. Not Dual or IPv6.

#39

Unfortunately that doesn’t work for me, respectively I couldn’t est it: My provider (german provider: Congstar) does not seem to accept “IP” as protokoll: In dual-mode the phone connects to the Internet (though: does not handle over the connection to the linked linux-computer), in IP-mode the phone doesn’t connect to the internet itself :frowning:
I cannot be the only person with this problem, any further hints ???

#40

Use sim slot 2
ipv4 is well supported… Not in sim slot1 (for me and other people wirh orange france provider)

1 Like