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

    Static Route VS Outbound

    Scheduled Pinned Locked Moved Routing and Multi WAN
    21 Posts 3 Posters 1.6k 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.
    • B
      Bambos @johnpoz
      last edited by

      @johnpoz yes, you are right and we agree (if the user is connected to the LAN 16.)

      In this case, we are talking about external user over internet.

      The site to site is between the 2 LAN's 16 and 27. Both pfsense have routing to each other with no problem.

      johnpozJ 1 Reply Last reply Reply Quote 0
      • johnpozJ
        johnpoz LAYER 8 Global Moderator @Bambos
        last edited by

        @bambos said in Static Route VS Outbound:

        In this case, we are talking about external user over internet.

        If the user is external, then the vpn does not come into play. If user X out on the internet vpns into site A, he would be able to route traffic over the vpn to site B, again no port forward needed.

        You would just need to setup routing via the vpn to get to the tunnel network of say the road warrior connection to site A.

        An intelligent man is sometimes forced to be drunk to spend time with his fools
        If you get confused: Listen to the Music Play
        Please don't Chat/PM me for help, unless mod related
        SG-4860 24.11 | Lab VMs 2.8, 24.11

        B 1 Reply Last reply Reply Quote 1
        • B
          Bambos @johnpoz
          last edited by

          @johnpoz Thank you Sir. Well noted. To my understanding you reffering to a case when the outside user accessing through remote access VPN as client on the server. Right ?

          johnpozJ 1 Reply Last reply Reply Quote 0
          • johnpozJ
            johnpoz LAYER 8 Global Moderator @Bambos
            last edited by

            Doesn't matter where the external user vpns into be it site A or site B. You can setup routing over the s2s vpn so that any remote client could access either site A or site B networks no matter which site they vpn into.

            An intelligent man is sometimes forced to be drunk to spend time with his fools
            If you get confused: Listen to the Music Play
            Please don't Chat/PM me for help, unless mod related
            SG-4860 24.11 | Lab VMs 2.8, 24.11

            B 1 Reply Last reply Reply Quote 0
            • B
              Bambos @viragomann
              last edited by

              @viragomann Great is working as you described !! thanks a lot.

              Now i'm just questioning my self, when the autocreated openVPN tab has to get a rule and why ?

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

                @bambos

                The OpenVPN tab is an interface group including all OpenVPN instances you're are running on the box, clients and servers as well. It is created by pfSense, when you set up the first OpenVPN to handle the traffic simply.

                But what you need here is the reply-to flag of pfSense. This needs to have a pass rule on a unique interface, so that it sees a distinct gateway, where responses have to be replied back. Therefor the reply-to doesn't work on interface group or floating rules.

                B 1 Reply Last reply Reply Quote 0
                • B
                  Bambos @viragomann
                  last edited by

                  @viragomann Good, thanks a lot for your support.

                  What about remote access open vpn instance on the server ? Does this need a rule on the OpenVPN tab ? or again needs an interface ?

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

                    @bambos
                    Best practice is to assign an interface to each OpenVPN instance in this case. So each rule hase clear mapping.
                    However, basically you may also assign rules to the OpenVPN tab which are applied to all OpenVPN instances then, but in any case you have to care that there is no rule matching the forwarded traffic you need to reply to the remote site.
                    So you may add a pass rule excluding port 100 in your example.

                    B 1 Reply Last reply Reply Quote 1
                    • B
                      Bambos @viragomann
                      last edited by

                      @viragomann thank you very much Sir. You gave me hints to play more with some things now. I have some things to redo for test. No sleep tonight :)

                      1 Reply Last reply Reply Quote 0
                      • B
                        Bambos @johnpoz
                        last edited by

                        @johnpoz Thanks for explaining everything. I tried what you suggested and is succesful. The only thing was that the remote user, couldn't been able to connect through a VPN Client, that's why i make it short term access using port 100. ok, now it's clear.

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