After saving this configuration, a dialog appears which asks for Username (4), the password of that user and the shared secret (3).
Thats it. Straigth forward. With this, I got a new configured VPN connection. But when I try to activate it, it loops forever trying to connect and runs into error. Over and over again.
Does anyone has done this before and had success? Any hints of what I am doing wrong is appreciated.
BTW: I use the settings direct from the Settings → VPN menu. No external app.
sfos version is 4.3.0.12
I have always looping error when saving a wrong password with vpn (not fritzbox, other vpn). The “solution” is to delete an re create the connection…
Might be other saved settings that do this…
Rather a workaround than a hint - I always put freetz on my fritzboxes in order to install an ordinary foss vpn server (e.g. OpenVPN or even Wire Guard is available). It’s easy to configure the client using .ovpn files then.
For the courageous, there is also OpenWRT available for some fritzboxes:)
Happy hacking!
It had it working long time ago with my old Jolla 1. Then I switched to my current XA2 and did not need it for some time. Now I wanted to configure it again and it just fails :-(. I tried to change the password with a simple one, just to be sure. No luck at all.
I am aware that there are more modern vpn solutions out there. But I was hoping to get it working again ‘out of the box’ ;-)…
Okay, did some debugging.
On the console, we can do a ps ax | grep connman-vpn and kill the pid. Then we can start it again with debug and stay on console enabled:
I have it working with my Xperia 10 II and the most recent Firmware (4.4). The Guide isn’t completely accurate anymore because it’s for an firmware version that had a different GUI. The differences are not that big and with a bit of experimenting you should get it to work. If i remember correctly package for Firmware 3.3 has nowadays the problem that it always forgets the password. and that there is no aarch64 package for the 64bit devices. Nokius has more recent builds in his repository that are working fine with firmware 4.4. I’m not sure if IPv6 might be a problem.
I wish you the best of luck to get it working on your side.
To sort out ipv6 issues, I tried to connect inside my local lan. The ipsec ports are also reachable not only from the outer internet. But also with this setup, no connection was possible.
Then I tried an old Android phone. The VPN connection worked almost on the first try. So, the FritzBox is setup correct.
I will stop trying to fix the issue in my SFOS version and will now update to the latest firmware first. Hopefully, after that the VPN connection will also work on my side…
I’m stucked here and wonder if there’s any way to debug this problem or know why it happens… could it be that sailfish can not resolve ipv6 addresses which my router uses?
I think the only solution is to connect only with ipv6 on the vpnc client so that ds-lite is not used. I’m not sure if this is possible but at least I hope this information guides someone with the right skills towards the solution.
After updating SFOS to 4.4.0.72, I tried again. Still no luck.
Then I followed the idea of @RosSigudottir . I checked out the trunk from vpnc and compiled that version. With the adapted configuration, described on that side, the connection to the Fritz Box instantly succeeds :-).
Interestingly, both vpnc binaries (the already installed one, and the fresh compiled one) report the same version of 0.5.3.
