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

Pfsense Gre Tunnel with Mikrotik Router (Incomming Traffic Block by default deny rule pfsense)

Scheduled Pinned Locked Moved NAT
20 Posts 2 Posters 1.6k 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.
  • R Offline
    Rohit 0 @Rohit 0
    last edited by Jul 10, 2023, 9:28 AM

    @Rohit-0 On mikrotik side i hve done all the routing and it work like a charm when tunnel with Netskope FW so i think i need some changes in pfsense.

    K 2 Replies Last reply Jul 10, 2023, 10:00 AM Reply Quote 0
    • K Offline
      keyser Rebel Alliance @Rohit 0
      last edited by Jul 10, 2023, 10:00 AM

      @Rohit-0 Hmm, hard to tell what causes your issue then because I agree that your firewall log should not be hit with blocks like that since you created the right allow rule on the GRE interface - unless you created the GRE interface with the wrong settings.

      Please post your current:

      • GRE interface definition
      • Current WAN Interface addresses in both ends.
      • Current pfSense outbound NAT rules
      • Current pfSense GRE interface Rules

      A few other observations.

      1: There is somthing wrong with your Microtik config as traffic sourced from 103.72.218.238 also gets forwarded over your GRE tunnel
      2: There is no need to tick “Static Route filtering” in advanced settings. This GRE Tunnel does not need that.

      Love the no fuss of using the official appliances :-)

      R 1 Reply Last reply Jul 10, 2023, 10:14 AM Reply Quote 0
      • K Offline
        keyser Rebel Alliance @Rohit 0
        last edited by Jul 10, 2023, 10:07 AM

        @Rohit-0 Anyways - since the firewal log blocks TCP:FA from 192.168.2.20 towards the internet, there seems to be something causing assymetric routing as that packet is not matched to an existing state. That can be many things, but it is quite often related to faulty NAT config in either end of the setup.

        Love the no fuss of using the official appliances :-)

        1 Reply Last reply Reply Quote 0
        • R Offline
          Rohit 0 @keyser
          last edited by Jul 10, 2023, 10:14 AM

          @keyser i will look into why public address is being forwarded ,
          here are my pfsense setting snapshot
          66016585-31e9-4f76-8a25-9a31d1e0ad8a-image.png
          133e3f13-1f95-42d8-b03f-6e7acd69cdc9-image.png
          84c3f7f7-2c0a-4d46-b3fd-0665ad9defd4-image.png
          13ef7c47-867e-4b53-b051-3ec8960689fa-image.png
          db2adb4d-998a-40bc-b667-b8e8d9ab7c7d-image.png

          a27032e5-07b8-44c8-a992-dae566dca8d6-image.png

          K 1 Reply Last reply Jul 10, 2023, 10:27 AM Reply Quote 0
          • K Offline
            keyser Rebel Alliance @Rohit 0
            last edited by keyser Jul 10, 2023, 10:28 AM Jul 10, 2023, 10:27 AM

            @Rohit-0 Right now you are missing outbound NAT rules intirely. You need to have pfSense NAT both you local pfSense Networks and the Remote Mikrotik client network. I think clicking “Automatic outbound NAT rule generation” should do it as your routing setup should make pfSense include the remote mikrotik network in the NAT for WAN outbound traffic.

            But if it does create automatic rules for NAT’ing on the GRE interface as well, you instead need to create a manual NAT rule on Interface WAN stating that all 192.168.1.0/24 and 192.168.2.0/24 (according to your drawing) should be NAT’ed using the IWAN interfaces address.

            Please post the revised NAT setup

            Love the no fuss of using the official appliances :-)

            R 1 Reply Last reply Jul 10, 2023, 10:31 AM Reply Quote 0
            • R Offline
              Rohit 0 @keyser
              last edited by Jul 10, 2023, 10:31 AM

              @keyser here is my revised NAT rule and let me check
              f1baef3d-30aa-4f4f-bfb1-46d483de7f58-image.png

              R 1 Reply Last reply Jul 10, 2023, 10:34 AM Reply Quote 0
              • R Offline
                Rohit 0 @Rohit 0
                last edited by Jul 10, 2023, 10:34 AM

                @Rohit-0 Still i'm getting blocked for GRE traffic

                R 1 Reply Last reply Jul 10, 2023, 10:37 AM Reply Quote 0
                • R Offline
                  Rohit 0 @Rohit 0
                  last edited by Jul 10, 2023, 10:37 AM

                  @Rohit-0 Thanks it was my mistake from mikrotik side i should not allow fast path in GRE setting , Thanks again for everything

                  K 1 Reply Last reply Jul 10, 2023, 10:42 AM Reply Quote 0
                  • K Offline
                    keyser Rebel Alliance @Rohit 0
                    last edited by Jul 10, 2023, 10:42 AM

                    @Rohit-0 My pleasure - but the Outbound NAT rules are still wrong - it will work, but not like you intend (fully routed).
                    You need to remove the four rules assigned with the GRE interface. They are not needed and will cause all traffic from the mikrotik network to appear as being sent from 10.160.254.50

                    Love the no fuss of using the official appliances :-)

                    R 1 Reply Last reply Jul 10, 2023, 12:15 PM Reply Quote 0
                    • R Offline
                      Rohit 0 @keyser
                      last edited by Jul 10, 2023, 12:15 PM

                      @keyser thanks again

                      1 Reply Last reply Reply Quote 1
                      20 out of 20
                      • First post
                        20/20
                        Last post
                      Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
                        This community forum collects and processes your personal information.
                        consent.not_received