Hello all - I was also recently trying to do a simple ipsec/l2tp vpn. I found that it works fine for everything except my android 5.1.1 device. The odd thing is that when I watch the log and/or isakmpd output I can see it connect fine, authenticate to l2tp and so on then it immediately disconnects and says that the client caused the disconnection. When I google I see all sorts of issues with android but mostly related to 6+. I can even see in the log that npppd successfully authenticates my android and creates a tunnel, android just kills it all after 1 second for some reason. Can anyone confirm that android 5.1.1 works with openbsd ipsec/l2tp before I spend more hours trying to figure out why just this android device is not working? Here is that tail of the log where l2tp is killed right after starting.
npppd[860]: ppp id=20 layer=base logtype=TUNNELSTART user="mike" duration=0sec layer2=L2TP layer2from=x.x.x.x:1701 auth=MS-CHAP-V2 ip=10.0.0.103 iface=pppx0 npppd[860]: ppp id=20 layer=base Using pipex=yes npppd[860]: ppp id=20 layer=lcp terminated by peer npppd[860]: l2tpd ctrl=21 RecvStopCCN result=GENERAL/1 error=none/0 tunnel_id=13671 message="" npppd[860]: l2tpd ctrl=21 call=12222 SendCDN result=ADMINISTRATIVE_REASON/3 npppd[860]: l2tpd ctrl=21 call=12222 logtype=PPPUnbind npppd[860]: ppp id=20 layer=base logtype=TUNNELUSAGE user="mike" duration=0sec layer2=L2TP layer2from=x.x.x.x:1701 auth=MS-CHAP-V2 data_in=213bytes,9packets data_out=219bytes,10packets error_in=0 error_out=0 mppe=no iface=pppx0 npppd[860]: l2tpd ctrl=21 Received CDN in 'cleanup-wait' state npppd[860]: l2tpd ctrl=21 logtype=Finished Justin -----Original Message----- From: owner-m...@openbsd.org [mailto:owner-m...@openbsd.org] On Behalf Of Raul Miller Sent: Tuesday, July 26, 2016 7:14 AM To: Maurice Janssen <maur...@z74.net> Cc: Steve Clement <st...@localhost.lu>; OpenBSD general usage list <misc@openbsd.org> Subject: Re: ispec - PSK - issues On Tue, Jul 26, 2016 at 2:08 AM, Maurice Janssen <maur...@z74.net> wrote: >>https://code.google.com/p/android/issues/detail?id=196939 > > Yeah, that's the link I wanted to send. Somehow I managed to copy the > wrong link in my previous email. I have been seeing a lot of copy&paste errors myself, where I performed the keyboard action to trigger a copy but paste gives me something from an older context. I'm sure a lot of people put a lot of time into making things work this way... -- Raul
