Bug #10407: L2TP static route not re-added after connection down/up - pfSense - pfSense bugtracker

Actions

Copy link

Bug #10407

closed

L2TP static route not re-added after connection down/up

Added by Federico Chiaravalli about 4 years ago. Updated over 3 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

Viktor Gurov

Category:

L2TP

Target version:

2.5.0

Start date:

Due date:

% Done:

100%

Estimated time:

Plus Target Version:

Release Notes:

Affected Version:

Affected Architecture:

Description

How to recreate:
Create L2TP VPN
Create a default gw to the VPN subnet
Create the static route

route is added to diagnostics -> routes
Disconnect from VPN
route is deleted from diagnostics -> routes
Reconnect to VPN
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'm not sure if this is an intended behaviour, I googled it, and I didn't found anything related to this - so I assume that this is a bug.

Actions

Copy link

Updated by Federico Chiaravalli about 4 years ago

Better explanation on Reddit: https://www.reddit.com/r/PFSENSE/comments/dt6181/static_route_problem_with_l2tpipsec_vpn/

Actions

Copy link

Updated by Jim Pingle about 4 years ago

Category set to Interfaces
Status changed from New to Needs Patch
Start date deleted (~~04/01/2020~~)

The L2TP WAN-type interface design is not designed to be used with VPNs. It may work, but not intentionally. It is designed to be used for ISPs which require it for WAN connectivity.

Though the routing behavior as stated is undesirable, I don't see us putting internal resources toward supporting this use case.

If someone wants to submit a PR to correct the behavior, we can certainly consider it.

Actions

Copy link