Thanks for the reply, so are you saying just a straight IPsec (L2TP server on the CHR and L2TP on the clients?) with routes opposed to policies would do the job ?
Yes, just L2TP over IPsec with static routes. Don’t forget not to masq your local subnets. Or, if all your equipment is MikroTik, then you can create gre over ipsec with static routes.
L2TP over IPsec could be trouble when all those remote systems are behind the same or a couple of CGNAT.
In that case it could be safer to use the (otherwise inferior) TCP tunnels like SSTP or OVPN.
As this is a low-bandwidth situation it will likely work OK.
Or you can use a GRE tunnel over manually configured IPsec, which means you can manually set tunnel mode for the IPsec transport and thus avoid problems with multiple clients behind the same NAT.
Sure, but that is a complicated solution that does not scale well.
SSTP has terrible performance under load (so does OpenVPN over TCP) but for purposes like some light remote management and monitoring it is fine.
Setting up an SSTP tunnel per remote device is quite simple, just create the server and a network for it (on a loopback) and add a user for each
remote device with username, password and remote IP address. On the remotes just setup the SSTP with user and password.
This assumes the SSTP will be made to the router that also runs the Dude. If not, there will be the additional issue of setting a route.
IPv6 is free in AWS I believe. That may be a way to escape the CGNAT. That said I think SSTP is your best solution. Even with IPv6 SSTP or L2TP/IPSEC would be a more flexible and light configuration. If only MikroTik had DMVPN.
Exactly what I have done, super easy and stable so far.
I didn’t however create the loop back network… I just specify local and remote for each user and it seems to work fine… Though RoMon sadly doesn’t work…
Using a separate network on a loopback interface makes it easier to write firewall rules for your management network.
Other than that, it is not required.
RoMon requires L2 connectivity. It could work over EoIP but it is unwise to deploy EoIP unless absolutely necessary.