Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    [SOLVED] Port Forwarding with OpenVPN Client (FW Rule Issue)

    Scheduled Pinned Locked Moved OpenVPN
    3 Posts 2 Posters 2.6k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • G Offline
      glego
      last edited by

      So I'm trying to set up some services behind an OpenVPN Client Host.

      So far I can see in Wireshark that the packages are reaching the receiver but can't complete.


      https://prnt.sc/hj6q9w

      My Configuration

      • Interfaces
          WAN
          LAN
          VLAN1
          OVPN (none/none)

      • NAT Port FWD
          Interface: OVPN
          Protocol: TCP/UDP
          Destination: OVPN Addresses
          Port Range: 27687
          Redirect IP: MyHostOnVlan1
          Redirect Port: 27687

      • NAT Outbound
        Interface: OVPN
        Protocol: Any
        Source: MyHostsOnVlan1 Subnet

      • Firewall Rules VLAN 1
          Source: MyHostsOnVlan1 Subnet
          Dest: Any
          Gateway: OVPN

      • Firewall Rules OVPN
          Source: Any
          Destination: MyHostOnVlan1
          Port: 27687

      • Firewall OpenVPN
        Source: Any
        Destination: Any

      When I check the states I get

      Interface: OVPN / TCP external:54270 -> MyHostOnVlan1:27687 (MyOpenVPNIP:27687) SYN_SENT:ESTABLISHED
      Interface: VLAN 1 / TCP external:54270 -> MyHostOnVlan1:27687 ESTABLISHED:SYN_SENT

      Thanks for your time!

      1 Reply Last reply Reply Quote 0
      • DerelictD Offline
        Derelict LAYER 8 Netgate
        last edited by

        Make sure the inbound traffic is NOT matched by rules on the OpenVPN tab (disable all rules there) and IS matched by rules on the OVPN tab. That will get reply-to functioning.

        Chattanooga, Tennessee, USA
        A comprehensive network diagram is worth 10,000 words and 15 conference calls.
        DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
        Do Not Chat For Help! NO_WAN_EGRESS(TM)

        1 Reply Last reply Reply Quote 0
        • G Offline
          glego
          last edited by

          @Derelict:

          Make sure the inbound traffic is NOT matched by rules on the OpenVPN tab (disable all rules there) and IS matched by rules on the OVPN tab. That will get reply-to functioning.

          Removing the rules from the OpenVPN tab resolved the issue. Thanks!

          1 Reply Last reply Reply Quote 0
          • First post
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.