Letting linux be the router, allowing dynamic routes, suggestion

[Etienne Dechamps]

On 12 May 2015 at 05:13, Marcelo Pacheco <marcelo at m2j.com.br> wrote:
> The solution to all of those challenges is to have the VPN software not be
> the router, but rather just dump incoming packets to the kernel and route
> outgoing packets with the kernel in charge.

I think you can already do this in tinc by using the Forwarding =
kernel option: http://tinc-vpn.org/documentation/Main-configuration-variables.html#index-Forwarding