Actions
Bug #11484
closed
Adding static routed subnets destroys the route at routing table
Status:
Not a Bug
Priority:
Normal
Assignee:
-
Category:
WireGuard
Target version:
-
Start date:
02/20/2021
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.5.0
Affected Architecture:
Description
Adding static routed subnets to wireguard allowed subnets destroys the static route.
The subnet is then just added to wg0 but the static route and gateway is deleted at the routing table.
So the static route is not working anymore.
Updated by Jim Pingle about 3 years ago
- Status changed from New to Not a Bug
- Priority changed from High to Normal
By doing that you have added two static routes (since Allowed IPs entries get route table entries), so naturally one will clobber the other. It's a misconfiguration.
Updated by Dirk Steingäßer about 3 years ago
Sorry, yes you gave me the missing hint. To reach a static routed subnet via wireguard you just need to add the gateway network address to wireguard "allowed subnets". If this is reachable via wireguard then the static route is via this gateway network is reachable, too becuase it is already within the routing table.
thanks sir!
Actions