Once the tunnel is establish can you test to ping the LAN IP address of each router from remote side PC. Meaning from LAN 192.168.7.X PC try to ping 192.168.0.1 (assuming that this is the IP of the route). If this ping receive reply this would mean that the VPN tunnel is ok and the problem is purely routing issue.
-if ping to the remote gateway is not successful this could mean that the tunnel is not established at all, though it shows the opposite. It could be PFS mismatch. Or ESP filtered packets by the device infornt if any of the site is behind NAT
-if ping to a machine behind the router is not successful, this could be firewall on the PC itself or routing issue - usually when the gateway on the PC is not the router configured with the VPN
Have you tried creating site to site tunnels for those different subnet/Vlans?
Reason all Vlans work is because you are using a class b subnet mask of 255.255.0.0 therefore you are using Network 192.168.x.x as suppose to a class c subnet mask of 255.255.255.0 which would be network of 192.168.0.x. So now all vlans are in tunnel communication would be seen in the 192.168.x.x.
Please mark or endorse this post if this helps you!
Configure DHCP WAN Settings on the RV34x Router
A Wide Area Network (WAN) is a network that covers a broad area. A user or network of users can connect to the Internet through an Internet Service Provider (ISP) who offer...
Configure Static IP WAN Settings on the RV34x Router
A Wide Area Network (WAN) is a network that covers a broad area. A user or network of users can connect to the Internet through an Internet Service Provider (ISP) who ...