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

    Troubles connecting between two separate pfsense firewalls

    Scheduled Pinned Locked Moved General pfSense Questions
    16 Posts 4 Posters 4.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.
    • R
      rbishop
      last edited by

      Both of my Firewalls are 1.2.3.  Do I need to update them both?

      1 Reply Last reply Reply Quote 0
      • P
        podilarius
        last edited by

        @rbishop:

        Both of my Firewalls are 1.2.3.  Do I need to update them both?

        Yes.

        1 Reply Last reply Reply Quote 0
        • R
          rbishop
          last edited by

          I have now upgraded both of my Firewalls to the latest version 2.0.  I am still not able to get to the devices behind Firewall A from behind Firewall B.

          1 Reply Last reply Reply Quote 0
          • M
            mgaudette
            last edited by

            Im trying to accomplish the same thing, cant.  Here`s what I did, what worked, and what did not work. That might help you, and might help people help you (and, think of it, it might help me too!)

            • I setup a Linux server at some hosted place with a route that basically says:  192.168.1.0/24 via 55.55.55.55 (the public IP of pfSense B)
            • configured pfSense to accept all connections from that Linux server

            I can ping 192.168.1.x from that server, which is on a totally separate network! Everything works fine.

            Now, I have another pfSense (call it pfSense A). I want, from that pfSense diagnostic "ping" screen, to be able to ping 192.168.1.x. I cant. I cant setup a route, because the route needs a gateway, and that gateway wen being created, needs to be on the same subnet as my pfSense A public IP (which isn't 55.55.55.xx)

            Is this what you are trying to do too?

            1 Reply Last reply Reply Quote 0
            • R
              rbishop
              last edited by

              Yes this is what I am trying to do.

              From Firewall B I am able to get to the WAN IP of Firewall A but nothing further…

              I have now setup a server behind Firewall B.  I am able to get to it from anywhere, including from behind Firewall A....

              1 Reply Last reply Reply Quote 0
              • M
                mgaudette
                last edited by

                Then haven`t you accomplished what you want? (please tell me how you did this?)

                Or is this just through port fowarding?

                1 Reply Last reply Reply Quote 0
                • R
                  rbishop
                  last edited by

                  Firewall A has public IP's on both inside and outside interface.  I have rules setup for each of the systems on the LAN side for HTTP, SSH, etc.  Firewall B is a "typical" router in that it is setup with a Public IP on the WAN and Private IP's on the LAN.  I do have multiple Public IP's that I am just port forwarding on Firewall B, in this case to HTTP and SSH.

                  1 Reply Last reply Reply Quote 0
                  • C
                    cmb
                    last edited by

                    Rules need to be on WAN to allow traffic in from the Internet, not LAN. I suspect your rules aren't permitting the traffic, are you seeing it getting blocked in the firewall log?

                    1 Reply Last reply Reply Quote 0
                    • R
                      rbishop
                      last edited by

                      CMB sorry I do have the rules setup on the WAN interface.

                      1 Reply Last reply Reply Quote 0
                      • R
                        rbishop
                        last edited by

                        I have fixed my problem….finally.

                        I was finally able to add in a route to Firewall A into Firewall B.  This now allows items behind Firewall B to see the servers behind Firewall A.

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