That could be a way.
For IPSec VPN, use the Interface mode (as opposed to policy-based VPN) when you create the tunnels. The tunnel then is just a port like other ports. You can use static routes or RIP for it. As the topology is not that dynamic I personally would go with static routes.
There are 2 places where multiple subnets come into play:
- the quick mode selectors in phase2
- the policies
For phase2, you need to define the QM selectors using address groups. You can do that from the CLI only. Would be worth a try if you can make it work with a wildcard QM, i.e. ' 0.0.0.0/0' .
Policies are easy: you need one ACCEPT policy from ' tunnel' to ' VLANx' for each VLAN.
For a dial-in VPN you don' t need a static route back to the tunnel, it will be created on the fly.
On the remote side, assuming you use Forticlient, enter all VLANs into the ' network behind tunnel' field. That will create the routes when the tunnel connects.
Ede Kernel panic: Aiee, killing interrupt handler!