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

    [noob question] pfSense as a OpenVPN client for selected devices

    Scheduled Pinned Locked Moved OpenVPN
    28 Posts 2 Posters 3.1k 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.
    • V
      viragomann @Draghmar
      last edited by

      @draghmar
      Depends on the rule creation option:
      23bc80e5-351d-43b6-bcad-983fcf02e1c7-grafik.png

      However, pfSenes cannot create a policy rule from a NAT, since there is no gateway info.

      So at best you can let it create an unassociated filter rule and edit it after to set the gateway.

      DraghmarD 1 Reply Last reply Reply Quote 0
      • DraghmarD
        Draghmar @viragomann
        last edited by

        @viragomann I think I did everything but https://dnsleaktest.com still is able to detect my IP. :( I have Port Forward set as above and in the created rule I changed gateway to VPN one. What else am I missing?

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

          @draghmar
          Maybe there is an other rule matching the DNS traffic before. Floating rule?

          Enable logging in the rule to investigate.

          DraghmarD 1 Reply Last reply Reply Quote 0
          • DraghmarD
            Draghmar @viragomann
            last edited by Draghmar

            @viragomann Hm...I checked Log packets that are handled by this rule but I don't see anything in System logs->Firewall poping up when browsing websites from device I'm testing from. And I don't have any other rule DNS related, just those two. I have fairly simple network here. No floating or anything fancy like that ;)

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

              @draghmar
              Do you consider the possibility that the client may use DoH?
              So what's about its HTTPS traffic?

              DraghmarD 1 Reply Last reply Reply Quote 0
              • DraghmarD
                Draghmar @viragomann
                last edited by

                @viragomann I'm testing from FireFox on Win 10 with DoH disabled and DNS servers set to router IP.
                What about HTTPS traffic?

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

                  @draghmar
                  When using DoH the DNS traffic goes over HTTPS protocol.

                  Never seen you rule set, so I cannot say if they are ok.
                  But for testing, direct the whole upstream traffic from the 'VPN clients' to the VPN server.
                  Verify that the policy routing rule matches.

                  DraghmarD 1 Reply Last reply Reply Quote 0
                  • DraghmarD
                    Draghmar @viragomann
                    last edited by

                    @viragomann Those are my NAT and rules:
                    pfsense-rules.png
                    pfsense-nat.png
                    Like I said - nothing complicated. ;) There are some NATs for web server and such. But that's it. The only additional thing are the rules for OpenVPN and for VPN interface. And those are ones we've discussed in this thread.

                    How can I direct like you said? I thought I just did force every device that should go through VPN to VPN server. The rule for that is visible on the list above.

                    Is there way to make some artificial connection to the DNS server that so could be sure that the flow is correct? I mean something like trying to connect to DNS IP having DNS port. I'm thinking here that I could try connect to router IP this way to check if it's redirected. I'd like to eliminate other factors this way because the only thing I know about testing this is to simply hit some URL from specified device...

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

                      @draghmar
                      You must not set a source port in the DNS rule, it has to be any.

                      DraghmarD 1 Reply Last reply Reply Quote 1
                      • DraghmarD
                        Draghmar @viragomann
                        last edited by

                        @viragomann Yup, that was it! Thanks! Now everything seems to work as it should. :D

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