Feature #3385
closed
Accommodate static routes for PPTP connections
Added by James Mills over 11 years ago.
Updated almost 5 years ago.
Description
Creating a static route on the pfSense box allows routing from the 10.20.2.0 network back across the (pptp) vpn to the 192.168.12.0 network, however as soon as the VPN disconnects, the static route is removed from the routing table (I assumed this is a correct action) though the route is still defined in the "System:Static Routes" table.
(the route in my configuration is : 192.168.12.0/24 192.168.13.2 UGS 0 12558 1456 pptpd0)
When the VPN reconnects, the static route is not reinstated and must be re-instated to bring the routing back online. This can be achieved by removal or the "System: Static Routes" entry, or simpy clicking through the Edit -> Save -> Apply screens.
(192.168.12.0/24) <-> Cisco Router (192.168.13.2 <-> 192.168.13.1 -- PPTP VPN Tunnel) pfSense <-> 10.20.2.0/24
correction :
When the VPN reconnects, the static route is not reinstated and must be re-instated to bring the routing back online. This can be achieved by removal [and re-addition of] the "System: Static Routes" entry, or simpy clicking through the Edit -> Save -> Apply screens.
- Tracker changed from Bug to Feature
- Subject changed from static route lost on vpn disconnect, not recreated on vpn reconnect. to Accommodate static routes for PPTP connections
- Category set to Routing
- Priority changed from Normal to Low
- Affected Version deleted (
2.1)
not a bug as routes on PPTP are not intended to be supported (really shouldn't do that, use something that's actually intended for site to site connectivity).
- Status changed from New to Needs Patch
PPTP is dead, and shouldn't be used in this context anyway
- Status changed from Needs Patch to Closed
Also available in: Atom
PDF