I noticed that in recent versions of WARP, you can NOT include any IP address in 10.1.10.0/24 as a valid tunneled private network. Any IP in the 10.1.10.0/24 range gets ignored and NOT populated in the routing table.
Why? This is quite inconvenient as I do have some existing private network/address in this range that needs to be accessed by WARP.
Inclusion in a tunnel config does not change the client config for any IP address range.
Are you talking about the Warp client split tunnel settings? If so what have you set specifically for your split tunnel config?
Understood. I was talking about the “private network” setting in the tunnel config, which is also “included” in the split tunnel setting of the warp client.
I have tried to use “10.1.10.0/24” and some individual IPs in this range, which didn’t work (network not reachable). I also tried some other 10.x ranges such as 10.1.1.0/24, which worked as expected.