This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Cannot connect from Android 9.0 via L2TP PSK to UTM 9.7 ?

I'm using a Samsung Galaxy A8 running Android 9 and I'm unable to connect to my UTM 9.7 via L2TP PSK ...

 

During connecting it just hangs there and then display an error, yet it's all fine connecting from stock Windows 10 L2TP connection.
I am also pretty certain this has worked before, but it would've been an older Android firmware, as well as older UTM firmware ...

I've tried changing the 96 bit truncation but there was no change.

One solution is to switch to OpenVPN, but since L2TP is built-in to both Windows and Android it would be nice if it worked,
and it also makes things easier if you cannot for some reason install additional packages on a system, but need to remotely connect.

 

Here's the log file:

 

2019:10:16-14:51:57 user pluto[23277]: packet from FROM:500: received Vendor ID payload [RFC 3947]
2019:10:16-14:51:57 user pluto[23277]: packet from FROM:500: ignoring Vendor ID payload [draft-ietf-ipsec-nat-t-ike-02]
2019:10:16-14:51:57 user pluto[23277]: packet from FROM:500: ignoring Vendor ID payload [draft-ietf-ipsec-nat-t-ike-02_n]
2019:10:16-14:51:57 user pluto[23277]: packet from FROM:500: ignoring Vendor ID payload [draft-ietf-ipsec-nat-t-ike-00]
2019:10:16-14:51:57 user pluto[23277]: packet from FROM:500: ignoring Vendor ID payload [FRAGMENTATION 80000000]
2019:10:16-14:51:57 user pluto[23277]: packet from FROM:500: received Vendor ID payload [Dead Peer Detection]
2019:10:16-14:51:57 user pluto[23277]: "L_for user"[3] FROM #3: responding to Main Mode from unknown peer FROM
2019:10:16-14:51:58 user pluto[23277]: "L_for user"[3] FROM #3: NAT-Traversal: Result using RFC 3947: peer is NATed
2019:10:16-14:51:58 user pluto[23277]: | NAT-T: new mapping FROM:500/4500)
2019:10:16-14:51:58 user pluto[23277]: "L_for user"[3] FROM:4500 #3: Peer ID is ID_IPV4_ADDR: '192.168.1.80'
2019:10:16-14:51:58 user pluto[23277]: "L_for user"[4] FROM:4500 #3: deleting connection "L_for user"[3] instance with peer FROM {isakmp=#0/ipsec=#0}
2019:10:16-14:51:58 user pluto[23277]: "L_for user"[4] FROM:4500 #3: Dead Peer Detection (RFC 3706) enabled
2019:10:16-14:51:58 user pluto[23277]: "L_for user"[4] FROM:4500 #3: sent MR3, ISAKMP SA established
2019:10:16-14:51:58 user pluto[23277]: "L_for user"[4] FROM:4500 #3: ignoring informational payload, type IPSEC_INITIAL_CONTACT
2019:10:16-14:51:59 user pluto[23277]: "L_for user"[2] FROM:4500 #4: responding to Quick Mode
2019:10:16-14:51:59 user pluto[23277]: "L_for user"[2] FROM:4500 #4: IPsec SA established {ESP=>0x0d4323bb <0xe17c582b NATOA=0.0.0.0 DPD}
2019:10:16-14:52:57 user pluto[23277]: "L_for user"[4] FROM:4500 #3: received Delete SA(0x0d4323bb) payload: deleting IPSEC State #4
2019:10:16-14:52:57 user pluto[23277]: "L_for user"[4] FROM:4500 #3: deleting connection "L_for user"[2] instance with peer FROM {isakmp=#0/ipsec=#0}
2019:10:16-14:52:57 user pluto[23277]: ERROR: asynchronous network error report on eth0 for message to FROM port 4500, complainant FROM: Connection refused [errno 111, origin ICMP type 3 code 3 (not authenticated)]




This thread was automatically locked due to age.
Parents Reply Children
No Data