A simple checkbox you can click next to a routing rule that adds the respective firewall rules to make it a NAT.
I don't see it being useful… All interfaces GUI gives you option to add routes to are either already NATed (WAN and MAN), or don't need NAT (LAN).
Besides - even if we allow adding routes via GUI to other ifaces - normally you don't need to NAT connections via specific route only - you need to NAT the whole iface.
dialog for PPTP VPN. I've tried the script in a separate thread and it works reasonably well. So it might be a good idea just to build this into the UI.
Not exactly WIP yet - but I'm considering to add the UI to replace that script. It should support multiple PPTP connections, and provide at least the same options as the current script provides. But not before the next build is released though - I'm trying to stabilize the current head now, and make another "stable" release before adding any more features.
If you would like to make a patch for PPTP client with GUI - sure, go ahead! Just let me know when you start so we don't do a double-work.
I see liyifan posted a screen shot for PPTP VPN at the beginning of the year, but I don't see a patch for it…
I'm waiting for this patch as well… Kind of silly to do all the work when it's already done :). Unfortunately, I didn't hear from liyifan since his last post on that thread.
It seems to me all using dnsmasq with VPN is useful only if you want the VPN to act as an alternate WAN. Otherwise, you really need firewall rules to say what should go across the vpn connection and what shouldn't.
Read my script more closely - it does exactly that. It uses both - dnsmasq and routing - to specify what should go across the vpn connection and what should not. All you need to do is to properly set configurable variables at the top of the script. Granted, it is only as flexible as I needed it to be for my own purposes (I didn't have any intention to publish that script while putting it together) - i.e. to be able to establish a VPN connection with the office, and route via PPTP connection only the traffic to VPN subnets (or - optionally - all traffic, depending on the DEF_GATEWAY setting). But I believe it turned out to be at least as flexible as Windows PPTP client, and even a bit more…