{"id":19984,"date":"2022-05-05T14:15:56","date_gmt":"2022-05-05T12:15:56","guid":{"rendered":"http:\/\/www.firewallhardware.it\/pfsense-e-opnvpn-accessi-a-tempo-per-openvpn-e-limitazioni-sulla-lan\/"},"modified":"2022-05-05T15:17:52","modified_gmt":"2022-05-05T13:17:52","slug":"pfsense-schedule","status":"publish","type":"post","link":"https:\/\/blog.miniserver.it\/en\/pfsense\/pfsense-schedule\/","title":{"rendered":"pfSense Schedule for OpenVPN Access"},"content":{"rendered":"

In this guide we will see how to limit, and thus make more limited the access of users who connect from the outside in VPN<\/strong> via our pfSense<\/strong> <\/a>to the LAN.<\/p>\n

By means of a time schedule, it will be possible to limit the accesses of the clients that connect with OpenVPN<\/strong> and create restrictions on the accesses of the individual servers and devices.<\/p>\n

Used Hardware:<\/h3>\n

This guide can be applied to all the hardware certified by us of the firewall line<\/a>.<\/p>\n

Software environment:<\/h3>\n

pfSense\u00ae 2.4.x<\/strong><\/a><\/p>\n

Access Schedule for OpenVPN users:<\/h3>\n

To allow access of our users only in a time interval it is necessary to create a schedule that will be useful to us on several occasions.<\/p>\n

    \n
  1. \n
      \n
    1. We proceed by going to Firewall \/ Schedules \/ and press the Add button.<\/li>\n
    2. In “Schedule Name” it is necessary to give a name to our schedule.<\/li>\n
    3. At this point we will select the month to apply it and the days by clicking on the single day of the calendar,<\/li>\n
    4. select the time range and click on “Add Time”.<\/li>\n
    5. Repeat the procedure to add another time \/ date range to be assigned to this schedule.<\/li>\n
    6. All created ranges will be displayed under “Configured Ranges.<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n

      \"OpenVPN<\/p>\n

      Here’s what our completed schedule will look like.<\/p>\n

      \"OpenVPN<\/p>\n

      At this point, in order to implement the scheduling created in the Firewall Rules, it is necessary to assign a very specific static IP address of the VPN tunnel to the user \/ s we want to limit.<\/p>\n

      This is necessary because the firewall manages the rules via IP addresses.<\/p>\n

      To assign a static IP address to the user, we will proceed as follows:<\/p>\n

        \n
      • go to VPN\/OpenVPN\/Client Specific Overrides and press the “Add” button<\/li>\n<\/ul>\n

        In the configuration screen that will appear, it will be sufficient to configure only 2 items:<\/p>\n

          \n
        • “Common Name”: the name of the VPN user<\/li>\n<\/ul>\n

          \"OpenVPN<\/p>\n

            \n
          • “Advanced”: we will have to insert the following string ifconfig-push [IP_TUNNEL] [NETMASK]<\/li>\n<\/ul>\n

            Where IP_TUNNEL will be the IP address of the tunnel that we would like to be assigned to the user.<\/p>\n

            \"OpenVPN<\/p>\n

            We repeat the procedure for each user we are interested in managing.<\/p>\n

            Access management and restriction for OpenVPN users<\/strong>
            \nWe can now implement our schedule created previously in the Firewall Rules to regulate user access and limit or allow access to individual servers.<\/p>\n

            It will be explained how to allow access to a server at a certain time, only to a specific user who connects via VPN<\/strong>
            \nLet’s start by going under Firewall \/ Rules and positioning ourselves under the “OpenVPN” interface, press the “Add” button to create a new rule to be placed at the top.<\/p>\n

            Select “Any” as protocol and in “Source” enter the IP address belonging to the VPN Tunnel network defined previously and assigned to the user concerned.<\/p>\n

            In “destination” we can enter in “Single host or alias” the IP address of the server to which we want to restrict the user’s connection.<\/p>\n

            \"OpenVPN<\/p>\n

            Finally, let’s position ourselves on “Advanced Options” and in the “Schedule” item select the Schedule created previously.<\/p>\n

            \"OpenVPN<\/p>\n

            In this way we have allowed the user “john” who connects in VPN with the IP address of the Tunnel 10.20.30.20 to access only the server 192.168.2.55 during the time range established in the scheduling.<\/p>\n

            We can repeat the procedure for each user to whom we want to grant access to the server at a certain time range.<\/p>\n

            At this point, to prevent the user from accessing other devices on the network, we create a rule that blocks access to everything. This rule must be placed UNDER the previously created access rules and associated with it.<\/p>\n

            \"OpenVPN<\/p>\n

            Here is how the created rules will appear, to note that the symbol in correspondence with the “schedules” is green if at that moment we meet the rules described in our schedule.<\/p>\n

            \"OpenVPN<\/p>\n

            It will be yellow instead when we are out of the scheduling range and therefore you will not have access.<\/p>\n

            \"OpenVPN<\/p>\n","protected":false},"excerpt":{"rendered":"

            In this guide we will see how to limit, and thus make more limited the access of users who connect from the outside in VPN via our pfSense to the LAN.<\/p>\n","protected":false},"author":11,"featured_media":25127,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"content-type":"","footnotes":""},"categories":[124],"tags":[270,138],"class_list":["post-19984","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-pfsense","tag-openvpn-e-pfsense-en","tag-pfsense-en"],"_links":{"self":[{"href":"https:\/\/blog.miniserver.it\/en\/wp-json\/wp\/v2\/posts\/19984","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.miniserver.it\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.miniserver.it\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.miniserver.it\/en\/wp-json\/wp\/v2\/users\/11"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.miniserver.it\/en\/wp-json\/wp\/v2\/comments?post=19984"}],"version-history":[{"count":9,"href":"https:\/\/blog.miniserver.it\/en\/wp-json\/wp\/v2\/posts\/19984\/revisions"}],"predecessor-version":[{"id":25126,"href":"https:\/\/blog.miniserver.it\/en\/wp-json\/wp\/v2\/posts\/19984\/revisions\/25126"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.miniserver.it\/en\/wp-json\/wp\/v2\/media\/25127"}],"wp:attachment":[{"href":"https:\/\/blog.miniserver.it\/en\/wp-json\/wp\/v2\/media?parent=19984"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.miniserver.it\/en\/wp-json\/wp\/v2\/categories?post=19984"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.miniserver.it\/en\/wp-json\/wp\/v2\/tags?post=19984"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}