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

    Routing tunel Gre

    Scheduled Pinned Locked Moved General pfSense Questions
    8 Posts 2 Posters 601 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
      s_serra
      last edited by

      Hi

      I have a gre tunnel between two pfsesne.

      I have a machine with the ip 185.113.143.148 pinging continuously at 8.8.4.4 locally.
      Traffic passes through the tunnel and the remote pfsense wan interface receives the response from 8.8.4.4.

      The problem is that traffic received from 8.8.4.4 is not passing from the wan to the gre tunnel on the remote pfsense.

      I tried with that firewall rule and without success.

      e79b5ac5-c457-484e-be2b-283feb8083dd-image.png

      I tried with a static route and also without success.

      28744900-4852-4f17-ad9a-1da1f8d8744c-image.png

      Can anyone help me understand what I'm doing wrong?

      Thanks

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

        Check the states at both ends while the ping is running. Make sure you see states on the GRE interfaces at each end and the NAT state on WAN at the end it leaves.

        Check the firewall logs at each end for blocked traffic.

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

          Thanks
          I already managed to solve this problem I think it was from the states. Now another problem has arisen in the local pfsense, I wanted the traffic in the local network to communicate without leaving the network, only when access to the internet is necessary to go out through the tunnel, I tried to do the following but it is not working very well, it seems that something thing loops and I get lossy sometimes. If the rule is only to forward the traffic through the tunnel, the machines cannot communicate within the network.

          b8802f9f-2d71-4686-95e4-f97864e2424c-image.png @stephenw10

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

            Traffic between hosts inside that /28 never goes through the firewall so that pass rule you've added does nothing. You can see there are no states or bytes shown on the rule.

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

              When I remove this rule the following appears to me.

              f893ebdb-2195-42c2-83c9-644ac6c85f6a-image.png

              If I add the rule the ping works.

              637a9604-b608-4ff1-9f68-34233e10b323-image.png

              It's a bit weird

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

                Hmm, you have something bridged? What are those IPs? If is the pfSense LAN address you might hit it.

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

                  @stephenw10

                  Thanks,

                  I had misplaced the ip`s in the proxmox by putting the mask /32 instead of /24 so obviously they weren't communicating because they were on different networks.

                  Compliments

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

                    Ah, that would do it! 👍

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