If you have already done some devel-su over USB ssh the risk is about nil - there is no risk of a clat version bricking your phone that I can imagine. Of course, when one works as root and can destroy everything as super user, that’s one risk but the only one I can see. Probably your are familiar with the most of the below, sorry about that, but for the record (also for myself) I put here how I work to contribute back the logs Jussi may find helpful (he cannot get connected to our IPs), in no time:
Add the repository, only once, of course, until told to move to another repository - you can use clattest or whatever name you like:
ssu ar clattest <the URL link from @abranson latest post about new repository>
You want to remove it ? (at least before next Jolla’s update to the next official version)
ssu rr clattest
I keep the repo as long as there is no Jolla updates coming, it is stable enough.
After adding (or removing) the repository use pkcon (or zypper)
pkcon refresh
pkcon update
If you remove the repository and get back the original rpm’s one may need to force the downgrade, I did that once but found it too cumbersome, I just keep Jussi’s clat version(s) until it becomes official from Jolla.
I created, on my computer the following text file to memorize how to turn on Jussi’s required debug settings:
cat <<EOF >/etc/sysconfig/connman
SYSCONF_ARGS=-d plugins/clat.c -d src/connection.c -d src/inet.c -d src/service.c -d src/provider.c -d src/network.c -d plugins/vpn.c
EOF
mkdir -p /etc/systemd/journald.conf.d/
cat <<EOF >/etc/systemd/journald.conf.d/debug.conf
[Journal]
Storage=persistent
RateLimitIntervalSec=0s
RateLimitBurst=0
SystemMaxUse=100M
RuntimeMaxUse=2M
EOF
systemctl restart systemd-journald
systemctl restart connman
Just cut and paste the above to the command prompt.
To run the dump before you launch the connection / and during the connection to (like) http://ipv6-test.com or https://ipleak.net (not sponsored, I’ve been using these for some reason, there are others),
you would run, in one shell window (if vpn0 is the device name, it may change)
tcpdump -i vpn0 > vpn0.dump
and on another shell window
tcpdump -i clat > clat.dump
I noticed that most of the time, with VPN the clat device dump was empty. Or at times, the device is not there. Report this information, anyway.
And finally, you can copy the script as a bash-shell script from @abranson post (very first post in this thread) to collect the log files in an archive to post (not here but by e-mail to connman-debug@jolla.com - the dump-files without the log files are not enough. (You may want to change $(date +%Y%M%d_%H%M%S) with $(date +%Y%m%d_%H%M%S) for correct month - not a big deal if you don’t.)
To finish your debugging session and calm down the verbose logging, you can memorize, like it is done above the following commands to continue to use your phone normally:
rm -f /etc/sysconfig/connman
rm -f /etc/systemd/journald.conf.d/debug.conf
systemctl restart systemd-journald
systemctl restart connman
Of course, you can also reboot, but remove the configuration files with debug settings first.
.
while IPv6 still does. Looks better, thanks! I’ve sent you the dumps and logs by e-mail.