IssueTracker

Although VPN connections under Android 7.1.2 worked for me, they do not work under Android 8.0.0 anymore. (IPSec Xauth PSK)

Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:

Steps to reproduce
What steps are needed to reproduce this issue?

Frequency
How frequently does this issue occur? (e.g 100% of the time, 10% of the time)

Expected output
What is the expected output?

Current output
What is the current output?

Android bug report
After reproducing the issue, press the volume up, volume down, and power button simultaneously. This will capture a bug report on your device in the “bug reports” directory. Attach the bug report  file to this issue.

Alternate method:
After reproducing the issue, navigate to developer settings, ensure ‘USB debugging’ is enabled, then enable ‘Bug report shortcut’. To take bug report, hold the power button and select the ‘Take bug report’ option.

Please provide the information requested in comment #2 to investigate further.

Please provide the information requested in comment #3 to investigate further.

Hi I Am experiencing the same issues as mentioned by the topic starter. I've tried to create a bug report, but i haven't rooted my device. However, i have attached the log of my VPN-router below.

Steps to reproduce
Configure a L2TP / IPsec PSK VPN using the native VPN client on Android 8 and try to connect

Frequency
Issue occurs 100% of the time.

Expected output
Connected to VPN

Current output
Message that connection failed.

Router log (IP-ADRES = the IP address of the Android)

2017-10-20 13:12:21     [IPSEC/IKE][Local][66:-][@IP-ADRES] may be security method/sbunet setting/GRE setting unmatched?
2017-10-20 13:12:21     [IPSEC/IKE][Local][66:-][@IP-ADRES] state transition fail: STATE_QUICK_R0
2017-10-20 13:12:19     sent MR3, ISAKMP SA established with IP-ADRES. In/Out Index: 66/0
2017-10-20 13:12:19     Matching General Setup key for dynamic ip client...
2017-10-20 13:12:19     NAT-Traversal: Using RFC 3947, no NAT detected
2017-10-20 13:12:19     Accept Phase1 prorosals : ENCR OAKLEY_AES_CBC, HASH OAKLEY_SHA
2017-10-20 13:12:19     Matching General Setup key for dynamic ip client...
2017-10-20 13:12:19     Find Phase1 proposal: SHA2_256
2017-10-20 13:12:19     Matching General Setup key for dynamic ip client...
2017-10-20 13:12:19     Find Phase1 proposal: SHA2_256
2017-10-20 13:12:19     Matching General Setup key for dynamic ip client...
2017-10-20 13:12:19     Matching General Setup key for dynamic ip client...
2017-10-20 13:12:19     Responding to Main Mode from IP-ADRES

Thanks for looking into this and good luck!

Steps to reproduce:
1. Setup VPN connection using IPSec Xauth PSK with IPSec key
2. Connect to VPN server
3. Connection attempt will fail

Frequency
100%

Expected output
Connect to VPN server successfully

Current output
Connection attempt fails

It works for me but only "non-permanent".

As soon as I actvate "permanent" it cant connect... like in 6.x and 7.x (now 8.0.0)

oh sry... its "Always On" in english version

Reply comment #7:
Can you please check whether issue is reproducible with latest Android 8.1.0 build(OPM1.1171019.011) for Pixel device?
If issue is still reproducible, please capture a bugreport and share it here.

Issue still reproducible with Android 8.1.0 build(OPM1.1171019.011) on Pixel device.

Could fix this issue now by removing the whole VPN user account and create a new one. Now the connection works again. As I'm not sure if I tried that with an earlier Android version I can only say that there must be at least an issue with my VPN system (AVM Fritz!Box 7490).

For anyone having similar issues, see my recent comments here https://issuetracker.google.com/issues/37074640#comment366
I'm curious if these are related or if my case is unique. If possible run 'ifconfig' on the device while trying to connect and compare the MTU of the ppp0 interface with that of your main wifi/LTE interface

Thank you for your feedback. We assure you that we are doing our best to address the issue reported, however our product team has shifted work priority that doesn't include this issue. For now, we will be closing the issue as won't fix obsolete. If this issue currently still exists, we request that you log a new issue along with latest bug report here https://goo.gl/TbMiIO.