Replies: 1 comment
-
Consider changing the retransmission settings and possibly other timed events (e.g. DPDs, rekeyings) on the server so it doesn't remove the SAs while clients are offline. The client might not notice that as it does not send DPDs actively, so the server should be configured to only remove completely abandoned SAs so clients can be offline for a while. Also, check power settings etc. on the client so the Android system does not disable the network connectivity for the app or put the app to sleep prematurely. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I've been having some issues with the Android application.
It stops receiving packets from the gateway, but after the roadwarrior went offline (after trying for 5 retransmits), the sessions from the roadwarrior are seen on the firewall (from 11:01:25 12[IKE] sending keep alive to WAN_IP_STATIC[4500] in the rw_android.log).
The VPN is showing as still connected but not working. I've attached the rw_android.log
The app isn't set up to save energy.
My system:
Gateway:
Firewall OPNsense 24.1.6-amd64
FreeBSD 13.2-RELEASE-p11
OpenSSL 3.0.13
strongSwan 5.9.13
Roadwarior:
Xiaomi Poco F1 LineageOS 20
Android 13
strongSwan VPN Client 2.4.2 (the latest Version from F-Droid Store)
strongSwan 5.9.11
The configurations
swanctl.conf:
Logs
ipsec.log
rw_android.log
I've also tested with forced UDP encapsulation and without dead peer detection, but unfortunately I got the same result.
Could you help me out?
grEEtZ
Beta Was this translation helpful? Give feedback.
All reactions