Port Forwards stop working when VPN is connected



  • I'm having an issue where my Port forwards through NAT have been working for several years now. I used to use an openVPN client to protect some internal IP addresses however not all. I just switch VPN providers and as such re-setup my OpenVPN client. I have found that the all my NAT and port forwards stop working when I start my OpenVPN but immediately start working if I stop the VPN. I've been going through the setup for weeks and am getting frustrated and hoping that you may be able to tell me where I'm going wrong. I've also tested to see if maybe the port forwards were working just through the VPN public IP and that doesn't seem to be the case. I'll see if I can show my setup below. Any help you can offer is greatly appreciated.
    0_1540316896006_InboundNAT.PNG
    0_1540316979542_OutboundNAT.PNG
    0_1540317362484_WANRules.PNG
    0_1540317464236_LANRules.PNG
    0_1540319937085_OpenVPN.PNG
    0_1540319828859_OPENVPN2.PNG
    0_1540320075841_BuckeyeGateway.PNG
    0_1540320092301_PIAEast.PNG


  • Netgate

    You have no upstream gateway on your WAN interface so you are not getting reply-to.

    You do not have Don't pull routes checked in your OpenVPN setup so the VPN provider is pushing you a default route.

    Therefore, connections are coming into WAN, hitting the server after NAT, but replies are going out OpenVPN.

    Adding the gateway to the WAN interface will correct the port forwards because those states will then get flagged with reply-to..

    If I was going to policy route certain hosts out the OpenVPN I would also check Don't pull routes.

    And, in case anyone is wondering, this is how you provide the necessary screen shots.



  • @derelict You are a genius dear sire. I couldn't for the life of me find that problem. Thank you.



  • I am having an issue similar to this. upnp does not seem to function right with the openvpn. What solved this?