Client-to-Site VPN not working with Google Pixel and Android 13 (IKEv2)

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Client-to-Site VPN not working with Google Pixel and Android 13 (IKEv2)

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Client-to-Site VPN not working with Google Pixel and Android 13 (IKEv2)
Client-to-Site VPN not working with Google Pixel and Android 13 (IKEv2)
2022-12-21 14:06:27
Tags: #pixel
Model: ER605 (TL-R605)  
Hardware Version: V1
Firmware Version: 1.2.1

Are there others with Google Pixel Android 13 with VPN issues, because so far it is impossible to make a connection :(

 

I checked this TP-Link Knowlage Page couple of times (Android settings) , I am doing the same but can not get VPN working.

 

Using controller OC200 1.0 (FW 1.21.7) , controller 5.7.6

 

I even removed VPN rule , recreate, reboot.

 

Also would like to know here I can see VPN connection errors in OC200 , can not find.

 

I hope I am not alone, hope somebody could help.

 

thank you!

 

 

  0      
  0      
#1
Options
7 Reply
Re:Client-to-Site VPN not working with Google Pixel and Android 13 (IKEv2)
2022-12-22 07:32:33 - last edited 2022-12-22 07:41:50

  @VoteForPedro 

 

i think you need to have sha2 to make it work on android. ER605v1 does not support this.

 

ER605v2 support sha2 in stand alone, the only device with sha2 support in stand alone and controller mode is ER8411

 

 

  0  
  0  
#2
Options
Re:Client-to-Site VPN not working with Google Pixel and Android 13 (IKEv2)
2022-12-27 15:14:37

  @shberge thank you for your reply.

The OC200 is showing me a lot of IKEv2 options as you can see below.

But you think this will not be used/pushed to the TL-R605 v1.0 ?

 

  0  
  0  
#3
Options
Re:Client-to-Site VPN not working with Google Pixel and Android 13 (IKEv2)
2022-12-27 15:37:19

  @VoteForPedro 

 

Yepp thats correct ER605v1,v2 and ER7206 use sha1, this settings downt work on this device. only device that work is ER8411. ER605v2 work in stand alone only if you want to test that.

  0  
  0  
#4
Options
Re:Client-to-Site VPN not working with Google Pixel and Android 13 (IKEv2)
2022-12-27 20:12:58

  @shberge 

I do not want to use it as a standalone. 

 

(strange OC200 is not giving me an prompt / message like 'not supported'. Would be nice, less frustrating)

 

1) Will the new TL-R605 2.6 solve my problem? so, will it work with OC200 ánd IKEv2?

 

2) And will it be easy to migrate/replace the TL-R605 v1 with TL-R605 2.6 with OC200? (I think so, because alle settings are pushed from oc200)

 

 thank you again!

  0  
  0  
#5
Options
Re:Client-to-Site VPN not working with Google Pixel and Android 13 (IKEv2)
2022-12-28 08:24:28

  @VoteForPedro 

 

1. No ER605v2 sha2 work only in stand alone, only device that support sha2 in controller and stand alone is ER8411

2. Yes this is easy to replace a router

  0  
  0  
#6
Options
Re:Client-to-Site VPN not working with Google Pixel and Android 13 (IKEv2)
2022-12-28 10:44:22

  @shberge 

ER8411 is way to expensive crying

 

I found the specs, and now I can see indeed it only supports MD5 / SHA1 (and no SHA2) 

 

But would it be possible to have VPN with IKEv2 and SHA1 or MD5 from OC200 (ER605/TLR605)? Or am I missing something again?wink

  0  
  0  
#7
Options
Re:Client-to-Site VPN not working with Google Pixel and Android 13 (IKEv2)
2022-12-28 11:49:29 - last edited 2022-12-28 11:51:37

  @VoteForPedro 

 

You have not missing anything, that TP-Link that do dirty work, same thing with ER605v2 SHA2 work only in stand alone

 

ER605v1 have support for all protocols you se in omada controller except SHA2 section, I don't think anything work on android with SHA1 so you probably need SHA2

I have not tested IPsec on adroid myself.

 

But you can use OpenVPN on your router, this will work. download OpenVPN client in google store and import ovpn file generated on Omada Contoller

 

Maybe ER605v1 will support SHA2 in the future. I don't know.

 

  0  
  0  
#8
Options