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

    Routing Specific Traffic over VTI

    Scheduled Pinned Locked Moved IPsec
    9 Posts 2 Posters 1.4k Views 2 Watching
    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.
    • S Offline
      stan.fergusonsmith
      last edited by

      This post is deleted!
      S V 2 Replies Last reply Reply Quote 0
      • S Offline
        stan.fergusonsmith @stan.fergusonsmith
        last edited by

        This post is deleted!
        1 Reply Last reply Reply Quote 0
        • V Offline
          viragomann @stan.fergusonsmith
          last edited by

          @stan-fergusonsmith said in Routing Specific Traffic over VTI:

          Remote Server WAN Rules:

          Bild Text

          What's your intention? Routing this to a machine on the remote site?

          Did you add a Port forwarding rule?

          S 1 Reply Last reply Reply Quote 0
          • S Offline
            stan.fergusonsmith @viragomann
            last edited by

            This post is deleted!
            V 1 Reply Last reply Reply Quote 0
            • V Offline
              viragomann @stan.fergusonsmith
              last edited by

              @stan-fergusonsmith
              A port forwarding rule is needed for this in any case.
              In the port forwarding rule you can select an option to let pfSense create an associated firewall rule automatically or just select "pass" to allow the traffic without an explicit rule.
              Anyway both are needed.

              But there is something else. Assuming it's not an issue for you to not see the real client IP at the destination device, you can go with masquerading as well.
              So on the remote site you have to add an additional outbound NAT rule to the IPSec interface with source = any, destination = 10.11.5.0/24, translation = interface address.

              And an additional outbound NAT rule is needed on the local VPN endpoint. So you have also switch the outbound NAT into hybrid mode and add a rule:
              interface: LAN
              source: any
              dest.: 10.11.5.0/24

              These NAT rules are needed, that the destination devices send reply packets back to the local pfSense and the local to the remote. Without this they would send replies to their default gateway.

              S 2 Replies Last reply Reply Quote 0
              • S Offline
                stan.fergusonsmith @viragomann
                last edited by

                This post is deleted!
                1 Reply Last reply Reply Quote 0
                • S Offline
                  stan.fergusonsmith @viragomann
                  last edited by

                  This post is deleted!
                  V 1 Reply Last reply Reply Quote 0
                  • V Offline
                    viragomann @stan.fergusonsmith
                    last edited by

                    @stan-fergusonsmith
                    Does your application really use a static source port?? That's very unusual.
                    Most application use a random source port. So you probably have to set the source port to 'any' in the port forwarding and firewall rule.

                    S 1 Reply Last reply Reply Quote 0
                    • S Offline
                      stan.fergusonsmith @viragomann
                      last edited by

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