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

    Problem with TCP and GRE tunnel

    Scheduled Pinned Locked Moved General pfSense Questions
    64 Posts 3 Posters 7.5k 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.
    • S
      StomperG @stephenw10
      last edited by

      @stephenw10 All ips I have are "single" i dont have an entire subnet

      1 Reply Last reply Reply Quote 0
      • stephenw10S
        stephenw10 Netgate Administrator
        last edited by

        Yeah those IPs are inconveniently not in a single /29!

        But what subnet sizes (masks) do you have set on the interfaces?

        S 1 Reply Last reply Reply Quote 0
        • S
          StomperG @stephenw10
          last edited by

          @stephenw10

          Local pf:
          85dd52c0-40b9-4b17-ac6a-d9dfe1064e3d-image.png
          7f5b282b-9b1c-47cf-a122-7373bf85a918-image.png
          9a9fec18-7a7f-4078-a301-3d107feee0a8-image.png

          VPC pf:
          a629ce5c-2652-48c2-a6d1-c70f9498f3a5-image.png
          313dd502-4266-4a7f-8c54-3a3eb0606b62-image.png

          1 Reply Last reply Reply Quote 0
          • stephenw10S
            stephenw10 Netgate Administrator
            last edited by

            OK so everything is /24 and thus you have the same subnet at both ends on the tunnel. Hence, routing conflict with that iperf command and anything else sourced from the firewall itself.

            Really you want those things is different subnets but because the remote WAN is using .132 you can't use /25 there.

            I would try to set the gateway as outside the subnet. There's a setting for that in the advanced gateway settings: 'Use non-local gateway'

            You can then set the remote WAN subnet to something much smaller, /32 even.

            Then you can set the other IPs in a different subnet such as 185.113.141.208/28. You can add that as the static route on the remote pf and then use the IPs directly on the local pf.

            The local pf LAN should use one of those IPs.

            As an alternative to all of that you could just add all the IPs at the remote side as VIPs and then NAT the traffic to/from them and use private IPs at the local LAN.

            Steve

            1 Reply Last reply Reply Quote 0
            • stephenw10S stephenw10 referenced this topic on
            • First post
              Last post
            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.