Fixed
Status Update
No update yet.
Comments
ve...@google.com
ve...@google.com
Information redacted by Android Beta Feedback.
ma...@gmail.com
redacted
ve...@google.com
Thank you for reporting this issue. We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
ch...@futurescope.co.uk
ch...@gmail.com
I have turmux
ti...@gmail.com
Unfortunately, the issue isn't solved in beta 2.1 despite the changelog saying it is :-(
yv...@load-it.com
This issue is still persisting in the Android 15 public beta 1 as well.
ch...@gmail.com
Thank you for reporting this issue. We have a fix rolling out in the next release.
yv...@load-it.com
New update
ch...@gmail.com
Oppo
ma...@gmail.com
The issue returned in Android 15 Beta 2
yv...@load-it.com
Android 15 beta 2.. issue persists
ma...@gmail.com
Yes, issue persists
Build number AP31.240426.023
Build number AP31.240426.023
ma...@gmail.com
Issue definitely still persisting :/
yv...@load-it.com
We detected a new issue
ch...@gmail.com
Still not resolved with Android 15 beta 2.2 :-(
yv...@load-it.com
Didn't have issue with beta 2.1. Now issue has returned. Android version AP31.240426.023.B4.
ch...@gmail.com
deleted
k....@gmail.com
Pixel 3 to L2TP to both Meraki and UBNT USG connects fine but stops passing traffic after 60-80 seconds.
Please help.
Please help.
br...@gmail.com
Agree, having same issue with UBNT. Disconnects after 90 seconds like clockwork from Pixel 3.
ka...@karlquinsland.com
I am having the same issue with a bog-standard Lt2p/IPSEC config.
I have an OSX 10.14.4 (latest public build as of 2019-01-28) client and a Pixel 3 XL running the PQ1A.190105.004 Build (latest public build as of 2019-01-28).
I can not get my L2TP connection to keep connected for more than about 90 seconds. The exact same configuration on the OSX client has been stable for upwards of 6+ hours, now.
I have an OSX 10.14.4 (latest public build as of 2019-01-28) client and a Pixel 3 XL running the PQ1A.190105.004 Build (latest public build as of 2019-01-28).
I can not get my L2TP connection to keep connected for more than about 90 seconds. The exact same configuration on the OSX client has been stable for upwards of 6+ hours, now.
pi...@gmail.com
Same here. It's android 9... Huawei P20 in my case, same scenario.
ch...@gmail.com
@google: still no update in this issue?
Do you want us to move to a more realible (professional) OS?
Do you want us to move to a more realible (professional) OS?
ad...@gmail.com
I have a Google Pixel 3 XL and I am also encountering VPN dropouts when connected to a Ubiquiti Unifi USG (Universal Security Gateway). I do not encounter the dropouts on a Pixel 2 or a Surface Pro 4.
do...@gmail.com
Pixel 3 XL here. Cisco Meraki MX with L2TP drops out after about 90 seconds.
he...@gmail.com
pixel 3 here and l2tp connection drop after about 90 seconds. same config on Chromebook works flawlessly.
had an essential phone before and even with Android 9 this device works as expected. no l2tp connection drop
had an essential phone before and even with Android 9 this device works as expected. no l2tp connection drop
jz...@gmail.com
Same for me too.
p....@gmail.com
Same here...Android 9 on a Honor 10 (9.0.0.162(C432))
ma...@gmail.com
Same issue here.... Pixel 2XL on Android Pie Feb update.
si...@gmail.com
Same on pixel 3 xl
th...@gmail.com
Yep ... Android 9 in Huawei P20 Pro
pi...@gmail.com
Can't believe there's no solution from Google yet to this...
ch...@gmail.com
No solution - not even any official comment!
dz...@dzeni.com
same here. had to revert to pptp :(
ch...@gmail.com
due to PPTP being insecure it should not been considered a valid "workaround"
br...@gmail.com
I changed to sstp :( and openvpn pocophone.
th...@gmail.com
Can't believe but update 9.0.0.195 (C432E5R1P9) released a few days ago on my Huawei P9 pro seems to fix this. No disconnect for hours.
k....@gmail.com
Just received February update on Pixel 3 (build PQ2A.190205.001) - VPN dropped after 80 seconds, so not fixed on Pixel 3 yet.
th...@gmail.com
I ment P20 Pro, not P9 :-)
yv...@load-it.com
Same here Huawei Mate 20 Pro with the newest Update 9.0.0.187 works again on IPSec. But I already setup a OpenVPN server as workaround.
si...@gmail.com
Same issue with Pixel 3 XL. Connects to Meraki L2TP vpn. Stops passing traffic at 45seconds, drops the connection around 6 minutes. Been trying to work with support since the phone came out to no avail.
mt...@gmail.com
Same problem, Pixel 3 + USG Pro 4
br...@gmail.com
Google Pixel 3 XL Android 9 Builod PQ2A.190305.002 still drops connection after 90 seconds
ch...@gmail.com
Still dropping out running on March update
za...@gmail.com
Still occurring on Pixel 3XL running the Verizon March Update (Build # PQ2A.190305.002). VPN is a Unifi USG router L2TP. Connection starts and works for the first 60-90 seconds, but then drops out.
in...@gmail.com
Even with the combination of YAMAHA RTX1200 and Pixel 3, the VPN tunnel with L2TP/IPsec goes down in 90 seconds.
It is possible to connect with other Android devices such as Xperia XZ1 without problems, but problems only occurred with Pixel 3.
Google Pixel 3 support in Japan answered only to wait for OTA correction without even requesting logs.
It is possible to connect with other Android devices such as Xperia XZ1 without problems, but problems only occurred with Pixel 3.
Google Pixel 3 support in Japan answered only to wait for OTA correction without even requesting logs.
mi...@gmail.com
same issue here on Pixel 3 connecting to UnFi EdgeRouter X.
bu...@gmail.com
I believe this is due to Pixel 3 not responding to L2TP keepalive packets.
bu...@gmail.com
Sorry for spamming, I submitted the comment too soon.
Based on my findings - Pixel 3 and 3XL has a bug with L2TP implementation.
The phone was capable of establishing the connection, however the phone does not seem to respond to L2TP keepalive heartbeat, which causes L2TP connection to be marked as disconnected by the VPN server after a predefined amount of time.
The IPSec tunnel however, remains up, and therefore the phone does not recognise the VPN connection as disconnected.
Attached is the server log that I posted to xda a while back.
Based on my findings - Pixel 3 and 3XL has a bug with L2TP implementation.
The phone was capable of establishing the connection, however the phone does not seem to respond to L2TP keepalive heartbeat, which causes L2TP connection to be marked as disconnected by the VPN server after a predefined amount of time.
The IPSec tunnel however, remains up, and therefore the phone does not recognise the VPN connection as disconnected.
Attached is the server log that I posted to xda a while back.
ch...@gmail.com
Got an update for Google connectivity services app.
Still dropping out after 90 sec
Still dropping out after 90 sec
br...@gmail.com
Move to ipsec ikev2 and external app strongswan since google does not care.!!!!!
ma...@gmail.com
Yeah, the lack of any support at all for "Enterprise" level features is pretty staggering.
ax...@gmail.com
Also NOT working on my Pixel 3, but it DOES work perfectly on my original Pixel. Using L2TP from my Unifi USG.
mi...@gmail.com
Has there been any word from the Android or Pixel team as to an official reason for this issue and when we can expect a resolution?
ro...@gmail.com
I'm running the Android Q beta on my Pixel 3 XL and L2TP is working perfectly for me now, it didn't work for me on Pie. Version information in attached screenshot if that's helpful.
mi...@gmail.com
Q also resolved this for me.
[Deleted User] <[Deleted User]>
Huawei P10, Android 9.0.1
VPN IPsec on FRITZ!Box 7590, always on active on the android device
Unstable connection, after ~2 minutes the vpn refresh itself but not responding often. Sometimes freeze phone for ~1 minute. With Android Oreo I didn't have this problem.
VPN IPsec on FRITZ!Box 7590, always on active on the android device
Unstable connection, after ~2 minutes the vpn refresh itself but not responding often. Sometimes freeze phone for ~1 minute. With Android Oreo I didn't have this problem.
ch...@gmail.com
installed April '19 Uupdate today => issue still persists
@Google: are you f**king kidding us?!
@Google: are you f**king kidding us?!
bu...@gmail.com
Still encountering this issue after april update.
This feature never worked on Pixel 3 XL and it's been almost half a year since the phone was launched. I've submitted numerous feedback to Google and never heard anything, can we get someone from Google to work on this please.
This feature never worked on Pixel 3 XL and it's been almost half a year since the phone was launched. I've submitted numerous feedback to Google and never heard anything, can we get someone from Google to work on this please.
bj...@gmail.com
Same Problem here with Nokia 8 (Android 9) and Google Pixel XL (Android 9), after ~2 minutes it disconnects...
fa...@gmail.com
Same problem Pixel 3 (Android 9 April security patch level)
fr...@gmail.com
If you look at the blocked by at the top of the page it shows there's another non-public issue blocking this one, probably some bigger deal that it appears at face value.
That said, still doesn't work today on my fully updated 3XL.
That said, still doesn't work today on my fully updated 3XL.
br...@gmail.com
I'm Beta testing Android Q and VPN is working great. I once left it
connected for 6 hours with no issues. Why they're not fixing V9 makes no
sense to me.
On Sun, Apr 14, 2019 at 4:51 PM <buganizer-system@google.com> wrote:
connected for 6 hours with no issues. Why they're not fixing V9 makes no
sense to me.
On Sun, Apr 14, 2019 at 4:51 PM <buganizer-system@google.com> wrote:
al...@gmail.com
Same issues with Pixel 3. After 1-2 minutes, it is connected, but traffic doesn't pass.
cr...@gmail.com
Same issue on my Pixel 3 using L2TP/IpSECv1. After 1-2 minutes, stops passing traffic.
ti...@gmail.com
Same issue on my Pixel 3 using L2TP/IpSECv1. After 1-2 minutes, stops passing traffic.
jr...@gmail.com
Same issue with Pixel 3 and Meraki IPsec VPN, stays connected, can't access network
fr...@gmail.com
Another monthly update just installed today, still not staying connected. This is pretty basic feature to have broken for so long, come on Google!
br...@gmail.com
I guess the good thing is that it works in 'Q'. I'm Beta testing now. Too
bad this is how you have to solve something.
On Thu, May 9, 2019 at 12:34 AM <buganizer-system@google.com> wrote:
bad this is how you have to solve something.
On Thu, May 9, 2019 at 12:34 AM <buganizer-system@google.com> wrote:
da...@gmail.com
Same problem, L2TP/IPSec-PSK disconnecting on new 3a XL on Google Fi w/ eSIM.
ICMP ping and SSH into a PC through the tunnel works fine until disconnect.
HTTPS to site running on same PC provides I get Chrome on phone to produce untrusted certificate error immediately, but continuing on to load page never works and eventually tunnel drops out.
Same problem occurs whether forcing connection to T-Mobile or Sprint as carrier.
No problems staying connected before service switched over from previous phone, Nexus 6P w/ Android 8.
Pixel 3a line won't get access to Q beta until June according to the beta web page.
ICMP ping and SSH into a PC through the tunnel works fine until disconnect.
HTTPS to site running on same PC provides I get Chrome on phone to produce untrusted certificate error immediately, but continuing on to load page never works and eventually tunnel drops out.
Same problem occurs whether forcing connection to T-Mobile or Sprint as carrier.
No problems staying connected before service switched over from previous phone, Nexus 6P w/ Android 8.
Pixel 3a line won't get access to Q beta until June according to the beta web page.
vi...@gmail.com
Honor10 android 9.0 issue with l2tp, disconnecting after 90 seconds.
st...@gmail.com
Xiaomi Mi Mix 2S Android 9.0 VPN L2TP, disconnected after 90 seconds.
th...@gmail.com
Xiaomi Mi Mix 3 Android 9 L2TP VPN disconnects after 90 seconds. Windows 10 machine no issues connection lasts indefinitely.
jo...@googlemail.com
Google Pixel 3 XL Android V9 L2tp VPN disconnects after short period (less than a minute). Sort this out or i'll never purchase another google product, this is absolutely ridiculous.
fr...@gmail.com
Just got the June update and this is still an issue on pixel 3 xl
ch...@gmail.com
My guess they will never fix this in Android 9 nor they will ever reply on this issue in this tracker!
th...@gmail.com
I have a Pixel 3aXL Android 9. Got it about a month ago. Using a TPLink router with L2TP. My phone has the same issue. It won't stay connected for more than 90 seconds. Pretty sad, It works on my Moto X pure with Android 7.1.
Pretty sad that Google won't fix this...
Pretty sad that Google won't fix this...
md...@gmail.com
Google Pixel 3a Android 9.0 VPN L2TP, disconnected after 90 seconds.
he...@gmail.com
it works in android 10 so also think they never fix it for 9....
ma...@gmail.com
I've given up waiting.
I setup an OpenVPN server, installed "OpenVPN for Android" and I'm really
impressed.
Fast, easy and super stable.
Should've done this ages ago.
I setup an OpenVPN server, installed "OpenVPN for Android" and I'm really
impressed.
Fast, easy and super stable.
Should've done this ages ago.
he...@gmail.com
l2tp VPN worked in android q beta until beta 5. the latest beta has got
this same bug. wtf Google!
I already filed a bug report.... very pissed!
Op di 2 jul. 2019 06:39 schreef <buganizer-system@google.com>:
this same bug. wtf Google!
I already filed a bug report.... very pissed!
Op di 2 jul. 2019 06:39 schreef <buganizer-system@google.com>:
ad...@adamjobbins.com
Damn! I waited for Beta 5 so I was installing something relatively stable. Just installed it :/
ch...@gmail.com
DAFUQ?!?!
@82: have you got any feedback on your bug report until now? Can you share the issue ID to publish in available forums like ubnt?
@82: have you got any feedback on your bug report until now? Can you share the issue ID to publish in available forums like ubnt?
st...@gmail.com
fr...@gmail.com
still broken on pixel 3 xl after installing August update
ch...@gmail.com
@all: fot those running the beta - have you tried testing the latest beta build released today?
Hope it'll be working again...
Hope it'll be working again...
he...@gmail.com
br...@gmail.com
Okay now, I went to Android 'Q' in part so this would work. Now they break
it in 'Q'./ What the heck????????
On Wed, Aug 7, 2019 at 4:02 PM <buganizer-system@google.com> wrote:
it in 'Q'./ What the heck????????
On Wed, Aug 7, 2019 at 4:02 PM <buganizer-system@google.com> wrote:
ch...@gmail.com
so google fixed it in prior beta release and fucked it up again in the latest betas... GREAT!
In conclusion they give a shit on this and want us to leave. No problem on iOS - I never faced an issue with l2tp
Not yet any reply from google.. Shame on you!!!!
In conclusion they give a shit on this and want us to leave. No problem on iOS - I never faced an issue with l2tp
Not yet any reply from google.. Shame on you!!!!
ad...@adamjobbins.com
Yesterday I received an update via the Play Store for "Google Connectivity Services" which listed in the release notes:
"Improved connection reliability when VPN is up", however a quick test resulted in a disconnect at 90 seconds still, so unfortunately that did not fix it :(
"Improved connection reliability when VPN is up", however a quick test resulted in a disconnect at 90 seconds still, so unfortunately that did not fix it :(
ch...@gmail.com
@Google: what about this
But NO access on this...
But NO access on this...
zo...@gmail.com
Continued plauge.. may a fix be designed soon!
st...@gmail.com
Ftf Google ? And fixe the Wear OS. Also.
he...@gmail.com
updated to final android q.
guess what?
it works! NOT.... what the f*cking f*CK Google!
It never worked for Pie and now Q! bigggg shame for you
Op za 31 aug. 2019 15:15 schreef <buganizer-system@google.com>:
guess what?
it works! NOT.... what the f*cking f*CK Google!
It never worked for Pie and now Q! bigggg shame for you
Op za 31 aug. 2019 15:15 schreef <buganizer-system@google.com>:
ch...@gmail.com
Was expecting it will not work on Q/10.
Google will give a pure shit on this. If they would there would be any answer on all those issues raised. But there's none...
On any mobile OS there's no issue with L2TP. One suggestion is to go back to PPTP - NO!!!! WAY! Other one is rebuilding entire network setup - are you seriously stupid?!?
I will sadly switch OS when my current phone is due
Google will give a pure shit on this. If they would there would be any answer on all those issues raised. But there's none...
On any mobile OS there's no issue with L2TP. One suggestion is to go back to PPTP - NO!!!! WAY! Other one is rebuilding entire network setup - are you seriously stupid?!?
I will sadly switch OS when my current phone is due
jr...@gmail.com
So I guess it's time to switch to Apple products.
he...@gmail.com
hell no going back to Apple. came from there. not going back!
Op di 3 sep. 2019 21:30 schreef <buganizer-system@google.com>:
Op di 3 sep. 2019 21:30 schreef <buganizer-system@google.com>:
se...@gmail.com
Having the same issue on my pixel 3xl on android 10. Please resolve this issue!!!
do...@gmail.com
How is it possible that only 123 people have starred this issue. Google needs to quit ignoring this issue.
br...@gmail.com
I've never seen an issue so easy to fix be ignore for so long. I say "easy
to fix" because until the last Beta build it was working. Looking at that
code and seeing what changed to cause this is an easy task for a
programmer. They obviously do not care if this works or not.
Sent from Brad's Pixel 3 XL
On Wed, Sep 4, 2019, 2:32 AM <buganizer-system@google.com> wrote:
to fix" because until the last Beta build it was working. Looking at that
code and seeing what changed to cause this is an easy task for a
programmer. They obviously do not care if this works or not.
Sent from Brad's Pixel 3 XL
On Wed, Sep 4, 2019, 2:32 AM <buganizer-system@google.com> wrote:
lu...@hotmail.com
Was really looking forward to installing Android 10 because it was finally working again in the early betas. Couldn't believe my eyes when the issue still occurred and I come to learn you guys broke it again between betas.
Stuck with you guys after my Pixel randomly just died this year, but this is really stretching that faith.
Stuck with you guys after my Pixel randomly just died this year, but this is really stretching that faith.
[Deleted User] <[Deleted User]>
well thanks to all of google's ignoring of a very important issue I am now
an iPhone user and I despise you for that
On Thu, 5 Sep 2019 at 14:30, <buganizer-system@google.com> wrote:
an iPhone user and I despise you for that
On Thu, 5 Sep 2019 at 14:30, <buganizer-system@google.com> wrote:
--
*Dave HirstSenior Network Administrator*
T: +44 (0) 1302 731537
M: +44 (0) 7341 098566
[image: IPv6 Certification Badge for Hirstdave][image: Image result for
CCNP certification][image: Image result for RIPE NCC Academy]
--
Registered Office:
Unipart Rail Limited, Unipart House, Cowley, Oxford, OX4 2PG Registered in
England and Wales: Registered No. 3038418
This e-mail has been sent in
confidence to the named addressee(s). If you are not the intended
recipient you must not disclose or distribute it in any form, and you are
asked to contact the sender immediately
jr...@gmail.com
So pixel 2 is offering to upgrade to Android 10.
Has anyone tested Pixel 2 under 10 and VPN?
Has anyone tested Pixel 2 under 10 and VPN?
bl...@gmail.com
I have a Pixel 3XL that I just updated to Android 10.
It still has the same issue, connects to VPN and passes traffic for 30-60 seconds, then dies.
It still has the same issue, connects to VPN and passes traffic for 30-60 seconds, then dies.
[Deleted User] <[Deleted User]>
it will continue to have this issue until google start to take this
seriously
so as an FYI I have demanded and received a full refund for the Pixel 3XL
that was useless since I bought it due to this
I sincerely advise you all to do the same if we start costing them money
they might start taking this problem seriously
On Wed, 11 Sep 2019 at 14:23, <buganizer-system@google.com> wrote:
seriously
so as an FYI I have demanded and received a full refund for the Pixel 3XL
that was useless since I bought it due to this
I sincerely advise you all to do the same if we start costing them money
they might start taking this problem seriously
On Wed, 11 Sep 2019 at 14:23, <buganizer-system@google.com> wrote:
--
*Dave HirstSenior Network Administrator*
T: +44 (0) 1302 731537
M: +44 (0) 7341 098566
[image: IPv6 Certification Badge for Hirstdave][image: Image result for
CCNP certification][image: Image result for RIPE NCC Academy]
--
Registered Office:
Unipart Rail Limited, Unipart House, Cowley, Oxford, OX4 2PG Registered in
England and Wales: Registered No. 3038418
This e-mail has been sent in
confidence to the named addressee(s). If you are not the intended
recipient you must not disclose or distribute it in any form, and you are
asked to contact the sender immediately
vo...@gmail.com
I would encourage everyone to submit their bug report as suggested in https://issuetracker.google.com/issues/118789580#comment2 )
Aalso, make sure you only share it with android-bugreport@google.com before you post the link, that report will contain a lot of info.
I opened up the description.txt file on my laptop and put in the full text from my VPN server showing the server side messages.
My bug report:https://drive.google.com/file/d/1G4tV3eE65zmbM_BszaSHKIyEFpNDkCA6/view?usp=sharing
Aalso, make sure you only share it with android-bugreport@google.com before you post the link, that report will contain a lot of info.
I opened up the description.txt file on my laptop and put in the full text from my VPN server showing the server side messages.
My bug report:
br...@gmail.com
They are totally ignoring everyone and every post. Very unprofessional to
flat out ignore people. If you don't plan to fix it, step up and be honest.
Why they broke it in the first place is a mystery. All but the last cut if
Beta firmware for 'Q' worked without issue. Then the last Beta drop they
broke it. Almost as if they started rolling things over from Android Pi
just before the official release. It would only take one engineer less that
and hour to identify this and possibly even resolve it.
Sent from Brad's Pixel 3 XL
On Wed, Sep 11, 2019, 10:26 AM <buganizer-system@google.com> wrote:
flat out ignore people. If you don't plan to fix it, step up and be honest.
Why they broke it in the first place is a mystery. All but the last cut if
Beta firmware for 'Q' worked without issue. Then the last Beta drop they
broke it. Almost as if they started rolling things over from Android Pi
just before the official release. It would only take one engineer less that
and hour to identify this and possibly even resolve it.
Sent from Brad's Pixel 3 XL
On Wed, Sep 11, 2019, 10:26 AM <buganizer-system@google.com> wrote:
br...@gmail.com
They are totally ignoring everyone and every post. Very unprofessional to
flat out ignore people. If you don't plan to fix it, step up and be honest.
Why they broke it in the first place is a mystery. All but the last cut if
Beta firmware for 'Q' worked without issue. Then the last Beta drop they
broke it. Almost as if they started rolling things over from Android Pi
just before the official release. It would only take one engineer less that
and hour to identify this and possibly even resolve it.
Sent from Brad's Pixel 3 XL
On Wed, Sep 11, 2019, 10:26 AM <buganizer-system@google.com> wrote:
flat out ignore people. If you don't plan to fix it, step up and be honest.
Why they broke it in the first place is a mystery. All but the last cut if
Beta firmware for 'Q' worked without issue. Then the last Beta drop they
broke it. Almost as if they started rolling things over from Android Pi
just before the official release. It would only take one engineer less that
and hour to identify this and possibly even resolve it.
Sent from Brad's Pixel 3 XL
On Wed, Sep 11, 2019, 10:26 AM <buganizer-system@google.com> wrote:
in...@gmail.com
I had this issue on my Pixel 3 on Android 9 and it continues to occur after the Android 10 OTA update. Bug report is here:
https://drive.google.com/folderview?id=10d5KgyR9FP1Jk1BN04-Y_qwccfVYLFN2
ja...@gmail.com
I have the same problem on Android Pie. Pixel 3 XL disconnects after 90 secs. I have testet flashing factory image and did not solve problem. Running latest Android 10.
LG G6 and Windows 10 connects and stays connected.
LG G6 and Windows 10 connects and stays connected.
ho...@gmail.com
So in my case I have been suffering with the bug the same as everyone else, but I just got the Android 10 update and so far I haven't been able to get a connection at all. At least I had 90 seconds before.
nx...@gmail.com
Running Android 10 on my pixel 3a and have the reported issues
jr...@gmail.com
Upgraded my Pixel 2 to Android 10.
VPN still working.
So it looks like this is an issue of Pixel 3 & 3a (XL versions as well).
VPN still working.
So it looks like this is an issue of Pixel 3 & 3a (XL versions as well).
ma...@gmail.com
It will be interesting to see if it remains an issue on the Pixel 4 then!
[Deleted User] <[Deleted User]>
you mean after this S*it Show you would even consider buying another Pixel
my god google must have done a number there
I'd Buy an iPhone before a pixel now and I would never buy an iPhone
On Thu, 19 Sep 2019 at 09:22, <buganizer-system@google.com> wrote:
my god google must have done a number there
I'd Buy an iPhone before a pixel now and I would never buy an iPhone
On Thu, 19 Sep 2019 at 09:22, <buganizer-system@google.com> wrote:
--
*Dave HirstSenior Network Administrator*
T: +44 (0) 1302 731537
M: +44 (0) 7341 098566
[image: IPv6 Certification Badge for Hirstdave][image: Image result for
CCNP certification][image: Image result for RIPE NCC Academy]
--
Registered Office:
Unipart Rail Limited, Unipart House, Cowley, Oxford, OX4 2PG Registered in
England and Wales: Registered No. 3038418
This e-mail has been sent in
confidence to the named addressee(s). If you are not the intended
recipient you must not disclose or distribute it in any form, and you are
asked to contact the sender immediately
th...@gmail.com
Pixel 3 XL on the project Fi network and also having the same issue as reported here.
ch...@gmail.com
Just installed the latest unplanned Android update.
Still fucked up.
Still fucked up.
[Deleted User] <[Deleted User]>
I have Returned my Pixel 3 XL and received a Full £799 refund I would suggest you all do the same. it is the only way you will get any resolution Google clearly is not interested in fixing this they have proved that by it taking 18 months and doing nothing when on a routed Pixel 3 we fixed it in under 2 days its actually quite easy todo its 2 lines of code so realy get your money back ASAP as google is taking the piss
ti...@gmail.com
I found out that my IPsec configuration also supports Xauth, which works perfectly for my needs. Anybody still facing this issue, is IPsec Xauth a valid solution or does your VPN provider (a Linux box in my case) not provide it?
[Deleted User] <[Deleted User]>
Xauth while it works missis the point this is an issue that can be fixed easily if google could be bothered but they have your money so they don't care get your refund hit them in the banck account and they might (they probably won't but you will have your money) and get a phone that works not one you have to work round
jo...@gmail.com
Running Android 10 on pixel 3a and have the same issue.
mi...@gmail.com
Android 10 - pixel3 - same issue
he...@gmail.com
had high hopes seeing an update in the play store about Google connection
services and better VPN support.
well again. it is NOT working
there is one person who made it work using rooted pixel. can you share the
code?
or at least make a pull request on AOSP?
Op zo 29 sep. 2019 05:18 schreef <buganizer-system@google.com>:
services and better VPN support.
well again. it is NOT working
there is one person who made it work using rooted pixel. can you share the
code?
or at least make a pull request on AOSP?
Op zo 29 sep. 2019 05:18 schreef <buganizer-system@google.com>:
mo...@gmail.com
October 5 update. Still hasn't fixed
ro...@gmail.com
Such a long time running bug with no response from Google. Doesn't make me want to upgrade to Pixel 4. More likely return to OnePlus
ma...@gmail.com
@126
That update is just for Google's VPN service they provide to Fi subscribers.
My root fix was just [ifconfig ppp0 mtu 1388] in a terminal to prevent larger frames from being dropped, but you'd need a way to automatically reapply it, as the interface returns to 1500 every time it comes up.
That update is just for Google's VPN service they provide to Fi subscribers.
My root fix was just [ifconfig ppp0 mtu 1388] in a terminal to prevent larger frames from being dropped, but you'd need a way to automatically reapply it, as the interface returns to 1500 every time it comes up.
[Deleted User] <[Deleted User]>
so there you go google a 5 min fix drop the mtu either that or admit that you don't want to so we start paying you more money
pa...@gmail.com
same here
to...@gmail.com
Hello,
i have android 9 xiaomi pocophone F1 and ha have the completely same behaviour with peer disconection after few seconds.. Android shows connections till up.
i have android 9 xiaomi pocophone F1 and ha have the completely same behaviour with peer disconection after few seconds.. Android shows connections till up.
st...@gmail.com
Hello, I have a Pixel 3XL, latest patches to Android 10 - still drops L2TP VPN connection to my USG around 60 seconds into session.
ad...@gmail.com
Please make sure you click the star button for this issue if it affects you.
do...@gmail.com
Has anyone had any luck with warranty? Since it is not a hardware issue, I would either need store credit or a refund so I can select a different phone.
I've put up with this issue for a year and I'm done waiting for the fix that ain't coming.
I've put up with this issue for a year and I'm done waiting for the fix that ain't coming.
lo...@gmail.com
Maybe all talented developers moved to Facebook?
ro...@gmail.com
set my l2tp on pixel 3 xl to always on. waited several mins and took report while it disconnected and reconnected. (latest update)
https://drive.google.com/open?id=16mInqCBgWBbGILAtf3l3oOeLu1V2bBub
jr...@gmail.com
Did anyone happened to have Pixel 4?
is the same thing happening on it?
is the same thing happening on it?
fi...@gmail.com
Just received my Pixel 4 XL this morning and did a quick test. I stayed connected to my L2TP VPN (UniFi USG) for 6 minutes before manually disconnecting.
jr...@gmail.com
I see, so the issue is just on pixel 3 and 3a (and XL versions of both)
md...@gmail.com
Confirmed working on Pixel 4 and Unifi USG here as well.
On Wed, Oct 23, 2019 at 2:10 PM <buganizer-system@google.com> wrote:
On Wed, Oct 23, 2019 at 2:10 PM <buganizer-system@google.com> wrote:
st...@gmail.com
same problem with a Pixel 3
he...@gmail.com
Pixel 3 XL,
```10-24 11:45:00.222 13395 13395 I pppd : LCP terminated by peer (User request)
10-24 11:45:00.223 13395 13395 I pppd : Connect time 1.6 minutes.
10-24 11:45:00.223 13395 13395 I pppd : Sent 49636 bytes, received 117895 bytes.
```10-24 11:45:00.222 13395 13395 I pppd : LCP terminated by peer (User request)
10-24 11:45:00.223 13395 13395 I pppd : Connect time 1.6 minutes.
10-24 11:45:00.223 13395 13395 I pppd : Sent 49636 bytes, received 117895 bytes.
lo...@gmail.com
As I understand, there is some blocker for this issue - https://pasteboard.co/IDr8Rp9.png
[Deleted User] <[Deleted User]>
Could Google confirm that this block is and why it is in place
however, I suspect that no one for google is looking at this as I have not seen a reply from google in months buy if you are watching prove me wrong and reply
however, I suspect that no one for google is looking at this as I have not seen a reply from google in months buy if you are watching prove me wrong and reply
ro...@gmail.com
Looks like Google doesn't care. I've seen not fixing infeasible on other versions of this bug. With that feeling I've ditched my pixel and gone back to OnePlus. My 7T been connected for 45 mins as of this post without issues.
br...@gmail.com
May be google is going to sell vpns?
I changed to sstp openvpn and strongswan, I am very satisfied.
On Thu, 24 Oct 2019, 12:14 , <buganizer-system@google.com> wrote:
I changed to sstp openvpn and strongswan, I am very satisfied.
On Thu, 24 Oct 2019, 12:14 , <buganizer-system@google.com> wrote:
he...@gmail.com
installed latest November patch on pixel 3.
still disconnect at 90 seconds....
my next phone is not a pixel!
I have this phone 1 year now and it NEVER worked @google.
WTF is wrong with you! People pay high end prices and your support is the
most CRAP ever!
Op do 24 okt. 2019 13:19 schreef <buganizer-system@google.com>:
still disconnect at 90 seconds....
my next phone is not a pixel!
I have this phone 1 year now and it NEVER worked @google.
WTF is wrong with you! People pay high end prices and your support is the
most CRAP ever!
Op do 24 okt. 2019 13:19 schreef <buganizer-system@google.com>:
do...@gmail.com
@120 @129
What is the fix for rooted devices? Already tried the 1 line of code in this thread, decreasing MTU, but it still disconnects. I've tried googling but coming up empty.
Connecting to Meraki MX450.
Thanks
What is the fix for rooted devices? Already tried the 1 line of code in this thread, decreasing MTU, but it still disconnects. I've tried googling but coming up empty.
Connecting to Meraki MX450.
Thanks
go...@gmail.com
I ain't getting a Pixel again either, Google needs to fix this ASAP!
mi...@gmail.com
Yes I ended up with a docker container and openvpn as a solution. I
couldn't wait any longer for Google to get their stuff to work.
The new pixel4 is nothing exciting. Closed the Nest API with no
alternative. C'mon Google!
On Wed, Nov 20, 2019, 11:08 AM <buganizer-system@google.com> wrote:
couldn't wait any longer for Google to get their stuff to work.
The new pixel4 is nothing exciting. Closed the Nest API with no
alternative. C'mon Google!
On Wed, Nov 20, 2019, 11:08 AM <buganizer-system@google.com> wrote:
ho...@gmail.com
So for anyone still dealing with this issue I have something for you to
try. In my case, when I have "data saver" mode active on my phone I have
the VPN problems. Turn that off and it connects fine and stays connected.
I suspect this explains why 3rd party VPNs seem to work since such a system
setting would apply differently to them.
On Wed, Nov 20, 2019, 5:30 PM <buganizer-system@google.com> wrote:
try. In my case, when I have "data saver" mode active on my phone I have
the VPN problems. Turn that off and it connects fine and stays connected.
I suspect this explains why 3rd party VPNs seem to work since such a system
setting would apply differently to them.
On Wed, Nov 20, 2019, 5:30 PM <buganizer-system@google.com> wrote:
he...@gmail.com
data saver is always off and does not work for me
Op do 21 nov. 2019 20:58 schreef <buganizer-system@google.com>:
Op do 21 nov. 2019 20:58 schreef <buganizer-system@google.com>:
aw...@waretec.com
Pixel 3a here. Data saver has no impact on VPN stability for me. I've never turned it on and have had L2TP connection stability / longevity problems in the native Android client from the beginning.
I switched to OpenVPN and it's rock solid. I have no faith in Google fixing this issue. You probably shouldn't either.
I switched to OpenVPN and it's rock solid. I have no faith in Google fixing this issue. You probably shouldn't either.
ad...@google.com
vi...@google.com
sa...@gmail.com
Same issue for me on Pixel 3a XL Android 10 December Security Patch. Connecting to Ubiquiti Edgerouter with L2TP/IPsec VPN with PSK. All other devices work fine (Laptop, other Android devices) but my 3a XL disconnects after ~90 seconds give or take. Tried factory reset and made sure data saver not enabled, same behavior.
ro...@gmail.com
yup Google doesn't care about this issue.....
Here you fix it.... No you fix it.
Here you fix it.... No you fix it.
th...@gmail.com
Maybe its time further action is taken, class action maybe?
I have had this phone since the initial release and no progress. Ive been patient as all of you, but to take over a year to fix a small problem is unacceptable. Especially in a time where network security is Paramount but this major function on these phone's is non functional. I would have chosen a different phone if this would have been disclosed at the start. So the false pretenses that this phone was sold under seems like a case to me. What do you think?
I have had this phone since the initial release and no progress. Ive been patient as all of you, but to take over a year to fix a small problem is unacceptable. Especially in a time where network security is Paramount but this major function on these phone's is non functional. I would have chosen a different phone if this would have been disclosed at the start. So the false pretenses that this phone was sold under seems like a case to me. What do you think?
[Deleted User] <[Deleted User]>
I'd be interested in the Class action what do we need to do
br...@averydennison.com
I know I've said this before, but I think it's worth repeating because of
how long this has went on. I first encountered this issue on my Pixel 3XL
with an update to Android 9. Over time I learned that with the Android Q
(10) Beta the issue was gone. So in my way of thinking I figured they had
fixed it in Q and just didn't go back and update Android 9. So I became an
Android Q Beta tester so I could actually have my VPN work correctly. And
it did work flawlessly for a very long time. And here it goes, right up to
the very last Beta drop before release and it was that last Beta drop that
it stopped working again. I'm thinking how perfect is that where I can tell
them exactly what cut of firmware it stopped working in. That's a
developers dream to have it isolated like that as they just have to go to
networking changes and see what changed between those two versions in
Android Q.
But I guess that's too hard!!!!!!
On Thu, Dec 12, 2019 at 5:44 AM <buganizer-system@google.com> wrote:
how long this has went on. I first encountered this issue on my Pixel 3XL
with an update to Android 9. Over time I learned that with the Android Q
(10) Beta the issue was gone. So in my way of thinking I figured they had
fixed it in Q and just didn't go back and update Android 9. So I became an
Android Q Beta tester so I could actually have my VPN work correctly. And
it did work flawlessly for a very long time. And here it goes, right up to
the very last Beta drop before release and it was that last Beta drop that
it stopped working again. I'm thinking how perfect is that where I can tell
them exactly what cut of firmware it stopped working in. That's a
developers dream to have it isolated like that as they just have to go to
networking changes and see what changed between those two versions in
Android Q.
But I guess that's too hard!!!!!!
On Thu, Dec 12, 2019 at 5:44 AM <buganizer-system@google.com> wrote:
--
*Bradley S Brewer* | Test Engineer | Product Evaluation | PSD
170 Monarch Lane, Miamisburg , OH 45342 | brad.brewer@averydennison.com
Office:937-865-6728
--
-------------------------------------------------------------------------------------------------------------
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited. If you received
this in error, please contact the sender and delete the material from any
computer.
For details about the personal information we process and why,
please see our Privacy Notice
<
-------------------------------------------------------------------------------------------------------------
65...@gmail.com
SynologyのVPNサーバアプリケーションに問題があるのだと思う。
ここを見ている人はみんなSynologyのNASを使ってますか？
ここを見ている人はみんなSynologyのNASを使ってますか？
gu...@gmail.com
Same issue here... Pixel 3XL trying to connect to Meraki VPN. The connection works but I have to rush in the next 90 secondes or so to do what I have to do before it stop working.
It stays connected but when it stops working I only see the Sent counter increasing and the received counter stays the same.
It stays connected but when it stops working I only see the Sent counter increasing and the received counter stays the same.
he...@gmail.com
I am not going to buy any pixel phone. paying premium price and be left in
de dirt for so long now. F*CK you Google with your flopped pixel line!
Op di 7 jan. 2020 21:57 schreef <buganizer-system@google.com>:
de dirt for so long now. F*CK you Google with your flopped pixel line!
Op di 7 jan. 2020 21:57 schreef <buganizer-system@google.com>:
ar...@gmail.com
Fix this already. wtf.
eo...@gmail.com
As mentioned by someone in this thread earlier, It seems that Pixel3 series have a problem on L2TP keepalive (RFC2661). To **workaround** the problem, you need to turn off the L2TP keep-alive feature on your VPN server. It's not a good way for most of users, including me.
I'm completely no idea why the protocol doesn't work in Pixel3 series. At least, L2TP/IPSec works to me well in Android Beta OTA.
I'm completely no idea why the protocol doesn't work in Pixel3 series. At least, L2TP/IPSec works to me well in Android Beta OTA.
ne...@gmail.com
Does anyone know how to implement this workaround on a Ubiquiti USG or a
Meraki MX64?
On Thu, Jan 16, 2020, 22:17 <buganizer-system@google.com> wrote:
Meraki MX64?
On Thu, Jan 16, 2020, 22:17 <buganizer-system@google.com> wrote:
[Deleted User] <[Deleted User]>
According to Meraki it can not be done on the MX range of firewalls
[Deleted User] <[Deleted User]>
Good Afternoon everyone. I'm currently on the google support line getting the runaround so this is a call to arms we need to start bombarding the support centre in a sustained way until they take this seriously
use the chat
use the phone
use email
make sure they cant get away from this
use the chat
use the phone
use email
make sure they cant get away from this
td...@gmail.com
New to Android and opened a case on the L2TP PSK Issue... It was suggested by support to me that I contact Ubiquiti on the issue. IMO, this has nothing to do with UniFi as my VPN works with all other devices (iOS/MacOS/Windows/Linux).
ad...@gmail.com
It's got nothing to do with ubiquiti. With my pixel 2 it worked. I upgraded
to a Pixel 3 and it stopped working. I then upgraded from pixel 3 to 4 and
it started working. Exact same ubiquiti hardware with no configuration
change.
On Sat, 29 Feb 2020, 14:13 , <buganizer-system@google.com> wrote:
to a Pixel 3 and it stopped working. I then upgraded from pixel 3 to 4 and
it started working. Exact same ubiquiti hardware with no configuration
change.
On Sat, 29 Feb 2020, 14:13 , <buganizer-system@google.com> wrote:
ba...@gmail.com
Works fine with my Chromebook, older Nexus5, Ubuntu, Windows 10, but with the Pixel3 at around 80 seconds a hello packet is sent by my VPN server, but the Pixel 3 never responds, so the VPN server assumes the connection is dead and removes it.
Sad that on a flagship phone Google has yet to fix a major security flaw.
Sad that on a flagship phone Google has yet to fix a major security flaw.
ch...@gmail.com
They sold the phone and got the money - they do not care any longer.
You can see their "interest" in fixing this issue:
1. not even one relpy from google on this issue
2. stating this issue is blocked by 119076193
3. no info about blocking issue nevertheless
4. fixing the issue in Android Q Beta (except the last beta)
5. fucking it up again in public release
You can see their "interest" in fixing this issue:
1. not even one relpy from google on this issue
2. stating this issue is blocked by 119076193
3. no info about blocking issue nevertheless
4. fixing the issue in Android Q Beta (except the last beta)
5. fucking it up again in public release
br...@gmail.com
My pocophone start working with the update for Android 10. it was not
working for almost 2 years.
Só it is a android problem.!!!!!!!!
Never saw imcompetence like Thais !!!!
A sábado, 29/02/2020, 18:52, <buganizer-system@google.com> escreveu:
working for almost 2 years.
Só it is a android problem.!!!!!!!!
Never saw imcompetence like Thais !!!!
A sábado, 29/02/2020, 18:52, <buganizer-system@google.com> escreveu:
td...@gmail.com
Still not working after March 2020 security patch for Android 10/Pixel 4 XL (received it on the Fi network this am). The case I had opened was closed.
st...@gmail.com
Same. Not working after 90 seconds. Motorola G7
ni...@gmail.com
This is a bug from 2015 (see 37074640 issue). Google doesnt plan to fix it.
he...@gmail.com
my router does support openvpn as well.
implemented openvpn with the official openvpn client. works rock solid with
always on VPN.
Op zo 15 mrt. 2020 19:45 schreef <buganizer-system@google.com>:
implemented openvpn with the official openvpn client. works rock solid with
always on VPN.
Op zo 15 mrt. 2020 19:45 schreef <buganizer-system@google.com>:
hu...@gmail.com
It maybe a bug from 2015, but they fixed it with the beta of android 10 and then ruined it again...
ai...@gmail.com
The absolute lack of a response from Google is infuriating.
he...@gmail.com
this is why this was my last pixel device.
premium prices means premium support.... and Google is failing big time
next phone will be an OnePlus again...
Op ma 16 mrt. 2020 19:41 schreef <buganizer-system@google.com>:
premium prices means premium support.... and Google is failing big time
next phone will be an OnePlus again...
Op ma 16 mrt. 2020 19:41 schreef <buganizer-system@google.com>:
ax...@gmail.com
So not to downplay this issue as I'm irritated that it hasn't been fixed when they broke something that worked before; but WireGuard has been working absolutely great for me to connect to my own home server running WireGuard with PiHole filtering out ads.
[Deleted User] <[Deleted User]>
Having this feature working would be a huge benefit for everyone else's safe working from home due to the Covid19 pandemic. We need to be able to log into a VPN and not have it disconnect after 90 seconds. Having this work on my phone would help me greatly at this time.
In the UK, a product needs to be 'Fit for Purpose' under the Sale of Goods Act 1979, and the Consumer Rights Act 2015 also provides protection to consumers. We successfully received full refunds for two of our Nexus 5x recently, after owning them for several years, so this legislation does hold companies to releasing fit for purpose products.
In the UK, a product needs to be 'Fit for Purpose' under the Sale of Goods Act 1979, and the Consumer Rights Act 2015 also provides protection to consumers. We successfully received full refunds for two of our Nexus 5x recently, after owning them for several years, so this legislation does hold companies to releasing fit for purpose products.
si...@gmail.com
After a series of mind-numbing messages and complaints, and despite being outside of the grace period for refunds, Google allowed me to return my Pixel 3a XL for a full refund.
They seem to have accepted that it's cheaper for them to credit affected devices rather than to fix the underlying problem.
If you go down this route, make sure your case is escalated to the ironically named 'Specialist Team' (they first rejected it because the thought VPN was a 3rd party app, and hadn't taken the time to read the case history!).
Good luck!
They seem to have accepted that it's cheaper for them to credit affected devices rather than to fix the underlying problem.
If you go down this route, make sure your case is escalated to the ironically named 'Specialist Team' (they first rejected it because the thought VPN was a 3rd party app, and hadn't taken the time to read the case history!).
Good luck!
do...@gmail.com
@183 - I tried this route back in November 2019 when my 1 year warranty was about to expire but had no luck. Was just told by the specialist team that they would send me a hardware replacement device before looking into further options even though I said it's not a hardware issue, I'd have the same software issue with the replacement device.
Were you still under warranty now that you received a refund?
Were you still under warranty now that you received a refund?
si...@gmail.com
#184 - Yeah, the device was just under 6 months old when I got the refund.
Sorry you weren't so lucky. There's a chance (if you're in the UK) that you're still covered under the Consumer Rights Act 2015; this is a design flaw that prevents the use of a critical (at least for professional users) feature, rendering the device 'not fit for purpose'. I assume there's equivalent legislation in most other countries.
It's reminiscent of the Recall Coordinator's scene in Fight Club, on a slightly less dramatic scale.
Sorry you weren't so lucky. There's a chance (if you're in the UK) that you're still covered under the Consumer Rights Act 2015; this is a design flaw that prevents the use of a critical (at least for professional users) feature, rendering the device 'not fit for purpose'. I assume there's equivalent legislation in most other countries.
It's reminiscent of the Recall Coordinator's scene in Fight Club, on a slightly less dramatic scale.
la...@gmail.com
Same issue here with Pie on a Razer Phone 2 connecting to a l2tp vpn. 30 seconds and it drops
ow...@gmail.com
Still having an issue connecting to my unifi VPN (USG). Running andoid 10 april 5 202 security patch.
Trying to connect using L2TP/IPSec PSK. It'll connect for a minute or two then drop off.
Trying to connect using L2TP/IPSec PSK. It'll connect for a minute or two then drop off.
su...@gmail.com
I'm seeing same thing with unifi L2TP VPN on UDM for server and Android 10 April security patch on Pixel 3XL too. I can connect for ~90 seconds and pass a tiny bit of data but not much and drops off after about 80 seconds.
There have been some mentions in this thread that it might be caused by MTU. Since this is layer 2 communication, it does seem relevant that it be mentioned what MTU is used in different places. On my VPN server side the upstream modem has MTU is configured as 1500.
On the phone side I'm using T-Mobile LTE, so potentially this could be same issue the OP mentioned with 464XLAT implementation. I'll see if I can configure and force an IPV6 connection instead for my server side to see if that helps.
There have been some mentions in this thread that it might be caused by MTU. Since this is layer 2 communication, it does seem relevant that it be mentioned what MTU is used in different places. On my VPN server side the upstream modem has MTU is configured as 1500.
On the phone side I'm using T-Mobile LTE, so potentially this could be same issue the OP mentioned with 464XLAT implementation. I'll see if I can configure and force an IPV6 connection instead for my server side to see if that helps.
[Deleted User] <[Deleted User]>
it is 100% the MTU it can be fixed in under 5 mins on a rooted device but that then brings the problems of having a rooted device what we need is google to make the same MTU change that has been detailed and tested working for 12 months now and implement it in to there signed code
the problem is that Google for some reason don't want to fix this I can say that because I have been active on this thread for 15 months and have had numerous calls with google one of with I gave them full step by step (it was only 8 steps) on how to fix this issue and that was last October
So with absolutely no hope of getting an answer, I ask Google why don't you want to Fix this issue do you not think we deserve an answer
the problem is that Google for some reason don't want to fix this I can say that because I have been active on this thread for 15 months and have had numerous calls with google one of with I gave them full step by step (it was only 8 steps) on how to fix this issue and that was last October
So with absolutely no hope of getting an answer, I ask Google why don't you want to Fix this issue do you not think we deserve an answer
do...@gmail.com
@189 Can you provide the details on the fix for those of us who are rooted? I tried asking back in comment 149, referencing comments 120 & 129, where I tried the MTU change, but it did not work me.
Thanks!
Thanks!
su...@gmail.com
If this is indeed solely caused by MTU of T-Mobile's implementation of ipv6 (IPV4 is encapsulated), perhaps decreasing the MTU on the server side on the L2TP interface might help for those of us that haven't rooted phones.
https://www.reddit.com/r/tmobile/comments/97ifsv/issues_with_ipv6_tmobile_lte_vpn_networks/e4900ws/
ne...@gmail.com
Doubt it's the carrier as it happens to me on AT&T and WiFi, on USG and
Cisco MX. It's definitely an Android problem. I'm using Android Q on a
Pixel 3a. My old Nexus 5X with Oreo does fine with VPN.
On Thu, Apr 16, 2020, 16:35 <buganizer-system@google.com> wrote:
Cisco MX. It's definitely an Android problem. I'm using Android Q on a
Pixel 3a. My old Nexus 5X with Oreo does fine with VPN.
On Thu, Apr 16, 2020, 16:35 <buganizer-system@google.com> wrote:
[Deleted User] <[Deleted User]>
you misunderstand the MTU miss-match seems to be between the 2 VPN endpoints Google got it wrong when coding the L2TP stack if you are running a Cisco ASA or other fully configurable Firewall you can change the MTU on that end to match and it will work. the problem is if you are using something less configurable like a Meraki MX or worse if you don't run the VPN then you are forced to use the standard L2TP MTU witch won't work because google screwed up and won't admit it
if you look at it seem like google are taking the attitude of we did it this way its wrong but now the rest of the world better change so we don't have to fix there mess
if you look at it seem like google are taking the attitude of we did it this way its wrong but now the rest of the world better change so we don't have to fix there mess
do...@gmail.com
Possible class action lawsuit regarding Pixel 3 issues, figured I'd post this here since our VPN issues were never resolved.
"If you are experiencing severe hardware and software issues, you can fill in the form on CSK&D’s website to give further information on the problems you are experiencing."
fa...@gmail.com
Same issue here:
Samsung Note 10 lite Android 10 Patchlevel July 2020
L2TP-VPN on Unifi Dreammachine keeps disconnecting every 2 minutes.
Other devices work fine.
Samsung Note 10 lite Android 10 Patchlevel July 2020
L2TP-VPN on Unifi Dreammachine keeps disconnecting every 2 minutes.
Other devices work fine.
ch...@gmail.com
Still fucked up in Android 11.
gi...@gmail.com
Pixel 3XL on Android 11 RP1A.200720.009 - L2TP/IPSec still not working - it disconnect after 60 seconds
fa...@gmail.com
good news!
I just installed the update for my Samsung Note 10 lite (Patchlevel September 2020) and now it works!
I just installed the update for my Samsung Note 10 lite (Patchlevel September 2020) and now it works!
ga...@gmail.com
Device: Pixel 3a on Android 11 RP1A.200720.009
Issue: L2TP/IPSec connection interrupted after ~30 seconds and connection status remains 'connected'.
Issue: L2TP/IPSec connection interrupted after ~30 seconds and connection status remains 'connected'.
pa...@gmail.com
Device: Pixel 3a on Android 11 RP1A.201005.004
Issue: L2TP/IPSec connection interrupted after ~90 seconds
Issue: L2TP/IPSec connection interrupted after ~90 seconds
ma...@gmail.com
Pixel 4a on Android 11 RP1A.201105.002 Connecting to home network with L2TP/IPSec PSK connects but apps can't connect to internet, and I can ping all devices on home network
ma...@gmail.com
I have been able to confirm L2TP/IPSec PSK are not working on the Pixel 5. So those who had switched to Pixel 4 and Pixel 4XL to successfully resolve the ~90 second connectivity drop out issue and have their VPNs back working again DO NOT GO TO PIXEL5. So far, I have confirmed the Pixel 5 will have issues connecting with UniFi and Sonicwall l2tp/ipsec psk vpns.
This time around however the issue is a bit different however with Pixel 5.
1. L2TP/IPSec PSK never connects when trying to connect from LTE/5G connection (ie not WIFI off or unavailable). The problem is simple. The Pixel 5 fails to ever resolve the l2tp vpn server name in "server address" field. Duh. The workaround is to use the ip address in the server name. However, continue to issue number 2 below as L2TP/IPSec PSK is broken on Pixel 5 even when hard coding the ip address of l2tp vpn server.
2. L2TP/IPSec PSK connects (both on WIFI and LTE/5G connections) and authenticates with the vpn server but then fails to pass and/or fragment large packets. This is most likely an MTU problem affecting the l2tp vpn connections on Pixel 5. The issue is on the Pixel 5 and I have found no workaround by changing MTU on the firewall (it’s a path and encapsulation problem) and happens regardless of ISP/mobile carrier (verified issue with T-Mobile, AT&T, Comcast, Cogent, Verizon). Other than that I haven’t had a chance to fully troubleshoot the issue and will probably not bother to root the Pixel 5 and mess around with it as my patience with such Pixel VPN problems has expired over the past two years.
We were all ready to upgrade our Pixel 4 phones to Pixel 5 but based on Google's track record with even caring to address these l2tp psk VPN problems we are returning all of our Pixel 5s for a refund.
This time around however the issue is a bit different however with Pixel 5.
1. L2TP/IPSec PSK never connects when trying to connect from LTE/5G connection (ie not WIFI off or unavailable). The problem is simple. The Pixel 5 fails to ever resolve the l2tp vpn server name in "server address" field. Duh. The workaround is to use the ip address in the server name. However, continue to issue number 2 below as L2TP/IPSec PSK is broken on Pixel 5 even when hard coding the ip address of l2tp vpn server.
2. L2TP/IPSec PSK connects (both on WIFI and LTE/5G connections) and authenticates with the vpn server but then fails to pass and/or fragment large packets. This is most likely an MTU problem affecting the l2tp vpn connections on Pixel 5. The issue is on the Pixel 5 and I have found no workaround by changing MTU on the firewall (it’s a path and encapsulation problem) and happens regardless of ISP/mobile carrier (verified issue with T-Mobile, AT&T, Comcast, Cogent, Verizon). Other than that I haven’t had a chance to fully troubleshoot the issue and will probably not bother to root the Pixel 5 and mess around with it as my patience with such Pixel VPN problems has expired over the past two years.
We were all ready to upgrade our Pixel 4 phones to Pixel 5 but based on Google's track record with even caring to address these l2tp psk VPN problems we are returning all of our Pixel 5s for a refund.
ma...@gmail.com
Is there anyway to elevate this issue? Who is the assignee for this issue?
do...@gmail.com
@202
What's the fix when you're rooted?
What's the fix when you're rooted?
ma...@gmail.com
@204
I have no idea if there is even a fix if rooted. I would have to root the Pixel 5 to even begin troubleshooting and I am not willing to do so. Enough is enough for me and the Google Pixel series software bugs. There was some conjecture in this thread that there was a 'MTU fix' that could be applied to the Pixel 3 series to resolve the 90 second drop out issue that continues to plague the Pixel 3 and earlier phones. I personally could never find such fix and believe the problem was more likely related to issues with how Android on the Pixel 3 and prior was handling keepalives (which could be related to MTU also but at a deeper level and interaction in the code). Regardless, I never found any simple fix that could be applied to a rooted device yet others here seemed to suggest there was (but I suspect they were resolving a different issue and not the more common 90 second drop out problem).
I have no idea if there is even a fix if rooted. I would have to root the Pixel 5 to even begin troubleshooting and I am not willing to do so. Enough is enough for me and the Google Pixel series software bugs. There was some conjecture in this thread that there was a 'MTU fix' that could be applied to the Pixel 3 series to resolve the 90 second drop out issue that continues to plague the Pixel 3 and earlier phones. I personally could never find such fix and believe the problem was more likely related to issues with how Android on the Pixel 3 and prior was handling keepalives (which could be related to MTU also but at a deeper level and interaction in the code). Regardless, I never found any simple fix that could be applied to a rooted device yet others here seemed to suggest there was (but I suspect they were resolving a different issue and not the more common 90 second drop out problem).
ai...@gmail.com
I'm just here with my pitchfork like everyone else, wondering why Google doesn't seem to care at all about this broken functionality in their "flagship" phone showcasing their "flagship" OS.
It's a good thing that Fi is now selling Samsung phones.
It's a good thing that Fi is now selling Samsung phones.
se...@gmail.com
I can add some logs if needed, but they do not differ from what is already posted here.
- On my Google Pixel 3 XL the IPSec tunnel is closed after about 90 seconds due to Android not responding to control messages.
- On my wife's Pixel 2 the IPSec tunnel is working as expected.
- On my Google Pixel 3 XL the IPSec tunnel is closed after about 90 seconds due to Android not responding to control messages.
- On my wife's Pixel 2 the IPSec tunnel is working as expected.
[Deleted User] <[Deleted User]>
Could an official Google person say, why this is not fixed?
At least it would be nice to know the reasons.
At least it would be nice to know the reasons.
cn...@gmail.com
Well right as I got home from picking up my new Pixel 5 this thread pops back up with disappointing info. Just upgraded from the 3 thinking this was resolved long ago. Testing on my pixel 5 I was able to connect and stay connected for over 5 minutes with WiFi and 5g using an l2tp/ipsec psk vpn. My test router was an edge router pro which definitely had/has an issue staying connected to my Pixel 3. Not sure if this helps anyone but but it is definitely a relief for me.
xs...@gmail.com
It's been two years since this original issue was opened. Google won't fix it. I've moved on to using Wireguard on my pihole. Would highly recommend everyone else do the same.
ma...@gmail.com
@209
This is very good info but the problem is not connecting but passing larger packets. I did not have a Ubiquiti to test with but did test with Sonicwall and UniFi devices. We could connect and stay connected indefinitely but the problem with passing larger packets (most likely closer to the 1400-1500 byte size). Once connected were you able to fully test connectivity to services that would push the packet size? One easy way to test is have a Full Tunnel VPN connection and then start hitting sites on the internet that stream video (such as CNN, NBC or FOX sites).
This is very good info but the problem is not connecting but passing larger packets. I did not have a Ubiquiti to test with but did test with Sonicwall and UniFi devices. We could connect and stay connected indefinitely but the problem with passing larger packets (most likely closer to the 1400-1500 byte size). Once connected were you able to fully test connectivity to services that would push the packet size? One easy way to test is have a Full Tunnel VPN connection and then start hitting sites on the internet that stream video (such as CNN, NBC or FOX sites).
ne...@gmail.com
Since updating to Android 11 (RP1A.201105.002) on my Pixel 3a, the behavior
has changed slightly, but it's still broken. On an MX64 via L2TP/IPSec the
connection is established and works for about 30 to 90 seconds after which
time, all network connectivity stops until I disconnect from the VPN. On a
USG, the connection is established and works for about the same length of
time, then the VPN disconnects on its own.
On Thu, Nov 19, 2020, 15:14 <buganizer-system@google.com> wrote:
has changed slightly, but it's still broken. On an MX64 via L2TP/IPSec the
connection is established and works for about 30 to 90 seconds after which
time, all network connectivity stops until I disconnect from the VPN. On a
USG, the connection is established and works for about the same length of
time, then the VPN disconnects on its own.
On Thu, Nov 19, 2020, 15:14 <buganizer-system@google.com> wrote:
jo...@gmail.com
Pixel 3/Android 11. The issue with L2TP is still there.
I can connect easily with other devices (huawei, one olus) but not with this phone.
Who knows, maybe the muricans don't want privacy and the Chinese do!
It had a nice camera though ;)
I can connect easily with other devices (huawei, one olus) but not with this phone.
Who knows, maybe the muricans don't want privacy and the Chinese do!
It had a nice camera though ;)
ro...@gmail.com
korean phones work just fine too. my samsung note 9 has yet to fail me... hopefully the note 20 ultra 5g will work too. find out in a few days.
guess google just doesn't care
guess google just doesn't care
ma...@gmail.com
Same here, Pixel 3a disconnecting after ~90 seconds. Unifi Dream Machine as VPN server.
ja...@gmail.com
I'm still experiencing on this my Pixel 3 as well attempting to connect to L2TP/IPSEC-PSK to a Meraki VPN tunnel.
I figured I would give Google Support another shot this am and I was quickly reminded of why that never works.
I was told to contact my carrier; my response was that this issue was happening also with the SIM card removed.
I went through all the other troubleshooting they wanted me to - apart from a full restore of the phone.
I eventually had to stop troubleshooting with them since I had to go out so I'm not sure what the end result would have been with them but this is clearly an OS issue.
I figured I would give Google Support another shot this am and I was quickly reminded of why that never works.
I was told to contact my carrier; my response was that this issue was happening also with the SIM card removed.
I went through all the other troubleshooting they wanted me to - apart from a full restore of the phone.
I eventually had to stop troubleshooting with them since I had to go out so I'm not sure what the end result would have been with them but this is clearly an OS issue.
lo...@gmail.com
If the developer cannot fix it for years usually it mean either he is a bad developer either his manager wasting money on his own vacation and not on the product.
Personally me believe that all good developers already moved to other FAAN companies.
Personally me believe that all good developers already moved to other FAAN companies.
gr...@gmail.com
I am currently utilizing a Google Pixel 4a and I am having a similar issue in which I cannot connect to any VPN. And, that is a problem because I NEED it to function for work.
tc...@gmail.com
I'm using WireGuard instead. This will never be fixed.
gr...@gmail.com
I have also figured out just now that I have to be connected to WIFI to connect to SOME vpn services. This is really inconvenient and not going to do well for me. Time to return it.
jr...@gmail.com
@220 Had the same issue, tried to use IP address instead of DNS name for server address, that worked.
fa...@gmail.com
OK, doesn't work on my Samsung Note 10 lite anymore after I updated to Android 11.
qw...@googlemail.com
Same issue for me, surely this is a Google issue that can be fixed?!?!?!
[Deleted User] <[Deleted User]>
OK so I was on the Phone with google about this Again (lost count of how many times now) I was told they would pass it to the correct teem (again lost count of how many times I've been told this) but this time I received an email and all it was, was an instruction on how to set up and connect a VPN
Well google that is just an insult you clearly have never looked at this Tread or Listened to the people calling and emailing you
So to everyone having this problem you have to choices as google clearly don't know how to fix this either move away from android or root your phone and change the MTU on the LTE radio to 1300 this fixes it and is only one line of code but needs the device to be rooted
Well google that is just an insult you clearly have never looked at this Tread or Listened to the people calling and emailing you
So to everyone having this problem you have to choices as google clearly don't know how to fix this either move away from android or root your phone and change the MTU on the LTE radio to 1300 this fixes it and is only one line of code but needs the device to be rooted
se...@gmail.com
Is there any additional information on the MTU topic for the modem?
se...@gmail.com
Okay, sorry for the spam but the MTU issue makes sense in certain cases but not here I think.
It would explain why a connection can not be established by I can not come up with a good reason why it would affect an already established connection.
I changed the MTU to a lower value but the tunnnel still closes after 90 seconds.
Is there any way to escalate this issue? Trigger the assignee? This is really annoying.
It would explain why a connection can not be established by I can not come up with a good reason why it would affect an already established connection.
I changed the MTU to a lower value but the tunnnel still closes after 90 seconds.
Is there any way to escalate this issue? Trigger the assignee? This is really annoying.
ai...@gmail.com
The only way they're going to pay attention to or escalate a 3 year old bug is if enough people complain, or if a media outlet writes a story on it.
I don't feel like they care about this broken core functionality at all otherwise.
I don't feel like they care about this broken core functionality at all otherwise.
[Deleted User] <[Deleted User]>
Just Received this
Hi Dave,
Thank you for contacting Google Support.
As per our conversation the other day, I would like to inform you that the issue that you are facing is not in our scope of support and for this you need to consult your network administrator. You may even visitwww.support.google.com
In case you have any additional questions, feel free to reply to this email or initiate a chat/phone with our support team.
Thanks!
Vikas
The Google Support Team
Hi Dave,
Thank you for contacting Google Support.
As per our conversation the other day, I would like to inform you that the issue that you are facing is not in our scope of support and for this you need to consult your network administrator. You may even visit
In case you have any additional questions, feel free to reply to this email or initiate a chat/phone with our support team.
Thanks!
Vikas
The Google Support Team
ch...@gmail.com
On my Pixel 3 since March '21 update L2TP connection could no longer be established at all. Prior to update I could connect for 90 sec - now I only get "not successful". FUCK YOU GOOGLE!
lu...@hotmail.com
Just updated, vpn still works for me, still cuts out after 60ish seconds though.
For a flagship phone still receiving new features, not fixing this issue that used to work perfectly fine is an absolute kick in the guts.
For a flagship phone still receiving new features, not fixing this issue that used to work perfectly fine is an absolute kick in the guts.
in...@sammysoft.de
I Just came accross the same problem.
I have been using ipsec xauth psk for years now without problems. The last device was running Android 8.1.
Now I tried to move to new hardware and am faced with the same problem:
VPN connects successfully but then only transfers a couple of bytes and stops.
Hardware: Motorola One Action.
Software: It still works with the Android 9 stock firmware
The problem occurs in all of the following: Android 10 stock, Android 10 GSI, Android 11 GSI
I recon the bug was introduced with Android 10 thus.
I have been using ipsec xauth psk for years now without problems. The last device was running Android 8.1.
Now I tried to move to new hardware and am faced with the same problem:
VPN connects successfully but then only transfers a couple of bytes and stops.
Hardware: Motorola One Action.
Software: It still works with the Android 9 stock firmware
The problem occurs in all of the following: Android 10 stock, Android 10 GSI, Android 11 GSI
I recon the bug was introduced with Android 10 thus.
dt...@gmail.com
Having the same problem, sad to read how far back this issue first came up.
aw...@waretec.com
People. Google DGAF. Use OpenVPN or WireGuard app and servers /
concentrators or buy different phones. Period. End of story.
Google doesn't care about this bug. They never will. Native support has
been broken for years. They either have inept resources (coders) assigned
to this bug, or none at all. I hope it's the latter, because if I lead a
programming team that couldn't figure this shit out after 2+ years, I
would Seppuku myself out if incompetent guilt.
On Tue, Apr 6, 2021, 7:34 PM <buganizer-system@google.com> wrote:
concentrators or buy different phones. Period. End of story.
Google doesn't care about this bug. They never will. Native support has
been broken for years. They either have inept resources (coders) assigned
to this bug, or none at all. I hope it's the latter, because if I lead a
programming team that couldn't figure this shit out after 2+ years, I
would Seppuku myself out if incompetent guilt.
On Tue, Apr 6, 2021, 7:34 PM <buganizer-system@google.com> wrote:
sz...@gmail.com
The same here. A tablet from Lenovo, updated to Android 10. VPN L2TP+IPsec keep quiet after around 2 minutes. Android shows established connection, however there is no traffic at all. The new bought device is completely inoperable for me, because I have to use VPN connection to work. I have also Xiaomi Mi Note (Android 11) and Huawei P Smart (Android 10) and everything works well, so I am not sure if this is related to Android 10 or jsut for some of manufacturer's overlay.
ja...@gmail.com
Unifi L2TP VPN server, can connect anytime from W10, never from Android. Please fix this!
ma...@gmail.com
Hello,
I've had the same issue with my Pixel 3 / 5 phones since years.
For VPN we use at home Unifi VPN by L2TP+IPsec who stops working.
On my new Pixel 5 the connection stops completly working.
I've spend some time to figgure out and solve both issues for me:
1. My Germany mobile provider Deutsche Telekom use as default APN a IPv6 based configuration.
As I had add the IPv4 APN and set them as default , I was able to connect, because the Unifi L2TP+IPsec VPN solution supports only a IPV4 connection.
2. To solve the in this thread reported 90sec connection issue, I had enabled WAN ICMP ping to the router.
It looke like if the mobile can't ping the router, the connection will dropped after 90sec.
As soon as I had add a firewall rule to allow WAN PING (ping from internet to the router), the connection was stable!
Kind regards
Markus
I've had the same issue with my Pixel 3 / 5 phones since years.
For VPN we use at home Unifi VPN by L2TP+IPsec who stops working.
On my new Pixel 5 the connection stops completly working.
I've spend some time to figgure out and solve both issues for me:
1. My Germany mobile provider Deutsche Telekom use as default APN a IPv6 based configuration.
As I had add the IPv4 APN and set them as default , I was able to connect, because the Unifi L2TP+IPsec VPN solution supports only a IPV4 connection.
2. To solve the in this thread reported 90sec connection issue, I had enabled WAN ICMP ping to the router.
It looke like if the mobile can't ping the router, the connection will dropped after 90sec.
As soon as I had add a firewall rule to allow WAN PING (ping from internet to the router), the connection was stable!
Kind regards
Markus
ro...@gmail.com
time to unfollow this. its clear google doesn't care. they no longer "assign" it to random staff. nothing has changed. still broke, still crap.
ma...@stolle.name
Unfortunately, the solution from #236 doesn't seem to work on my Pixel 3XL. I verified that WAN ping doesn't work. Then set up the firewall rules to allow pings. Verified that WAN ping works. But the phone VPN still disconnects after 90 seconds.
al...@gmail.com
Turning on WAN pings doesn't work for me either.
mi...@gmail.com
Same, I tried to replicate the solution but no avail. Tried with ICMP echo request only but with all ICMP types enabled. Could #236 Markus share the configuration used in router?
lo...@gmail.com
I noticed one thing, not sure it was listed here.
Establish VPN connection from desktop - everything works, no drops after 90sec.
Establish VPN connection from Pixel - not only phone connection dropped after 90sec, but first one from desktop as well.l, immediately with phone one.
Establish VPN connection from desktop - everything works, no drops after 90sec.
Establish VPN connection from Pixel - not only phone connection dropped after 90sec, but first one from desktop as well.l, immediately with phone one.
br...@gmail.com
I have no idea if any of this will help.
I have been using a PPTP tunnel for years, and only with Pixel 4 has it not worked. Same indications as L2TP has seen.
Last week I was in Central America, and was not able to get my (Sprint) International Roaming working. Unfortunately, the tech had me do a full network reset, which deleted my eSIM (thats the unfortunate part). After many attempts, I was finally able to get a new eSIM downloaded and got roaming working with BTL (Belize Telemedia Ltd).
I had to mostly rebuild my phone (they also had me do a factory reset) and on a whim, created and tried my VPN.
Well, it worked and stayed connected for as long as I wanted, as far as I can tell. Certainly, it connected and passed traffic. I thought maybe it was an eSIM issue and getting a new one had fixed the problem.
Upon returning home and joining my Sprint network, I checked and the VPN didnt work. I dont even see indications of connection attempts in my server logs.
I dont believe this is a matter of Sprint blocking the required ports. I have always been able to use my VPN with wifi tether on my phone.
Since it appears this is a phone issue, not a network, I cant help but wonder if the roaming had anything to do with it. I had an LTE signal with BTL and although the connection was a lot slower than home network, all I can say is it worked there, and not here. The primary difference in the phone config was roaming.
I havent even bothered trying to force roaming somehow and check on it, but all if this might help someone...
I have been using a PPTP tunnel for years, and only with Pixel 4 has it not worked. Same indications as L2TP has seen.
Last week I was in Central America, and was not able to get my (Sprint) International Roaming working. Unfortunately, the tech had me do a full network reset, which deleted my eSIM (thats the unfortunate part). After many attempts, I was finally able to get a new eSIM downloaded and got roaming working with BTL (Belize Telemedia Ltd).
I had to mostly rebuild my phone (they also had me do a factory reset) and on a whim, created and tried my VPN.
Well, it worked and stayed connected for as long as I wanted, as far as I can tell. Certainly, it connected and passed traffic. I thought maybe it was an eSIM issue and getting a new one had fixed the problem.
Upon returning home and joining my Sprint network, I checked and the VPN didnt work. I dont even see indications of connection attempts in my server logs.
I dont believe this is a matter of Sprint blocking the required ports. I have always been able to use my VPN with wifi tether on my phone.
Since it appears this is a phone issue, not a network, I cant help but wonder if the roaming had anything to do with it. I had an LTE signal with BTL and although the connection was a lot slower than home network, all I can say is it worked there, and not here. The primary difference in the phone config was roaming.
I havent even bothered trying to force roaming somehow and check on it, but all if this might help someone...
ma...@gmail.com
The configuration change on my router in post #236 was to allow the WAN ping as described here https://help.ui.com/hc/en-us/articles/115003146787-UniFi-UDM-USG-Firewall-How-to-Enable-ICMP-on-the-WAN-Interface
I get the same issue, VPN from oher WLAN was working fine, but not from my mobile phone. From that point I had discovered that the Unifi solution works only with IPV4 network addresses too.
I'm wondering, that with similar settings the issue is not solved for other.
I get the same issue, VPN from oher WLAN was working fine, but not from my mobile phone. From that point I had discovered that the Unifi solution works only with IPV4 network addresses too.
I'm wondering, that with similar settings the issue is not solved for other.
rh...@gmail.com
I am now running into this issue, it has been really frustrating!
I have tested this with 2 separate Pixel 3a phones and both disconnect from the L2TP VPN on my Ubiquity UDMPro at exactly 93 seconds every single time.
Both Pixels are fully updated (Android 11, build RQ3A.210605.005).
I have tested the same setup with a Nexus 5X (Android 8.1.0) and it worked fine.
Tested with an iPhone and it worked fine as well.
I have tried enabling ICMP on the WAN Local interface (with separate Echo Request and Echo Reply Rules, as well as trying a ICMP/Any rule as well), but the issue persists.
I have also tried disabling 'Internet Threat Management' (while ICMP was allowed) on the UDM Pro but again the issue persists.
I still have a few months left of my warranty so am considering trying to return it as defective.
I would really rather not though as I haven't had any other issues with it (and don't want to be without a phone while it is getting sorted).
My options at this point really feel like buy a different phone or ignore the $700 router I purchased specifically to have a VPN between my phone and home :|
I have tested this with 2 separate Pixel 3a phones and both disconnect from the L2TP VPN on my Ubiquity UDMPro at exactly 93 seconds every single time.
Both Pixels are fully updated (Android 11, build RQ3A.210605.005).
I have tested the same setup with a Nexus 5X (Android 8.1.0) and it worked fine.
Tested with an iPhone and it worked fine as well.
I have tried enabling ICMP on the WAN Local interface (with separate Echo Request and Echo Reply Rules, as well as trying a ICMP/Any rule as well), but the issue persists.
I have also tried disabling 'Internet Threat Management' (while ICMP was allowed) on the UDM Pro but again the issue persists.
I still have a few months left of my warranty so am considering trying to return it as defective.
I would really rather not though as I haven't had any other issues with it (and don't want to be without a phone while it is getting sorted).
My options at this point really feel like buy a different phone or ignore the $700 router I purchased specifically to have a VPN between my phone and home :|
al...@gmail.com
You can try another VPN protocol: openvpn for example.
rh...@gmail.com
I suspect that will be my eventual work around. The whole point of getting a router that supported a VPN that my device also is supposed to support was not having to rely on additional servers and apps. I am probably just venting at this point. I am feeling a bit silly to have spent so much on networking gear now that I can't use one of the main reasons I bought it.
jr...@gmail.com
This has been ignored by Google for almost 3 years.
They acknowledged the issue, but are not planning on fixing it. it's blocked by issue#https://issuetracker.google.com/issues/119076193
Either stop using L2TP/IPSec, or stop using Google phones.
They acknowledged the issue, but are not planning on fixing it. it's blocked by issue#
Either stop using L2TP/IPSec, or stop using Google phones.
du...@gmail.com
I recommend stopping using L2TP/IPsec. It's very complex under the hood,
the FreeSWAN / LibreSWAN / StrongSWAN stuff is complex to configure for all
the different cases, and it's complex to configure on the phone too.
All the cool kids are using Wireguard -- free, libre, simple, secure,
supported almost everywhere, and much easier to configure than IPsec. They
have a fantastic Android app and there's excellent third party support for
Ubiquiti's USG:https://github.com/WireGuard/wireguard-vyatta-ubnt .
On Fri, Jul 2, 2021 at 5:28 PM <buganizer-system@google.com> wrote:
the FreeSWAN / LibreSWAN / StrongSWAN stuff is complex to configure for all
the different cases, and it's complex to configure on the phone too.
All the cool kids are using Wireguard -- free, libre, simple, secure,
supported almost everywhere, and much easier to configure than IPsec. They
have a fantastic Android app and there's excellent third party support for
Ubiquiti's USG:
On Fri, Jul 2, 2021 at 5:28 PM <buganizer-system@google.com> wrote:
rh...@gmail.com
Thanks, I will check that out :)
aw...@waretec.com
To echo others, Google refuses to fix this issue. Whatever their reason,
incompetence, laziness, we'll never know. It's been years...
WireGuard (or OpenVPN) on a Ubiquiti router running Vyatta, or WireGuard
(or OpenVPN) on a RPi as a VPN concentrator if you have a Ubiquiti device
running UnifiOS.
Problem solved.
On Fri, Jul 2, 2021, 8:26 PM <buganizer-system@google.com> wrote:
incompetence, laziness, we'll never know. It's been years...
WireGuard (or OpenVPN) on a Ubiquiti router running Vyatta, or WireGuard
(or OpenVPN) on a RPi as a VPN concentrator if you have a Ubiquiti device
running UnifiOS.
Problem solved.
On Fri, Jul 2, 2021, 8:26 PM <buganizer-system@google.com> wrote:
du...@gmail.com
Wireguard is an order of magnitude faster than OpenVPN, has better
assured/minimum security properties, and is even simpler.
If you need to do later 2 tunneling OpenVPN rocks, but people on this bug
are not those people. :)
On Fri, Jul 2, 2021, 18:35 <buganizer-system@google.com> wrote:
assured/minimum security properties, and is even simpler.
If you need to do later 2 tunneling OpenVPN rocks, but people on this bug
are not those people. :)
On Fri, Jul 2, 2021, 18:35 <buganizer-system@google.com> wrote:
ad...@google.com
The issue has been fixed in Android S and it will be available in a future build.
br...@gmail.com
ai...@gmail.com
Will this fix only be coming to Android S and later builds?
[Deleted User] <[Deleted User]>
It has been broken for 4 or 5 iterations of android and is still yet to be assigned to an engineering team so my guess would be no it will never be fixed because Google don't give a dam about it
Seriously give them a call about it there attitude is aporling
Look at this thread not 1 response from Google in nearly 3 years
My advice vote with your wallet get your hardware from other suppliers let's be honest it won't put a dent in there profit but at least they won't have your money and you might get a phone that works
Seriously give them a call about it there attitude is aporling
Look at this thread not 1 response from Google in nearly 3 years
My advice vote with your wallet get your hardware from other suppliers let's be honest it won't put a dent in there profit but at least they won't have your money and you might get a phone that works
ra...@gmail.com Restricted+
Restricted+
Comment has been deleted.
as...@gmail.com
This is still borked. and yet the status says ""fixed"
in...@gmail.com
I gave up on Google a long time ago in expecting a fix... similar to how they still refuse to implement DHCPv6 and won't play nice with windows DNS servers for IPV6 address registration even using SLAAC with RD adverts. Furthermore they have hard-coded their DNS servers in most of their devices purposefully ignoring network DHCP assignments of DNS servers. Their do no evil has become a major security risk, in my opinion. I have since implemented OpenVPN instead of L2TP. It seems to work fine. Welcome to the tech oligopolies folks! Until the feds have the gumption to take on "Ma Google" your stuck with what you get.
Get BlueMail for Android
On Aug 1, 2021, 7:52 AM, at 7:52 AM, buganizer-system@google.com wrote:
Get BlueMail for Android
On Aug 1, 2021, 7:52 AM, at 7:52 AM, buganizer-system@google.com wrote:
al...@gmail.com
please fix it in android 11, i just keep connected 1minute30second and after that i can't connected to internet but vpn says still connected. pls fix it.
btw i am in L2TP/IPsec
and i know in android 12 there is no option to L2TP, it seems google erase it :(
btw i am in L2TP/IPsec
and i know in android 12 there is no option to L2TP, it seems google erase it :(
fr...@boukamp.net
Yep... This is still not working.. L2TP connection between my UDM Pro and my Pixel 5 won't work.. other devices (including Android phones) have no issues connecting to the UDM Pro via that same L2TP connection...
Tried it again with other Pixel 5 phones.. same issue.
Google, how long does this take you to fix? Looking rather unprofessional...
Could you at least provide an update, please?
Tried it again with other Pixel 5 phones.. same issue.
Google, how long does this take you to fix? Looking rather unprofessional...
Could you at least provide an update, please?
lu...@hotmail.com
Considering L2TP looks like it's being depreciated in Android 12, I think it's fair to say this issue isn't going to get fixed.
[Deleted User] <[Deleted User]>
It was never getting fixed why bother if it's hard just stop supporting it hay Google
ha...@gmail.com
Honest question and definitely not trying to be a smart ass since I hasn't been on many issue trackers. Doesn't reply #252 mean this problem has been resolved for future releases of Android? I.E., Android S / Snow Cone / 12? If that's the case aren't we just waiting a few more weeks for the final RC? Or is it like #261 says and L2TP is being marked as obsolete and that's the 'fix?'
lu...@hotmail.com
Updated to Android 12. Issue still present and new L2TP connections cannot be created.
If there was any hope, it's gone now.
If there was any hope, it's gone now.
lo...@gmail.com
Pre-created (before migrating to Android 12) VPN connections still dropping
ha...@gmail.com
That's disappointing.
This may not be the place to discuss this for more than a few reasons, but has anyone still attached to this tracker seen VPN stability related improvements with 3rd party roms like GrapheneOS / LineageOS?
This may not be the place to discuss this for more than a few reasons, but has anyone still attached to this tracker seen VPN stability related improvements with 3rd party roms like GrapheneOS / LineageOS?
al...@gmail.com
As many ppl mentioned here just use WireGuard instead. It's much better!
du...@gmail.com
I definitely do not understand the situation where people who do not currently use third party ROMs are thinking about using third party ROMs instead of Wireguard.
L2TP/IPsec was a good option once. Now the only reason to use it is if you somehow can't use Wireguard. If you have to use L2TP/IPsec, try the StrongSWAN app. I don't use it, but it has 4.3 stars on Google Play so it probably works.
L2TP/IPsec was a good option once. Now the only reason to use it is if you somehow can't use Wireguard. If you have to use L2TP/IPsec, try the StrongSWAN app. I don't use it, but it has 4.3 stars on Google Play so it probably works.
ha...@gmail.com
"I definitely do not understand the situation where people who do not currently use third party ROMs are thinking about using third party ROMs instead of Wireguard."
Fear of the unknown. Someone who knows their way around a customized Android phone isn't inherently network savvy at the levels currently being discussed. I would put myself in that category.
That being said, I'm climbing the learning curve and making my way towards wireguard. Goodbye L2TP
Fear of the unknown. Someone who knows their way around a customized Android phone isn't inherently network savvy at the levels currently being discussed. I would put myself in that category.
That being said, I'm climbing the learning curve and making my way towards wireguard. Goodbye L2TP
lu...@hotmail.com
StrongSwan stopped supporting L2TP from what I can see. Unfortunately I can't just run Wireshark or OpenVPN because it's my work's network and their Meraki MX64 for some stupid reason only supports L2TP right now. Google clearly ain't fixing the problem and Cisco certainly doesn't seem in a hurry to provide a different VPN client option for that model.
Right now I'm left with either dealing with it, convincing the business to buy something else for something only I'm experiencing, buying a new phone that hopefully isn't borked, or remoting into my home PC and then connecting from there, a not fast or fun experience. Thankfully my needs to use it are few and rare between, but it sucks that it's broken, especially when it was fine for years beforehand
Right now I'm left with either dealing with it, convincing the business to buy something else for something only I'm experiencing, buying a new phone that hopefully isn't borked, or remoting into my home PC and then connecting from there, a not fast or fun experience. Thankfully my needs to use it are few and rare between, but it sucks that it's broken, especially when it was fine for years beforehand
be...@gmail.com
Pixel 5a with Android 11 still refuses to connect to Ubiquiti UDMP. Grrr. Please fix.
fl...@gmail.com
Comment has been deleted.
th...@gmail.com
Google dropped support for l2tp. This will not get fixed. Android 12 does
not even have this as an option anymore.
On Sun, Nov 28, 2021, 3:48 PM <buganizer-system@google.com> wrote:
not even have this as an option anymore.
On Sun, Nov 28, 2021, 3:48 PM <buganizer-system@google.com> wrote:
Description
Hardware/Software: Pixel 2 XL on latest Pie build (PPR2.181005.003) and Google Fi
Steps to reproduce: Set up a VPN connection using L2TP/IPSec PSK as the Type, attempt to connect.
Observed behavior: Connection either hangs forever and never connects, or 'connects' but is unable to pass traffic
Expected behavior: VPN connects successfully and passes traffic
There seem to be some different issues at play, there were some incompatibilities with certain encryption schemes that seem to have been resolved at this point, but it's still not working smoothly. I did some testing during the times when the VPN connects but fails to pass traffic, and that seems to be caused by an MTU mismatch between the ppp0 tunnel interface and the LTE radio interface. Manually editing the MTU (ifconfig ppp0 mtu 1388) resolves that temporarily, although the change is lost every time the interface changes state (ie reboot or roaming to/from LTE/WiFi) and it doesn't really explain why sometimes it fails to connect at all. That I think may be related to some sort of 464XLAT implementation by Tmobile, who Fi is using as an underlying carrier, since they have gone IPv6-only and the endpoint for the VPN is IPv4-only.
Because I know at some point someone will try to blame the server on the other end, it's enterprise-grade Cisco gear running a standard configuration, so simply put, it's not the problem here. I have access to run pcaps from the endpoint to help troubleshoot, but this seems solidly like an Android/Fi networking issue.