@caveboy 10.1.10.150---10.1.10.160 and your LAN IP are in the same network segment, which causes this problem. You can change the VPN IP Pool to 10.1.20.150--10.1.20.160 to fix the issue.

@Yannie 

What should I put in the remote subnet field? My IP range at home is 192.168.1.0 mask is 255.255.255.0. My office network starts at  10.1.10.0 with a mask of 255.255.255.0 What should I put in there as the IP number? What does the /means after the IP number? Thank You from a Newbie

Trying to sort out something similar now and I'm looking up CIDR notation.

https://www.ionos.com/digitalguide/server/know-how/cidr-classless-inter-domain-routing/

Your 10.1.10.10 network with a subnet mask of 255.255.255.0 encompasses addresses 10.1.10.1 to 10.1.10.255. 10.1.10.10 is inside this.

This is expressed in CIDR notation as: 10.1.10.1/24.

Your VPN IP pool is 10.1.10.150 - 10.1.10.160. This is inside 10.1.10.1/24 and Omada will not allow this due to possible conflicts.

The smallest VPN IP pool you can use is a /29 which encompasses 8 addresses according to the link I posted. If you want more than this you can go all the way up to a /24, but you cannot use anything that overlaps with your LAN pool.

May I suggest a VPN pool of 10.1.11.1/29?