new network button<\/strong>, you will be able to configure your line whether it is dynamic (therefore without a static IP) or static (therefore with an IP perm.<\/p>\nA small menu will open with a series of logos that, when clicked, show how to configure that device in dynamic mode. In our example, we will proceed with the “static” configuration and then click on the button Manual configuration<\/strong> at the bottom.[vc_single_image image=”18332″ img_size=”full” onclick=”link_image”]Simply by following the on-screen instructions, we have configured our network.[vc_single_image image=”18334″ img_size=”full” onclick=”link_image”][vc_single_image image=”18336″ img_size=”full” onclick=”link_image”][vc_single_image image=”18338″ img_size=”full” onclick=”link_image”][vc_single_image image=”18340″ img_size=”full” onclick=”link_image”][vc_single_image image=”18342″ img_size=”full” onclick=”link_image”][vc_single_image image=”18362″ img_size=”full” onclick=”link_image”]Now, move to the Lists<\/strong> tab. You have the possibility to immediately choose 3 profiles already preloaded and configured to block different types of sites.<\/p>\nIt starts with the Base profile, up to the more protective and aggressive Alto profile which imposes many more restrictions. It is possible to read below a brief description of the blocked contents.<\/p>\n
If you want to customize the blocks, click on Custom configuration<\/strong>.<\/p>\nNotice below, the classic White and Black lists to add or remove sites (or entire domains) by customizing the profile more.<\/p>\n
Finally, Kutter<\/strong> is able to filter the searches respecting the blocks of your profile, excluding the results also from the search results of Google<\/strong> and Bing<\/strong> search engines.<\/p>\nFor example, if I have excluded pornographic content from my profile, I will not see these results from Google and Bing engine searches.<\/p>\n
In this example, we will proceed to perform a custom configuration<\/strong>.[vc_single_image image=”18350″ img_size=”full” onclick=”link_image”]The list configuration home page looks like the following figure. A list of categories and 3 columns indicating: Allow, Block, Program the block<\/strong>[vc_single_image image=”18352″ img_size=”full” onclick=”link_image”]Clicking on the arrow to the left of the category will open the list with the content.[vc_single_image image=”18354″ img_size=”full” onclick=”link_image”]In this example we will show the Social Network <\/strong>category and show how to authorize access only during the lunch break. Clicking on the clock-shaped icon in the third column (Schedule Block), a menu will open in which to insert the block time slots.[vc_single_image image=”18356″ img_size=”full” onclick=”link_image”][vc_single_image image=”18358″ img_size=”full” onclick=”link_image”][vc_single_image image=”18360″ img_size=”full” onclick=”link_image”]We continue in this way until the complete customization of our list (in the Base<\/strong> example).<\/p>\nYou can create a different list every 5 coins<\/strong>; that is to say that an office with 25 nominal users can create up to 5 different lists (employees, administration, management, etc.) to balance the different needs of the company. By selecting the basic profile, and then clicking on the pencil icon, we will be able to choose one of the 5 useful dns pairs, precisely, in case we want to diversify the lists.<\/p>\nPfSense\u00ae configuration<\/h3>\n
[vc_separator css=”.vc_custom_1557400611541{margin-top: -20px !important;}”]Now that our network and our lists have been configured, let’s move quickly to our firewall. Here we should simply insert Kutter<\/strong> dns as shown in the figure<\/p>\ngo to the pfSense menu under System, General Setup<\/strong>.[vc_single_image image=”18366″ img_size=”full” onclick=”link_image”]In order for Kutter<\/strong> to start browsing control, our network will have to use the firewall as a dns server<\/strong>.<\/p>\nThere are three possible solutions to achieve this behavior:<\/p>\n
\n- force the network devices to use the pfSense DNS forwarder.<\/li>\n
- oblige network devices to use Kutter’s DNS.<\/li>\n
- Redirect traffic on port 53 to kutter DNS.<\/li>\n<\/ol>\n
In this guide we will illustrate the first solution:<\/p>\n
we now enable the DNS service from: Services<\/strong> -> DNS resolver<\/strong><\/p>\nEnable it and configure it so that requests can be forwarded:<\/p>\n
check the checkbox “Enable DNS resolver<\/strong>” and “Enable Forwarding Mode<\/strong>” selecting the interfaces on which the DNS service will respond (in our case only the “LAN”)[vc_single_image image=”18413″ img_size=”full” onclick=”link_image”]Next we will create two rules.<\/p>\nWe will then go to Firewall<\/strong> -> Rules<\/strong>.<\/p>\nLet’s create a rule that allows access to the dns service of the firewall, the second rule that prevents access to the DNS service for the rest of the traffic.[vc_single_image image=”18415″ img_size=”full” onclick=”link_image”]At this point the firewall will allow the use of only the pfSense DNS Server, which will resolve the names via the kutter DNS.<\/p>\n
All systems must use the firewall as DNS, manually configuring the DNS or properly configuring the DHCP Server.<\/p>\n
If you use pfsense DHCP go to Services <\/strong>-> DHCP<\/strong> Server and configure the DNS section with the IP of the firewall of the LAN (configure as below if it is assumed that the firewall has ip 192.168.1.1 on the LAN).[vc_single_image image=”18417″ img_size=”full” onclick=”link_image”]<\/p>\nConclusions<\/h3>\n
The ease of use and configuration, make Kutter<\/strong> a powerful ally to increase corporate security. The implementation methods are sufficiently “elastic”, and allow its use in practically every context and with every device.<\/p>\nKutter<\/strong> is compatible with any device that allows the forwarding of dns requests, and with devices that allow the use of the ddns service.<\/p>\n <\/p>\n","protected":false},"excerpt":{"rendered":"
Kutter, content filter and Malware protection tested with pfSense and OPNsense, Cloud Technology, simple and immediate to activate.<\/p>\n","protected":false},"author":11,"featured_media":25656,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"content-type":"","footnotes":""},"categories":[124],"tags":[261,262,263,264],"class_list":["post-18472","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-pfsense","tag-filtraggio-en","tag-kutter-en","tag-maleware-en","tag-web-proxy-en"],"_links":{"self":[{"href":"https:\/\/blog.miniserver.it\/en\/wp-json\/wp\/v2\/posts\/18472","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=18472"}],"version-history":[{"count":7,"href":"https:\/\/blog.miniserver.it\/en\/wp-json\/wp\/v2\/posts\/18472\/revisions"}],"predecessor-version":[{"id":23959,"href":"https:\/\/blog.miniserver.it\/en\/wp-json\/wp\/v2\/posts\/18472\/revisions\/23959"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.miniserver.it\/en\/wp-json\/wp\/v2\/media\/25656"}],"wp:attachment":[{"href":"https:\/\/blog.miniserver.it\/en\/wp-json\/wp\/v2\/media?parent=18472"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.miniserver.it\/en\/wp-json\/wp\/v2\/categories?post=18472"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.miniserver.it\/en\/wp-json\/wp\/v2\/tags?post=18472"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}