Just updated to 4.5.0.21 ot looks like the update hasn’t been applied?
4.5.0.21 update installs connman 1.32+git194-1.19.2 . Don’t know what it contains but it did not work for me - I restored (upgraded) from the test repository 1.32+git194.15-1.13.1 and now everything works as before. Maybe we need to just wait a bit more.
4.5.0.24 still installs connman 1.32+git194-1.19.2 - no CLAT update - VPN leaks (for some - see above). If you are using Jussi’s working CLAT solution, follow the procedure in Testing CLAT for IPv6-only mobile networks - #146 by canne to remove the test repository before the 4.5.0.24 update. After the update, follow the same procedure to reinstall the connman from the test repository in order to get rid off the VPN leaks if you have any. Humbly hoping that Jolla would accept Jussi’s connman PR.
@canne are you able to pin point Jussi’s connman PR that you’re referring to? See Pull requests · sailfishos/connman · GitHub
There’s some regression between 1.32+git194…1.32+git202 that should be sorted before promoting newer version to the public.
Cf. Testing CLAT for IPv6-only mobile networks - #168 by jlaakkonen, it says “The changes have now been merged and will be included in the next release” - so I would rather reformulate my wish : please integrate in the next release a connman version which contain the modifications of the PR [connman] Cleanup and fix index uses after CLAT VPN changes. Fixes JB#60897 by LaakkonenJussi · Pull Request #47 · sailfishos/connman · GitHub , thanks!
Hello all who’ve participated in CLAT testing before or are interested in this topic in particular. I’m very sorry that it has been a quite long wait for you but because of the ownership changes mentioned elsewhere on the forum we had a bit of downtime in general.
The CLAT VPN changes weren’t in the last release, unfortunately, and that is why I’d wish to ask your help again. Anyone willing to test how CLAT functions after some fixes done to issues that were detected in regular, i.e., non-CLAT use?
The very comprehensive instructions written by @canne in Testing CLAT for IPv6-only mobile networks - #146 by canne can be used still, just use this repository instead:
https://repo.sailfishos.org/obs/home:/jlaakkonen:/clat-new/aarch64/
It will contain a 1.32+git204 version of the most recent ConnMan that has some fixes on top of the previously mentioned git194. There was some issues that apparently during the waiting period for us has been lost from the internal tester’s minds but I did find at least one non-CLAT use related issue with mobile data:
- Right after boot and unlocking the device mobile data is a behaving a bit badly and needs a simple restart of mobile data to have IPv4 support back - I guess with CLAT this is of no issue ;). I’m thinking it is some sort of DHCP issue that I’m working on. EDIT: This seems to happen only on X10 III and only when SIM is put into slot 2.
But I’d be grateful if someone would see how this works with CLAT after some changes were made to internal index management to support the dual-index approach (per each ConnMan service, required by CLAT) better. I think that after installing this it is required to forcefully install any older version because of versioning checks, this can be done with (after disabling the repository as noted in the instructions):
pkcon --allow-downgrade <package>-<version>
or
zypper install --force <package>=<version>
After this week I’ll be back next year to check on the possible results anyone has had with this version. Same instructions on how to send the logs apply still.
Thank you all for all the help you’ve already given with this.
Welcome back! Meanwhile, your previous work has saved me (or at least my VPN). I will be roaming from the operator’s IPv6 country to a (sane) country with IPv4-only. Let’s see what happens!
Im testing from yestarday and seems my X10 III can be finally used as daily driver.
Mobile data works and suvives reboots, hotspot works. I can see 4G and mobile data icon!
OS version: 4.5.0.24
Does it make sense to try the changes if one did not have problems before?
I can run the packages and report if I got problems now.
Nice to hear! And thank you for testing.
Actually I just noticed that the issue reported in my previous post happens only on X10 III and only when the SIM is put into slot 2. It might be really an issue of the older Radio Interface we use on that device, since newer might not have that issue. I need to update the post.
Well if you want you can try the new version if you have the time and enthusiasm to help us in finding out potential issues. A wider testing will always be better, that is the version we’ve had on our internal testing and running on the development devices since summer but more testing, especially if you live in a country where CLAT is enabled will give more insight if there is something we should still fix.
You can always install the previous version back. We’ll up the version in one way or another before releasing ConnMan with the next release, so in that sense you can use this version until that happens.
Thank you! I’m glad it works still well. Hopefully this new one didn’t break anything but in that case I guess you have good position in evaluating if something went south with this one :).
Maybe it is too early to judge, but my impression is that since installing the latest connman version on my Xperia 10 III, my network connection is much more stable than before. This is especially true for Android apps which had complained about being offline most of the time before.
I will continue to watch the network’s behaviour in the next days, but for now I want to thank everyone who worked on fixing that issue.
Thank you for testing. I’m glad to hear that it even improves stability. Apparently nothing is broken then and this is good news and supports the decision to include the changes in the next release.
I am running the new lib now for a few weeks. I had no problem to fix, but it also does not seem to break anything.
Works fine when roaming, too. Escaping the operator terrorizing me with IPv6-only by driving over the frontier to an IPv4-wonderland with the help of PureMaps without never turning the phone off. Bulletproof operation both with VPN on or off. Gives the usual “SIM card has been changed, you need to reboot” strange message but I just shrugged it off and nothing bad happened in the IP-world. Production.
The new clat version is a huge improvement for me. Since installing this version i didn’t loose the interface anymore. Thank you!
I’m not so sure anymore. Now after some time I have to say that especially Android apps keep complaining about being offline more often than not.
Whenever that happens, a restart of Android app support is necessary to restore mobile network connectivity.
Can you describe that in what kind of situations these happen? Roaming or changing network types? Or after a long uptime of the device in general? There are many variables here and some error cases may originate from app support even. Without any logs it is difficult to tell but may I boldly assume that the situation is not at least worse than before?
There are no special circumstances in my case. No roaming, no unusual long uptime, no frequent App support restarts. Usually I avoid activating Wifi and use mobile data only (Telekom Germany), in order to avoid network switches.
This time even restarting Android app support didn’t help so far, so it may be related to a different issue now. Have to reboot tonight…
BTW, as described in another post, Whatsapp seems to be the only Android app with working network connectivity, all other apps are offline.