Hi, found a solution 2 years ago, I’ve never tried again and I have not idea if it still works, I think it’s worth checking this thread: VPN Connection to a Fritz Box - #10 by geobra
I just set up the FRITZ!Box VPN connection on my relative fresh flashed SFOS 4.6.0.15 on my Xperia 10 V and it worked immediately. What is the issue your having?
ifconfig shows that bytes are transmitted over vpn1, but none are received.
Pings to e.g. 192.168.0.1 (the router) fail.
When looking at “Connection details”, I see e.g.
Connection state:
...
Nameservers 192.168.0.1
Address 192.168.0.201/24
Netmask 255.255.255.0
Gateway ***.***.***.*** (actually here is the public IP address of the cable modem, which I find a bit strange)
Server route 192.168.0.0/255.255.255.00.0.0.0
Server route 0.0.0/0.0.0.00.0.0.0
Provider state:
WireGuard.Interface.Address 192.168.0.201/24
WireGuard.Interface.DNS 192.168.0.1
....
WireGuard.Peer.AllowedIPs 192.168.0.0/24,0.0.0.0/0
...
Confirmed. It should be as easy as configuring the VPN (IPSec) in the fritz.box and adding a VPNC connection in sailfish settings → VPN → VPNC. No openvpn, wireguard, replacing binaries or (if I recall) advanced options required.
I do remember the German site helping me with what to put where, it took me a few tries.
Seems that there are actually several causes to the problem: IPv4 change at the provider and lack of IPv6 capability of Sailfish’s VPN.
The provider has recently changed from public IPv4 addresses to CGNAT, so the IPv4 address is not reachable from publich internet any more.
It turned out that Selfhost’s DynDNS always returns the IPv4 address, even in IPv6 only mode.
Then, why does Sailfish’s Wireguard VPN display ‘connected’? Really great. Probably it displays “Connected” as soon as it gets an address from the DNS.
It’s also possible to create a MyFritz account, which includes DynDNS under the myfritz.net domain. No idea why AVM is not advertising this on the DynDNS config tab. You need to activate the checkbox that the FritzBox should be reachable from internet.
I have checked Wireguard from an Android device to verify that the connection using this name is working.
Also, from Sailfish I can ping the FritzBox using the myfritz.net subdomain name.
With IPv6 Sailfish Wireguard connects to the Fritz Box, but reports “Problem with connection”. Really great…
(I can see from the FritzBox admin page that the connection was made.)
So, continue with IPSEC and IPv6:
With the standard settings, there is still “Idle → Connecting → Problem with connection”.
With Gateway vendor “Cisco”, Mode for IKE “PSK”, NAT traversal mode “Enforce NAT-T” as noted on the mentioned page: still the same failure.
With the vpnc rpm from Nokius and after a re-boot still the same.
After creating a .conf file and running vpnc from the command line, I get ‘vpnc: unknown host …myfritz.net’
I get the same result if I enter the IPv6 address instead of the myfritz subdomain name.
Double check: I can still ping the FritBox from the internet.
While IPSEC/VPNC and IPv4 “just work”, I found it impossible to connect using the FritzBox IPv6 address, on both Sailfish and android.
Copying the IPv6 address to firefox between http://[], both devices show the FritzBox login.
Brackets [] in the VPN config make no difference.
Changing the IPv6 address to IPv4, both devices set up a vpn connection.
My only advice right now is: focus on Wireguard. Since you got it to connect and get some logging in the FritzBox that means someting. (I never saw my IPv6 connection attempts logged.) You might end up having “just a routing issue”.
I might experiment with it once I get the C2 but I don’t feel like messing with my “production device”.
Thanks. I have commented/asked on OpenRepos. Hopefully one of the Wireguard implementations will finally work with IPv6. I would have expected that IPv6 is state of the art by now…
