OpenVPN config - traffic not NATing
-
@clazmania
Yes, then presumably you're missing the outbound NAT rule.Is the outbound NAT in automatic mode?
I'd expect, that the required rule is generated automatically if it is.
Otherwise you have to add it manually. -
-
@clazmania
The source has to be your internal networks, e.g. "LAN subnets" and the translation address has to be the VPN clients address. pfSense might provide a variable for it in the drop-down. Otherwise you have to assign an interface to the VPN client instance to get it. -
-
-
@Antibiotic Thanks, I do have a similar config. The only difference is the dst port, guessing due to ISAKMP.
-
This post is deleted! -
-
-
@clazmania Are you using IPSEC VPN?
Shoud be set VPN interface not a OpenVPN itself. IDK may by you called VPN interface as OpenVPN))) -
@Antibiotic I did call it OpenVPN and that may have been a mistake. Because I have an OPENVPN and OpenVPN and I think that is causing confusion for me. I guess I can remove the config and recreate with another name. Then revisit.
-
@clazmania said in OpenVPN config - traffic not NATing:
@Antibiotic I did call it OpenVPN and that may have been a mistake. Because I have an OPENVPN and OpenVPN and I think that is causing confusion for me. I guess I can remove the config and recreate with another name. Then revisit.
Reply Quote
0Ah ))) Good luck
-
@clazmania
I don't assume, that you want to edtablish an IPSec through the OpenVPN provider. That's the only thing the ISAKMP rule is good for, however. -
@clazmania ISAKMP only use for IPsec protocol , if you use openvpn protocol set as in my example
-
@Antibiotic I just wanted to follow up on this one. I found out the problem was that I had not changed the gateway for the firewall rule, which is listed in the advanced settings. After changing the gw, voila. Darn stupid mundane details...i swear.....
Anyway, thank you for helping....
