Outbound PPTP VPN Connection broken AGAIN
-
Ah I see. Well then that would not be too much of an issue for me. Thanks.
-
It means the old limitations are in place:
- You can't make outbound PPTP connections if you are running a PPTP server
- You can't make two outbound PPTP connections to the same remote PPTP server
jimp, can you clarify? Is the pptp proxy required to maintain outbound pptp connections?
-
To maintain them? No, but to bypass the restrictions I mentioned, yes.
-
Okay, I've been unable to maintain an outbound VPN connection from a PC on the LAN to an outside server for longer than a few minutes with the inbound PPTP VPN disabled (no redirect) and the pf scrub disabled.
Where else can I look to troubleshoot this?
-
Not sure what that might be. I had a PPTP connection up (and practically idle) from behind a 2.0 box to a 2.0 box for more than a half hour the other day.
-
I must say if I do not run a ping to the destination PPTP VPN server my connection also dies…
-
This gets better!
Now I can't even establish a connection.
Other than the default outbound rule, any others that outbound PPTP needs? I believe I deleted the inbound rules when turning disabling the PPTP server.
-
Shouldn't be anything that it touches special, if you can't establish a PPTP connection the most likely cause is that you've already got a PPTP connection going on another machine to that same remote system.
-
Well, I can guarantee that's not the case. I have, however made multiple attempts from my machine.
I don't see anything in states with the remote server's IP, so I'm not sure what it could be.
-
Reboot fixed it.
Dunno why a reboot was required, but I'm not complaining.
-
Since the issue won't be fixed until 2.1 is there a timeline for at least a beta of 2.1 that will contain the fix? We've been dealing with the issue in hopes that a fix was coming sometime soon, but if it's going to be several more months then we'll probably want to switch to a different firewall that supports pptp until PFSense is stable in that regard, and then switch back. Also if there is anything I can do to assist in helping the developers fix the issue I am willing.
-
No ETA. We have to release 2.0 before we can even think about ALPHAs of 2.1, let alone BETAs.
