Closed xmaxmex closed 1 year ago
@xmaxmex Hello! Please see Internal VPN IPs and traffic. When connecting using IPsec/XAuth ("Cisco IPsec") or IKEv2 mode, the VPN server does NOT have an internal IP within the VPN subnet 192.168.43.0/24
, so it is normal that you cannot ping 192.168.43.1
.
A ppp
interface is only created if using IPsec/L2TP mode to connect, but not for IPsec/XAuth ("Cisco IPsec") or IKEv2 mode. The Android strongSwan VPN client uses IKEv2 mode, so you won't see a ppp
interface in this case.
Checklist
Describe the issue A clear and concise description of what the bug is.
To Reproduce Steps to reproduce the behavior:
Expected behavior A clear and concise description of what you expected to happen.
Logs Check logs and VPN status, and add error logs to help explain the problem, if applicable.
Server (please complete the following information)
Client (please complete the following information)
Additional context Add any other context about the problem here.
Hi,
A have two vpn clients, one mikrotik side, its ok ppp0 and ip 192.168.42.10.
And android strongswan, with sswan file, just say connected!
But on Linux server, a ihave only one ppp0 ?
And only route to the ip 192.168.42.10
On Andorid exist a tun1 with ip 192.168.43.10
But on android i cant ping 192.168.43.1?
I can ping 192.168.43.10, tun1 inteface
And on Linux Server doesnt exist routes and a new ppp1 inteface ?
Any help?