Project

General

Profile

Actions

Bug #13099

closed

Static routes to destinations at L2TP clients are not re-added after a client reconnects

Added by Viktor Gurov 2 months ago. Updated 26 days ago.

Status:
Resolved
Priority:
Normal
Assignee:
Viktor Gurov
Category:
L2TP
Target version:
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

Actions #1

Updated by Viktor Gurov 2 months ago

similar to #10407, but server-side

Actions #3

Updated by Jim Pingle 2 months ago

  • Status changed from New to Pull Request Review
Actions #4

Updated by Viktor Gurov 2 months ago

  • Status changed from Pull Request Review to Feedback
  • % Done changed from 0 to 100
Actions #5

Updated by Jim Pingle 2 months 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.

Actions #6

Updated by Viktor Gurov about 2 months ago

  • Status changed from Feedback to New
Actions #7

Updated by Jim Pingle about 2 months ago

  • Status changed from New to Pull Request Review
Actions #8

Updated by Viktor Gurov about 2 months ago

  • Status changed from Pull Request Review to Feedback
Actions #9

Updated by Jim Pingle 26 days 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 PDF