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

    Static route

    Scheduled Pinned Locked Moved Russian
    18 Posts 2 Posters 1.3k 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.
    • A
      Antibiotic @viragomann
      last edited by

      @viragomann I mean, it's no any conflicts if pfSense as main will do NAT but WIFI router will do DCHP for local subnet behind this router but not pfSense?

      pfSense plus 24.11 on Topton mini PC
      CPU: Intel N100
      NIC: Intel i-226v 4 pcs
      RAM : 16 GB DDR5
      Disk: 128 GB NVMe
      Brgds, Archi

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

        @Antibiotic
        No.

        A 1 Reply Last reply Reply Quote 0
        • A
          Antibiotic @viragomann
          last edited by Antibiotic

          @viragomann Ok , thank you my friend for an assistance!)))) Have a good day! All now, looks working)))

          pfSense plus 24.11 on Topton mini PC
          CPU: Intel N100
          NIC: Intel i-226v 4 pcs
          RAM : 16 GB DDR5
          Disk: 128 GB NVMe
          Brgds, Archi

          1 Reply Last reply Reply Quote 0
          • A
            Antibiotic @viragomann
            last edited by Antibiotic

            @viragomann said in Static route:

            ISAKMP

            But if me planning to use OpenVPN on WFI router, do need to create any more rules? in case of NAT will disable on WIFI router?or its only for IPsec

            pfSense plus 24.11 on Topton mini PC
            CPU: Intel N100
            NIC: Intel i-226v 4 pcs
            RAM : 16 GB DDR5
            Disk: 128 GB NVMe
            Brgds, Archi

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

              @Antibiotic
              This rule is only for IPSec. It needs a static outbound port, so a rule is required to achieve this.

              Your current rule set on the wifi interface allows any port to any destination in the internet anyway. So there is no additional rule needed.

              Consider that it also allows access to the LAN. Maybe this is not desired and you want to block it.

              A 2 Replies Last reply Reply Quote 0
              • A
                Antibiotic @viragomann
                last edited by Antibiotic

                @viragomann said in Static route:

                Consider that it also allows access to the LAN. Maybe this is not desired and you want to block it.

                Can you suggest rule example for this? Have a dedicated NIC for WIFI router connected to pfSense ( pfSense have 4th NIC's and all home network on different NIC's of pfSense)

                pfSense plus 24.11 on Topton mini PC
                CPU: Intel N100
                NIC: Intel i-226v 4 pcs
                RAM : 16 GB DDR5
                Disk: 128 GB NVMe
                Brgds, Archi

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

                  @viragomann Also have an option on WAN page of WIFI router (Forward local domain queries to upstream DNS) Upstream DNS my pfSense. Is it better to set ON this option or does not matter? in case of NAT doing pfSense!

                  pfSense plus 24.11 on Topton mini PC
                  CPU: Intel N100
                  NIC: Intel i-226v 4 pcs
                  RAM : 16 GB DDR5
                  Disk: 128 GB NVMe
                  Brgds, Archi

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

                    @Antibiotic
                    I use an RFC 1918 alias, which I had add all private network ranges to.
                    128232e0-2184-4ce9-8430-cee9aee2e74b-grafik.png

                    Add a block or reject rule and use this alias as destination. Put this rule above of the allow-any rule.

                    Also have an option on WAN page of WIFI router (Forward local domain queries to upstream DNS) Upstream DNS my pfSense. Is it better to set ON this option or does not matter?

                    Seems to apply to local domains only. This might assume, that you have domains configured on the router.

                    If it's possible, I would set pfSense as DNS in the DHCP settings of the wifi router, so that the devices send requests directly to pfSense.

                    A 2 Replies Last reply Reply Quote 0
                    • A
                      Antibiotic @viragomann
                      last edited by

                      @viragomann Ah, thank you

                      pfSense plus 24.11 on Topton mini PC
                      CPU: Intel N100
                      NIC: Intel i-226v 4 pcs
                      RAM : 16 GB DDR5
                      Disk: 128 GB NVMe
                      Brgds, Archi

                      1 Reply Last reply Reply Quote 0
                      • A
                        Antibiotic @viragomann
                        last edited by

                        @viragomann Could you please assist with OpenVPN, don't understanding where is my mistake with settings?
                        https://forum.netgate.com/post/1161108

                        pfSense plus 24.11 on Topton mini PC
                        CPU: Intel N100
                        NIC: Intel i-226v 4 pcs
                        RAM : 16 GB DDR5
                        Disk: 128 GB NVMe
                        Brgds, Archi

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