Route all traffic through tunnel?

Welcome to the forums. The easiest way I know would be in 3 steps. 1) Create a policy allowing all traffic down the tunnel (and a matching one on the far end) 2) Create a policy route switching all source traffic from that subnet down the tunnel. 3) Create a static route (a second default route) with the same distance and priority as your first, but pointing down the tunnel. This will only work if the tunnel has been created in interface mode on both ends. This way you have an interface on which to add an IP address for routing. Hope that helps. (By the way, I' m doing exactly that now, and it works like a charm. When the tunnel is down, traffic still routes to the Internet via the other local policy(s). When the tunnel comes up, all traffic switches over to the tunnel.)

IMHO you don' t need the policy route. On the contrary, the policy route will obsolete the second default route. If you just use the second default route with slightly lesser priority (translate: " cost" ) then traffic to the internet will prefer the tunnel. If the tunnel goes down, the second default route will be deleted (check Gateway Detection) and the first default route is used instead.