Feature Requests

It would be very useful to add  the possibility of having more complex setups of *Remote subnet* and *Local subnet* in the [IPSec] VPN tunnel editing section.

What exactly do you need?  It will handle summery routes...  This gives it a LOT of versatility.

What exactly do you need?  It will handle summery routes...  This gives it a LOT of versatility.

What I need is being able to use something like this:

Local subnets:
192.168.0.0/24
10.0.0.0/24
172.30.1.1

Remote subnets:
192.168.1.0/24
10.10.10.8/29
10.195.56.99

In the IPSec configuration page. I'd need a more flexible setup of the encryption domains. It'd be very useful in my opinion, not just to me. I think.

IPsec does rout entires just like the route command.  Since all three are not even close, this is not trivial...  If you had 192.168.64.0/24 and 192.168.65.0/24 on one router, you could represent it as 192.168.64.0/23 in the IPsec tunnel page.  Because of the way you have your local net laid out, you need 9 tunnels on each system.  Masking that behind a GUI means less control and less understanding to the user.

Note that I have done a summery route for one client that is a /20 to a AT&T MPLS network.  It works very well with a good network design.  Any chance of re-iping your network?