Project

General

Profile

Issue #3326

update custom routing table (table 220 by default) with new routes if new networks and routes appear

Added by Noel Kuntze 8 months ago. Updated 7 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Affected version:
5.8.2
Resolution:

Description

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.

History

#1 Updated by Noel Kuntze 8 months ago

In the same vein we could also start using throw type routes in table 220 for traffic that we don't need to handle differently from the main table.

EDIT: Why? Then we don't need to update those routes if they change in the main routing table.

#2 Updated by Noel Kuntze 7 months ago

Update: Seems the issue only occurs if strongswan starts before NetworkManager (maybe other software with the same purpose as it, too).

Also available in: Atom PDF