Hi @Daggett 

Thanks for posting in our business forum.

Daggett wrote

 

~iOS Mobile Device Config

Interface

Private Key: Redacted

Public Key: Redacted

Addresses: 192.168.192.3/32

Listen Port: 51820

MTU: 1420

DNS Servers: 1.1.1.1, 1.0.0.1

 

Peer

Public Key: Redacted

Preshared Key: Redacted

Endpoint: Redacted:51820

Allowed IP's: 0.0.0.0/0, 192.168.192.0/32, local lan range/24

Exclude Private IP's: None

Persistent Keepalive: 25

 

 

What is this subnet? This is a misconfig that should be fixed before I look further into the issue described.

I don't recall there are issues except for the interface misconfig which may cause a reboot issue on the new releases. So, what are the posts(links) of a similar case like yours? 

  @Clive_A 

So what you have highlighted in red is the ip range I chose to use for wireguard (it is not the actual range but one I chose to put in the post). At the time I implemented wireguard without that entry in my peer config on omada and in the wireguard app the connection would not function/connect be it iOS device or laptop. So if your saying that is a misconfiguration I must have been lucky for the past year it even worked. So should the 192.168.192.0/32 you highlighted in red be removed from both the omada peer and client configurations?

As for the post links I will try to find them unfortunately it was late at night when i found them last night. So they very well could have been on the tplink omada sub reddit as well.

  @MR.S 
Thank you for looking at my config and your suggestions on what I should try changing. When I tried your changes to my settings for the peers this is what I ended up with below and initially again had success connecting. The first three tests or so my peer was able to connect to the wireguard server and traverse the internal network to our nvr, ping the gateway, and ping 8.8.8.8. However now I am back to the handshake not completing after five seconds, retrying. I think I may try regenerating new key pairs again but even with the hokeyness of my prior config and the cleaned up simplified one you suggested I don't think key pairs are the problem seeing how they are showing the same behavior. I should also mention I have verified my dns record is correct and pointing to the right ip address before and after testing. Seems strange to me my prior wireguard server/peer configuration worked for over a year with the hokeyness in the configuration with no problems and than when I updated the router to Firmware 1.2.3 it no longer does.

~Omada Peer Config

Interface: Wireguard VPN

Endpoint (removed as suggested)

Endpoint Port: (removed as suggested)

Allow Address: 192.168.192.3/32

Persistent Keepalive: 25

Public Key: Redacted 

Preshared Key: Redacted

~iOS Mobile Device Config

Interface

Private Key: Redacted

Public Key: Redacted

Addresses: 192.168.192.3/32

Listen Port: 51820 (Did not remove)

MTU: 1420 (Did not remove)

DNS Servers: 1.1.1.1, 1.0.0.1

Peer

Public Key: Redacted

Preshared Key: Redacted

Endpoint: Redacted:51820

Allowed IP's: 0.0.0.0/0 (removed all but the one listed for full tunnel)

  @MR.S 

Here is my configuration I only have three peers technically configured at this point. Other then my redacted keys I feel your sample and my setup are near identical unless I am missing something. 

Server

List of Peers

Single Peer

iPhone XS Configuration

  @MR.S 

Nah, there is nothing that overlaps IP-wise, unfortunately. I wish it was as simple as that since that would have made this an easy fix haha. My config matches your example minus the actual keys and network range you chose in the example. Like I said before, until I updated the router to firmware 1.2.3 from 1.2.2 wireguard worked even with my original screwy configuration that I was told was messed up and wrong. I even initially get a successful connection when launching the vpn after a setting change using all the current keys. I am thinking I hit my last resort option of a full factory reset on the router.

However, I know for a fact my wireguard vpn stopped working consistently and reliably when I updated the router's firmware. That was the only change to anything on my network when it quit working.