Show Posts
1
18.7 Legacy Series / How to configure outbound access to PPTP and IPSEC/L2TP?
« on: August 07, 2018, 01:00:22 pm »
Cheers,
I'm testing opnSense after years of pfSense and like what I see - but I was not able to get LAN users connect to external PPTP and IPSEC/L2TP servers.
Version is 18.7 on Hyper-V, DSL-Modem comes via VLAN-tagged interface.
Internet access is working
Inbound NAT to a Windows-PPTP server works (2 NAT rules, 1 with PPTP, one with GRE)
Outbound PPTP does not work (fails imidiately)
Outbound IPSEC/L2TP also does not work (times out after a while)
PPTP module is not installed, IPSec is deactivated on the firewall. Outbound NAT rules are generated automatically (not hybrid).
The internal IP address in question has been given full access to the internet (IPv4, any protocols).
I deleted the inbound NAT for PPTP as a test, did not change the behaviour.
Seems I missed something, if anyone has any suggestion to try or documentation to read, please answer.
I'm testing opnSense after years of pfSense and like what I see - but I was not able to get LAN users connect to external PPTP and IPSEC/L2TP servers.
Version is 18.7 on Hyper-V, DSL-Modem comes via VLAN-tagged interface.
Internet access is working
Inbound NAT to a Windows-PPTP server works (2 NAT rules, 1 with PPTP, one with GRE)
Outbound PPTP does not work (fails imidiately)
Outbound IPSEC/L2TP also does not work (times out after a while)
PPTP module is not installed, IPSec is deactivated on the firewall. Outbound NAT rules are generated automatically (not hybrid).
The internal IP address in question has been given full access to the internet (IPv4, any protocols).
I deleted the inbound NAT for PPTP as a test, did not change the behaviour.
Seems I missed something, if anyone has any suggestion to try or documentation to read, please answer.