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

    OpenVPN Not Connecting - Unable To Contact Daemon

    OpenVPN
    2
    41
    3.7k
    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.
    • P
      panzerscope @viragomann
      last edited by

      @viragomann said in OpenVPN Not Connecting - Unable To Contact Daemon:

      @panzerscope
      The first one might be manually added.
      The red framed are from the NAT rules.
      e0b173ea-f8ae-4ecd-bf17-1e716794f5ad-grafik.png

      With your recent rule set they will never be applied, since the are other matching rule above of them.

      You can also disable the filter rule association for these rules.

      Many thanks.

      Where would I find the "Filter Rule Association" setting ?

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

        @panzerscope
        In the NAT rule.
        If you have this selected pfSense adds a filter rule.
        If you select "pass" it lets the traffic pass without a filter rule.

        P 1 Reply Last reply Reply Quote 0
        • P
          panzerscope @viragomann
          last edited by

          @viragomann said in OpenVPN Not Connecting - Unable To Contact Daemon:

          @panzerscope
          In the NAT rule.
          If you have this selected pfSense adds a filter rule.
          If you select "pass" it lets the traffic pass without a filter rule.

          Thanks.

          I may be oversimplifying my next question, but isn't it easer to just set the Filter to "Pass" ?

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

            @panzerscope
            This depends on your needs. If you let pfSense create a rule you can verify it in your rule set.
            If you let it create an "unassociated" rule you can also edit it. For instance, turn it into a policy-routing.

            P 1 Reply Last reply Reply Quote 0
            • P
              panzerscope @viragomann
              last edited by

              @viragomann said in OpenVPN Not Connecting - Unable To Contact Daemon:

              @panzerscope
              This depends on your needs. If you let pfSense create a rule you can verify it in your rule set.
              If you let it create an "unassociated" rule you can also edit it. For instance, turn it into a policy-routing.

              Ok thanks, will leave it as it is.

              I note that since changing these rules with respect to DNS that my pfBlockerNG is seemingly no longer blocking ads. I have loaded up a few websites now and ads are now displaying. Worth noting that I have killed the VPN connection to make sure it was nothing to do with that.

              As we have used the RF1918 in recent DNS rules I am wondering if it is causing issues, I ask as when I go to pfBlockerNG configuration, that the IP and DNSBL use these private addresses for it to operate (as per below screenshots) and wondered if I have inadvertently done something.

              fb7d29d5-7e46-4621-bc43-52e2854e096d-image.png

              a6a09305-8897-4717-b3ee-849e1e1bb2ff-image.png

              Any thoughts ?

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

                @panzerscope
                This might be due to DNSBL. Is the service even running? If not, try to restart it.

                P 1 Reply Last reply Reply Quote 0
                • P
                  panzerscope @viragomann
                  last edited by

                  @viragomann said in OpenVPN Not Connecting - Unable To Contact Daemon:

                  @panzerscope
                  This might be due to DNSBL. Is the service even running? If not, try to restart it.

                  I restarted it a couple of times and now seems to be resolved.

                  I am still having a curios issue with the VPN.

                  I have deleted all my prior VPN related rules to start fresh. What is really odd is if my VPN is connected ALL my devices are being routed through the VPN, despite my LAN rules as shown below should be sending all my traffic through my WAN as there are no VPN related rules in existence and the standard rule for all LAN Subnets being sent through the default gateway (AKA my WAN)

                  0890b800-4c79-4c18-87a5-7c973e013c20-image.png

                  I noted that I could stop this behaviour by going into the VPN client and checking the following option.

                  460b78f4-580c-47e5-9a2e-ddfb42b8bf6c-image.png

                  Now, with the VPN connected, my clients now use the WAN and not the VPN. However this is no help as I do not want to use a -Rout Up script, and obviously with this setting enabled if I try to use my LAN rules to direct devices out to the VPN, it is not working.

                  **Sigh, I really do not know why this is such a pain.

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

                    @panzerscope
                    You don't have any policy routing rule for the VPN at the moment.
                    We talked about this all above and you had the rules before. So recreate them again.

                    P 1 Reply Last reply Reply Quote 0
                    • P
                      panzerscope @viragomann
                      last edited by panzerscope

                      @viragomann said in OpenVPN Not Connecting - Unable To Contact Daemon:

                      @panzerscope
                      You don't have any policy routing rule for the VPN at the moment.
                      We talked about this all above and you had the rules before. So recreate them again.

                      Already done that with a few different rule types, makes no difference .

                      4ec0a960-6544-4eb9-85cf-c7fe7fdebef0-image.png

                      Plus what I am saying is without a VPN rule, all my LAN devices should NOT be going over VPN, but they do lol.

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

                        Good news is that it is not sorted and I have the devices split over the VPN and WAN as needed.

                        Only issue I am having ensuring that the VPN us using the VPN DNS servers. I have the VPN client set to "Pull DNS", however when doing the leak test, it is showing that Cloudflare DNS is being used, which is not too surprising as I use Cloudflare (1.1.1.1) as my remote DNS server.

                        That being said, earlier in this topic, we created a rule to redirect my VPN clients to 1.1.1.1 as shown below.

                        e7bab4a5-59b0-4ebe-8435-7875a0fc3857-image.png

                        So I altered this to the DNS of the VPN provider (5.254.106.2), unfortunately after doing that I cannot get websites to resolve for clients on the VPN. I have confirmed I can ping the VPN DNS servers (When connected/disconnected from VPN), so all is well on that end.

                        While possibly completely unrelated, I went into the DNS settings and input the DNS servers for the VPN and allocated the VPN DNS entries to use the VPN Gateway as per the below screenshot.

                        bcd36cb3-e464-4e0c-a65e-ea13c4acb4a3-image.png

                        Any suggestions ?

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