update custom routing table (table 220 by default) with new routes if new networks and routes appear
Currently, strongSwan does not update the custom routing table (table 220) when new routes or addresses appear. Also, it does not retry installing of routes for, for example, passthrough policies for which at install time were not suitable routes in the main table, but later there are. This means that the custom routing table between the following two scenarios differ in the end:
1) all networks (from passthrough and trap policies) reachable at start time
2) not all networks (from passthrough or trap policies) reachable at start time, but later they are.
Ideally strongSwan would add the routes when it can so the passthrough and trap policies work as intended in the latter case.