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

    Site to Site overriding my WAN? (SOLVED)

    Scheduled Pinned Locked Moved OpenVPN
    10 Posts 3 Posters 940 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.
    • K
      killmasta93
      last edited by killmasta93

      Hi,
      I was wondering if someone could shed some light, currently have a site to site OpenVPN, Im not sure if its normal on the Site 2 which is the client is having the WAN ip of site 1 instead of site 2. The issue is that on theres a goverment website that only lets get in if we have the WAN IP of the Site 2

      ex:

      Site 1 Server---WAN----181.143.51.XXX
      Site2 Client----WAN----181.143.88.xx

      The idea for users on Site 2 to navigate with the WAN 181.143.88.xx rather then 181.143.51.xxx

      Thank you

      Tutorials:

      https://www.mediafire.com/folder/v329emaz1e9ih/Tutorials

      1 Reply Last reply Reply Quote 0
      • V
        viragomann
        last edited by

        Does the server push the default route?
        "Redirect gateway" checked in the server settings?

        1 Reply Last reply Reply Quote 0
        • K
          killmasta93
          last edited by

          Thanks for the reply, i do not have redirect gateway i dont think thats an option see picture

          https://ibb.co/b78qv8

          Thank you

          Tutorials:

          https://www.mediafire.com/folder/v329emaz1e9ih/Tutorials

          1 Reply Last reply Reply Quote 0
          • V
            viragomann
            last edited by

            Seems to be a very old version. Why not updating?

            What does the routing table on the client look like?

            1 Reply Last reply Reply Quote 0
            • K
              killmasta93
              last edited by

              Thanks for the reply, the client i updated to 2.3.5 but the server version is still 2.2.4 but whats even odd was that the client was 2.3.2 and was working well ofcourse i did not notice the IP until the users told me is there another way i can troubleshoot this?

              Tutorials:

              https://www.mediafire.com/folder/v329emaz1e9ih/Tutorials

              1 Reply Last reply Reply Quote 0
              • K
                killmasta93
                last edited by

                bump? anyone?

                Tutorials:

                https://www.mediafire.com/folder/v329emaz1e9ih/Tutorials

                1 Reply Last reply Reply Quote 0
                • DerelictD
                  Derelict LAYER 8 Netgate
                  last edited by

                  You are going to be hard-pressed to find someone willing to give their time when you are running such an ancient version.

                  Chattanooga, Tennessee, USA
                  A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                  DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                  Do Not Chat For Help! NO_WAN_EGRESS(TM)

                  1 Reply Last reply Reply Quote 0
                  • K
                    killmasta93
                    last edited by

                    so your telling me on the new version 2.3.X its not suppose to do that?

                    Tutorials:

                    https://www.mediafire.com/folder/v329emaz1e9ih/Tutorials

                    1 Reply Last reply Reply Quote 0
                    • DerelictD
                      Derelict LAYER 8 Netgate
                      last edited by

                      No, I am not saying that, but you could easily be chasing something that is already fixed.

                      Chattanooga, Tennessee, USA
                      A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                      DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                      Do Not Chat For Help! NO_WAN_EGRESS(TM)

                      1 Reply Last reply Reply Quote 1
                      • K
                        killmasta93
                        last edited by

                        I guess your right, tried on my test enviroment 2 pfSense boxes both running 2.3.5 and the Site 2 was using its own WAN rather then using Site 1 WAN

                        Tutorials:

                        https://www.mediafire.com/folder/v329emaz1e9ih/Tutorials

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