https://redmine.pfsense.org/https://redmine.pfsense.org/favicon.ico?16780521162020-04-01T18:03:43ZpfSense bugtrackerpfSense - Bug #10407: L2TP static route not re-added after connection down/uphttps://redmine.pfsense.org/issues/10407?journal_id=453572020-04-01T18:03:43ZFederico Chiaravalli
<ul></ul><p>Better explanation on Reddit: <a class="external" href="https://www.reddit.com/r/PFSENSE/comments/dt6181/static_route_problem_with_l2tpipsec_vpn/">https://www.reddit.com/r/PFSENSE/comments/dt6181/static_route_problem_with_l2tpipsec_vpn/</a></p> pfSense - Bug #10407: L2TP static route not re-added after connection down/uphttps://redmine.pfsense.org/issues/10407?journal_id=453622020-04-02T07:15:39ZJim Pingle
<ul><li><strong>Category</strong> set to <i>Interfaces</i></li><li><strong>Status</strong> changed from <i>New</i> to <i>Needs Patch</i></li><li><strong>Start date</strong> deleted (<del><i>04/01/2020</i></del>)</li></ul><p>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.</p>
<p>Though the routing behavior as stated is undesirable, I don't see us putting internal resources toward supporting this use case.</p>
<p>If someone wants to submit a PR to correct the behavior, we can certainly consider it.</p> pfSense - Bug #10407: L2TP static route not re-added after connection down/uphttps://redmine.pfsense.org/issues/10407?journal_id=492512020-11-06T05:12:53ZViktor Gurov
<ul><li><strong>Affected Version</strong> set to <i>2.5.0</i></li></ul><p>Fix:<br /><a class="external" href="https://gitlab.netgate.com/pfSense/pfSense/-/merge_requests/39">https://gitlab.netgate.com/pfSense/pfSense/-/merge_requests/39</a></p> pfSense - Bug #10407: L2TP static route not re-added after connection down/uphttps://redmine.pfsense.org/issues/10407?journal_id=492602020-11-06T10:40:23ZJim Pingle
<ul><li><strong>Status</strong> changed from <i>Needs Patch</i> to <i>Pull Request Review</i></li><li><strong>Target version</strong> set to <i>2.5.0</i></li><li><strong>Affected Version</strong> deleted (<del><i>2.5.0</i></del>)</li></ul> pfSense - Bug #10407: L2TP static route not re-added after connection down/uphttps://redmine.pfsense.org/issues/10407?journal_id=493192020-11-09T07:51:20ZRenato Botelhorenato@netgate.com
<ul><li><strong>Status</strong> changed from <i>Pull Request Review</i> to <i>Feedback</i></li><li><strong>Assignee</strong> set to <i>Viktor Gurov</i></li></ul><p>PR has been merged. Thanks!</p> pfSense - Bug #10407: L2TP static route not re-added after connection down/uphttps://redmine.pfsense.org/issues/10407?journal_id=493222020-11-09T08:00:10ZViktor Gurov
<ul><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li></ul><p>Applied in changeset <a class="changeset" title="Auto add static routes for PPP interfaces. Fixes #10407" href="https://redmine.pfsense.org/projects/pfsense/repository/2/revisions/05af32629d9259817070a72f388a7d4c4835d76d">05af32629d9259817070a72f388a7d4c4835d76d</a>.</p> pfSense - Bug #10407: L2TP static route not re-added after connection down/uphttps://redmine.pfsense.org/issues/10407?journal_id=493602020-11-10T14:24:40ZJim Pingle
<ul><li><strong>Category</strong> changed from <i>Interfaces</i> to <i>L2TP</i></li></ul> pfSense - Bug #10407: L2TP static route not re-added after connection down/uphttps://redmine.pfsense.org/issues/10407?journal_id=495852020-11-18T22:47:36ZAlhusein Zawi
<ul></ul><p>route is not deleted if reconnecting.</p>
<p>Static route will be deleted if L2TP interface is down.</p>
<p>Static route will be added if L2TP interface is up/reconnected.</p>
<p>2.5.0.a.20201118.1850</p> pfSense - Bug #10407: L2TP static route not re-added after connection down/uphttps://redmine.pfsense.org/issues/10407?journal_id=495862020-11-18T23:05:19ZAlhusein Zawi
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Resolved</i></li></ul>