Actions
Bug #13099
closed
Static routes to destinations at L2TP clients are not re-added after a client reconnects
Start date:
Due date:
% Done:
100%
Estimated time:
Plus Target Version:
22.05
Release Notes:
Default
Affected Version:
2.6.0
Affected Architecture:
Description
How to recreate:
- Create L2TP VPN
- Create a static route to the subnet behind L2TP VPN client
- Disconnect L2TP VPN client
- Reconnect L2TP VPN client
- route is not re-added
- Disable the static route
- Enable the static route
- route is added to diagnostics -> routes
The static route should be automatically re-added when the L2TP interface is up, i.e. via /usr/local/sbin/vpn-linkup-l2tp
Updated by Viktor Gurov over 4 years ago
- Target version set to 2.7.0
- Plus Target Version set to 22.05
Updated by Jim Pingle over 4 years ago
- Status changed from New to Pull Request Review
Updated by Viktor Gurov over 4 years ago
- Status changed from Pull Request Review to Feedback
- % Done changed from 0 to 100
Applied in changeset commit:1c04a6d44e03e2cc175b7af509f8f55eee55be82.
Updated by Jim Pingle over 4 years ago
- Subject changed from L2TP VPN static route not re-added after client reconnect to Static routes to destinations at L2TP clients are not re-added after a client reconnects
Updating subject for release notes.
Updated by Viktor Gurov over 4 years ago
- Status changed from Feedback to New
Updated by Jim Pingle over 4 years ago
- Status changed from New to Pull Request Review
Updated by Viktor Gurov over 4 years ago
- Status changed from Pull Request Review to Feedback
Updated by Jim Pingle about 4 years ago
- Status changed from Feedback to Resolved
Looks good. Following the procedure above, the route goes away when the client disconnects and comes back when the client reconnects.
Actions
Also available in: Atom