Routing to S2S on Server LAN (Windows)

[rvn]

After some initial jubilation upon successfully accessing the VPN Gatweway LAN (Windows 10) :

viewtopic.php?p=120939&sid=adb2185141ff ... 5fdfdb5c42

I'm now trying to expand my access to several different S2S VPNs that exist within that same network (facilitated by the EdgeRouter).

LAN Gateway 192.168.0.1 (192.168.0.0 /24)
VPN Gateway 192.168.0.46
S2S Network 10.0.1.0 /24 (ER static route to ER vti0)
VPN Client 192.168.20.5

I was hoping it would be as simple as adding those routes (push) to the server config but this seems to result in the traffic being redirected back to the router and then out of the WAN rather than the S2S (vti)? The S2S is working correctly from the LAN (and can be accessed from the VPN Gateway ok) just not via the VPN?

Will i need to be routing the S2S (10.0.1.0 /24) back to the OpenVPN IP "somehow"?

Tracert (from client)

Tracing route to [10.0.1.14]
over a maximum of 30 hops:

1 41 ms 43 ms 44 ms 10.8.0.1
2 42 ms 40 ms 44 ms 192.168.0.1
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
.....etc


route print (client)

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.20.1 192.168.20.5 50
10.0.1.0 255.255.255.0 10.8.0.1 10.8.0.2 257
10.8.0.0 255.255.255.0 On-link 10.8.0.2 257
10.8.0.2 255.255.255.255 On-link 10.8.0.2 257
10.8.0.255 255.255.255.255 On-link 10.8.0.2 257
127.0.0.0 255.0.0.0 On-link 127.0.0.1 331
127.0.0.1 255.255.255.255 On-link 127.0.0.1 331
127.255.255.255 255.255.255.255 On-link 127.0.0.1 331
192.168.0.0 255.255.255.0 10.8.0.1 10.8.0.2 257
192.168.20.0 255.255.255.0 On-link 192.168.20.5 306
192.168.20.5 255.255.255.255 On-link 192.168.20.5 306
192.168.20.255 255.255.255.255 On-link 192.168.20.5 306
192.168.149.0 255.255.255.0 10.8.0.1 10.8.0.2 257
192.168.210.0 255.255.255.0 10.8.0.1 10.8.0.2 257
wan.wan.wan.wan 255.255.255.255 192.168.20.1 192.168.20.5 306
224.0.0.0 240.0.0.0 On-link 127.0.0.1 331
224.0.0.0 240.0.0.0 On-link 10.8.0.2 257
224.0.0.0 240.0.0.0 On-link 192.168.20.5 306
255.255.255.255 255.255.255.255 On-link 127.0.0.1 331
255.255.255.255 255.255.255.255 On-link 10.8.0.2 257
255.255.255.255 255.255.255.255 On-link 192.168.20.5 306
===========================================================================

[rvn]

RESOLVED:
Yes, i needed to add the 10.8.0.0 /24 subnet into the relevant config of the remote S2S network (of course)