How to make traffic go between OpenVPN and Wireguard networks?

Question

openvpn

There is a VPS on which openvpn (network 10.8.0.*) and wireguard (10.7.0.*) are raised.

There are two clients with networks 192.168.1.0/32 and 192.168.0.0/32. This is an apartment and cottage.

There are also other clients that should have access to the specified networks 192...

Previously, only openVPN was configured and everything worked fine. Now I want to switch to wireguard, but a transitional period is required and the work of both openvpn and wireguard is required.

Now the network 192.168.1.0 (apartment) remains on openvpn, and 192.168.0.0 (cottage) on wireguard.

The router with wireguard connects to the server, pings on ip 10.7.0.* go back and forth, you can ping 10.8.0.1 from the router and everything will be fine, but pings to 10.8.0.* no longer go (although everything pings normally from the server itself ). There are also no pings to 192.168.1.1 (a home router connected via openvpn, 10.8.0.7).

The routes on the server are now:

# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         51.***      0.0.0.0         UG    0      0        0 eth0
10.7.0.0        0.0.0.0         255.255.255.0   U     0      0        0 wg0
10.8.0.0        0.0.0.0         255.255.255.0   U     0      0        0 tun0
51.***      0.0.0.0         255.255.255.255 UH    0      0        0 eth0
172.16.238.0    0.0.0.0         255.255.255.0   U     0      0        0 br-a453332e5303
172.17.0.0      0.0.0.0         255.255.0.0     U     0      0        0 docker0
192.168.1.0     10.8.0.2        255.255.255.0   UG    0      0        0 tun0

It is necessary that the networks behind the wg0 and tun0 interfaces see each other.

Answer 1

And here routes on the server? They are automatically created.
The following must be allowed on the server:
1. forward packets through the kernel (sysctl)
2. The firewall must allow packets to pass between networks 192.168.1.0 and 192.168.0.0 (iptables -A FORWARD xxxx -j ACCEPT), or between interfaces (iptables -A FORWARD -i xxx -o xxx -j ACCEPT).
But your end devices in both subnets must have routes to opposite subnets - each through its own VPN. Or distribute them automatically or by hand.
In general, the idea of ​​a semi-relocation and waiting for an answer here on the forum, instead of a complete migration of a summer house and an apartment, looks crooked.

Answer 2

In short, everything turned out to be simple - on a router that did not respond, it was necessary to register a route to 10.7.0.1, without it he could not answer the ping.