Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revisionBoth sides next revision
docs:guide-user:firewall:fw3_configurations:fw3_parent_controls [2020/03/20 15:43] – typo torxgewindedocs:guide-user:firewall:fw3_configurations:fw3_parent_controls [2023/08/30 08:26] – [Blocking services with banIP] vgaetera
Line 2: Line 2:
 {{section>meta:infobox:howto_links#basic_skills&noheader&nofooter&noeditbutton}} {{section>meta:infobox:howto_links#basic_skills&noheader&nofooter&noeditbutton}}
  
-Parental control of internet access can be done in several ways: +===== Introduction ===== 
-  * Timely restriction of internet access per IP/MAC+  * This article describes common methods to perform parental control of internet access. 
-  * Restrict / deny / block access to certain web pages: +  * Be sure to apply restrictions to all source zones if you are using a firewall-based method.
-    * Blocking Servers by blocking Static IPs +
-    * Blocking Name resolution (DNS) by Adblockers +
-    * Blocking IPs based on their Domainnames (FQDN, Hostnames) +
-    * Blocking sites by using Proxy Servers+
  
-====== Restrict / deny / block access to certain web pages ====== +===== Restrict / deny / block access to certain web pages ===== 
-===== Blocking Servers by blacklisting their IP ===== +==== Blocking servers by blacklisting their IP ==== 
-If a server is running at a single IP or just uses a small set of IPs, blocking these IPs in fw3 is a very efficient way to block this site. It is the quickest and most efficient way of blocking websites and is well supported even in the Webinterface. Assuming OpenWRT operates with a LAN and WAN zone a filter in the FORWARDING chain that rejects packets is enough. The setup is detailed at [[docs:guide-user:firewall:fw3_configurations:fw3_config_examples#block_lan-side_access_to_a_specific_site|fw3 rule to block a site]]+Follow: 
-ASN lists could be used to block large numbers of IPs belonging to certain companies. A script would be used to fetch all current IPs assigned to a certain company and this information is used to update the firewall accordingly.+[[docs:guide-user:firewall:fw3_configurations:fw3_config_examples#block_lan-side_access_to_a_specific_site|Firewall rule to block a site]] 
 + 
 +If a server is running at a single IP or just uses a small set of IPs, blocking these IPs in fw3 is a very efficient way to block this site. 
 +It is the quickest and most efficient way of blocking websites and is well supported even in the web interface. 
 +Assuming OpenWrt operates with a LAN and WAN zone a filter in the FORWARD chain that rejects packets is enough. 
 +ASN lists could be used to block large numbers of IPs belonging to certain companies. 
 +A script would be used to fetch all current IPs assigned to a certain company and this information is used to update the firewall accordingly.
  
 Drawbacks: Drawbacks:
-  * To circumvent these IP based restrictions an internet proxy or TOR could be used.+  * To circumvent these IP based restrictions an internet proxy or Tor could be used.
   * Dynamic hosts change their IP on a regular basis, invalidating the blacklist   * Dynamic hosts change their IP on a regular basis, invalidating the blacklist
  
-===== Blocking Name resolution (DNS) by Adblockers ===== +==== Blocking name resolution (DNS) by Adblockers ==== 
-This method voids DNS lookups so, for example, ''www.youtube.com'' does not generate the desired IP address. The [[packages:pkgdata:adblock|adblock package]] can be used to blacklist certain domainnames and prevent the DNS server handing out the right IP. Alternatively DNSMASQ can be configured to return a NXDOMAIN answer in case a blacklisted domainname is queried. Another option is to use PiHole in the LAN and divert DNS requests to PiHole.+Follow: 
 +[[docs:guide-user:services:ad-blocking|Ad blocking]], 
 +[[docs:guide-user:base-system:dhcp_configuration#dns_filtering|DNS filtering]] 
 + 
 +This method voids DNS lookups so, for example, ''www.youtube.com'' does not generate the desired IP address. 
 +Adblock can be used to blacklist certain domain names and prevent the DNS server handing out the right IP. 
 +Alternatively Dnsmasq can be configured to return a NXDOMAIN answer in case a blacklisted domain name is queried. 
 +Another option is to use Pi-hole in the LAN and divert DNS requests to Pi-hole.
  
 Drawbacks: Drawbacks:
Line 27: Line 36:
   * If several DNS are in the LAN just changing the local settings to the unfiltered DNS renders this control useless.   * If several DNS are in the LAN just changing the local settings to the unfiltered DNS renders this control useless.
  
-===== Blocking IPs based on their Domainnames (FQDN, Hostnames) ====== +==== Blocking IPs based on their domain names (FQDN, host names) ==== 
-Since OpenWRT in a typical setup with a LAN and WAN zone does the name resolution and the firewall at the same time, all information is there to match domainnames, their current IPs as they are handed out to the LAN-hosts and act accordingly in the firewall. This is essential if a single domain might resolve to several IPs. For instance websites that operate with a CDN can be blocked by their name instead of finding out each and every IP the CDN might be using.+Follow: 
 +[[docs:guide-user:firewall:fw3_configurations:dns_ipset|Filtering traffic with IP sets by DNS]]
  
-Example: +Since OpenWrt in a typical setup with a LAN and WAN zone does the name resolution and the firewall at the same time, all information is there to match domain names, their current IPs as they are handed out to the LAN-hosts and act accordingly in the firewall. 
-Assumed you want to block everything that ends with the domainname 'example.com' or 'example.net' perform the following steps: +This is essential if a single domain might resolve to several IPs
-  * Install the package kmod-ipt-ipset and replace dnsmasq with dnsmasq-full: ''opkg update && opkg install kmod-ipt-ipset && opkg install dnsmasq-full'' +For instance websites that operate with a CDN can be blocked by their name instead of finding out each and every IP the CDN might be using.
-  * In ''/etc/config/dhcp'' add in the region ''config dnsmasq'' the option ''list ipset '/example.com/example.net/MyExample'''. It should look as follows (without the triple-dots): <code>config dnsmasq +
-        option domainneeded '1' +
-        option localise_queries '1' +
-        option expandhosts '1' +
-        option readethers '1' +
-        option leasefile '/tmp/dhcp.leases' +
-        option resolvfile '/tmp/resolv.conf.auto' +
-        option localservice '1' +
-        option rebind_protection '0' +
-        ... +
-        list ipset '/example.com/example.net/MyExample' +
-        ... +
-        option authoritative '1' +
-        option cachesize '1000' +
-        option domain 'lan' +
-        option logqueries '1'</code> +
-  * In ''/etc'config/firewall'' add <code>config ipset                                     +
-        option enabled '1'            +
-        option name 'MyExample'             +
-        option match 'ip'                     +
-        option storage 'hash'</code> and now also a filter rule <code>config rule                           +
-        option src 'LAN'                +
-        option name 'Block Example Domains'                   +
-        option dest 'wan'              +
-        option target 'REJECT'         +
-        option ipset 'MyExample dest'            +
-        list proto 'tcp'                      +
-        list proto 'udp'</code> +
-  * restart the firewall and DNSmasq ''/etc/init.d/firewall restart && /etc/init.d/dnsmasq restart'' +
-  * To observe the filtering taking place enable logging to the syslog for the DHCP server and watch the log with ''logread -f''. Another handy command is ''ipset list'' to inspect the current IPs that where added by the DNS server to the list of domains.+
  
 Drawbacks: Drawbacks:
-  * If servers are multi-homed its not possible to distinguish in the firewall. +  * This will block all sites sharing the same IP with the targetedso use carefully for domains which rely on [[wp>Content_delivery_network|CDNs]]
-  * Not supported in the Webinterfacethere is a project at [[https://github.com/lvqier/luci-app-dnsmasq-ipset|GitHub]] that might be available in the future.+  * Completely blocking sites that use localized domains is problematic.
  
-===== Blocking sites by using Proxy Servers ====== +==== Blocking services with banIP ==== 
-A proxy server like SQUID can be used to block access to websites. It can check HTTP(S) specific details. The huge benefit of this option is to have the finest level of control. It can even distinguish in cases where a single server with a single IP runs for example a blacklisted and whitelisted domain at once.+See also: 
 +[[packages:pkgdata:banip]], 
 +[[packages:pkgdata:luci-app-banip]]
  
-Drawbacks: +banIP can block services using IP/CIDR listse.gyou can block WhatsApp with [[https://github.com/HybridNetworks/whatsapp-cidr|HybridNetworks/whatsapp-cidr]].
-  * Comparatively resource hungry and somewhat difficult to run on typical OpenWRT hardware. If this setup appeals to you consider a beefier Hardware and Software like IPFire, PFSense, Untangle, OPNSense, ... +
-  * Complex setup +
-  * If not everything else except the proxy is blocked, it can be circumvented.+
  
-====== Timely restriction of internet access ====== +<code bash> 
-**Example:** Block internet access for a certain MAC address IP address on weekdays during 21:30-07:00+opkg update 
 +opkg install banip luci-app-banip 
 +uci set banip.global.ban_enabled="1" 
 +uci del_list banip.global.ban_feed="whatsapp" 
 +uci add_list banip.global.ban_feed="whatsapp" 
 +uci commit banip 
 +/usr/share/libubox/jshn.sh 
 +json_init 
 +json_load_file /etc/banip/banip.custom.feeds 2> /dev/null 
 +json_add_object "whatsapp" 
 +json_add_string "descr" "WhatsApp CIDR" 
 +json_add_string "url_4" "https://raw.githubusercontent.com/
 +HybridNetworks/whatsapp-cidr/main/WhatsApp/whatsapp_cidr_ipv4.txt" 
 +json_add_string "rule_4" "/^[^#]/{print \$1\",\"}" 
 +json_close_object 
 +json_dump > /etc/banip/banip.custom.feeds 
 +/etc/init.d/banip restart 
 +</code>
  
-===== Web interface ===== +==== Blocking sites by using proxy servers ===== 
-First, make sure that your router has the right time **and** the right timezone.+Follow: 
 +[[docs:guide-user:services:proxy:overview|Proxy server overview]]
  
-<WRAP group> +A proxy server like [[docs:guide-user:services:proxy:proxy.squid|Squid]] or [[docs:guide-user:services:proxy:tinyproxy|Tinyproxy]] can be used to block access to websites. 
-<WRAP half column> +It can check HTTP(S) specific details. 
-  //Network -> Firewall -> Traffic Rules -> New forward rule// +The huge benefit of this option is to have the finest level of control. 
-  - Add name for your rule, e.g. "Kids weeksdays", "Kids weekend" +It can even distinguish in cases where a single server with a single IP runs for example a blacklisted and whitelisted domain at once.
-  - Source zonelan +
-  Destination zonewan +
-  - Click //Add and edit// +
-  - Select //Source MAC address// or //Source address// +
-  - Set //Action// to be //Reject// +
-  - Select weekdays +
-  - Select start/stop time +
-  - Save&apply +
-</WRAP>+
  
-<WRAP half column> +Squid offers many features like SNI HTTPS based filtering, SSL-bump and spliceHowever, for typical resource constrained devices, Tinyproxy offers the most important options (filtering websites) as well. For parental control, due to ease of setup and low RAM/Flash requirements, consider Tinyproxy first.
-{{ :media:docs:howto:firewall_-_parental_control_settings_via_luci.png?direct&0x400 |Timely restriction of internet access via LuCI}} +
-</WRAP> +
-</WRAP>+
  
-More detailed explanations in French+Drawbacks
-[[https://www.rezine.org/documentation/routeur-openwrt/#index1h1|step-by-step explanations with screenshots]]+  * If not everything else except the proxy is blocked, it can be circumventedThe firewall must block the client-device from accessing the internet directly. 
 +  * The clients need to configure the proxy in their browser.
  
-NB: If your focus is on authorised timeslots, you can create a rule that always rejects, and add a few rules that accept for the authorised timeslots. Order the rules so as to bring Accept rules before the Reject rule.+===== Time restriction of internet access ===== 
 +Block internet access for MAC or IP addresses (or everyone) on week days during specific time interval.
  
-NBThe stop time will stop kids from creating a **new** connection e.g. to browse one more page on WikipediaIt will not kick out your kids if they have an existing connection e.gin an Android game app. To enforce the stop timeyou need something extra. Consider the script belowstarting with cat+<WRAP important> 
 +  * Verify that your router has the correct time and timezone. 
 +  * Apply the following workarounds to ensure reliable operation: 
 +    * [[docs:guide-user:firewall:fw3_configurations:dns_ipset#established_connections|Reorder firewall rules]] to enforce time restrictions for already established connections. 
 +    [[docs:guide-user:base-system:system_configuration#daylight_saving_time|Reload kernel timezone]] to handle DST-related changes. 
 +</WRAP> 
 + 
 +==== Web interface instructions ==== 
 +Adjust the parameters according to your configuration. 
 + 
 +  - Navigate to **LuCI -> Network -> Firewall -> Traffic Rules**. 
 +  - Click **Add** and specify: 
 +    * Name: ''Filter-Parental-Controls'' 
 +    * Protocol: Any 
 +    * Source zone: ''lan'' 
 +    * Destination zone: ''wan'' 
 +    * Action: reject 
 +  - (Optional) If you want to add a MAC or IP limitation, on the **Advanced Settings** tab specify: 
 +    * Source MAC address: ''00:11:22:33:44:55'' 
 +    * Source IP address: ''192.168.1.2'' 
 +  - On the **Time Restrictions** tab specify: 
 +    * Week Days: MondayTuesdayWednesday, Thursday, Friday 
 +    * Start Time: ''21:30:00'' 
 +    * Stop Time: ''07:00:00'' 
 +  - Click **Save**, then **Save & Apply**.
  
-NB: If you have e.g. a Guest network, this rule won't restrict your kid if/when they connect to the Guest network.+You can add another rule to apply time restrictions on weekend.
  
-==== Command-line interface ====+==== Command-line instructions ====
 Add a new firewall rule. Add a new firewall rule.
 Edit the following example code block to suit your needs and then copy-paste it into the terminal. Edit the following example code block to suit your needs and then copy-paste it into the terminal.
Line 116: Line 127:
  
 <code bash> <code bash>
 +# Configure firewall
 uci add firewall rule uci add firewall rule
-uci set firewall.@rule[-1].name="Kids weekdays"+uci set firewall.@rule[-1].name="Filter-Parental-Controls"
 uci set firewall.@rule[-1].src="lan" uci set firewall.@rule[-1].src="lan"
-uci set firewall.@rule[-1].src_mac="78:BB:AA:3A:88:14"+uci set firewall.@rule[-1].src_mac="00:11:22:33:44:55"
 uci set firewall.@rule[-1].dest="wan" uci set firewall.@rule[-1].dest="wan"
 uci set firewall.@rule[-1].start_time="21:30:00" uci set firewall.@rule[-1].start_time="21:30:00"
 uci set firewall.@rule[-1].stop_time="07:00:00" uci set firewall.@rule[-1].stop_time="07:00:00"
 uci set firewall.@rule[-1].weekdays="Mon Tue Wed Thu Fri" uci set firewall.@rule[-1].weekdays="Mon Tue Wed Thu Fri"
-uci set firewall.@rule[-1].utc_time="0" 
 uci set firewall.@rule[-1].target="REJECT" uci set firewall.@rule[-1].target="REJECT"
 uci commit firewall uci commit firewall
Line 130: Line 141:
 </code> </code>
  
-Once the time is reached, the default rule order prevents closing already established connections+===== Restrict access to Wi-Fi by MAC address ===== 
-The rules should be reordered to resolve the issue.+Restrict access to your Wi-Fi by MAC address. 
 +The primary motivation for this capability is a family member gives out the SSID and passphrase to a friend while in your home
 +Later you no longer want to allow the person to use your Wi-Fi.
  
 +There are several solutions to this problem with decreasing labor and effectiveness.
 +  - The most comprehensive is to create a [[docs:guide-user:network:wifi:guestwifi:start|guest Wi-Fi]].
 +  - Change the passphrase for the interfaces.
 +  - Only allow/deny LAN access for devices with matching MAC addresses.
 +
 +This section focuses on the last option using the wireless interface MAC filter option.
 +This is a simple solution that can be invalidated by a smart hacker changing the MAC address of their device.
 +
 +==== Web interface instructions ====
 +  - Navigate to **LuCI -> Network -> Wireless**.
 +  - Click **Edit** on a selected interface.
 +  - On the **MAC Address Filter** tab specify:
 +    * MAC Address Filter:
 +      * Allow listed only
 +      * Allow all except listed
 +    * MAC List:
 +      * ''11:22:33:44:55:66''
 +      * ''aa:bb:cc:dd:ee:ff''
 +  - Click **Save**, then **Save & Apply**.
 +
 +==== Command-line instructions ====
 <code bash> <code bash>
-cat << "EOF" > /etc/firewall.estab +# Use allow-type or deny-type filter 
-for IPT in iptables ip6tables +uci set wireless.@wifi-iface[0].macfilter="allow
-do +uci set wireless.@wifi-iface[0].macfilter="deny"
-${IPT}-save -c -t filter \ +
-| sed -"/FORWARD.*ESTABLISHED/d; +
-/FORWARD.*reject/i $(${IPT}-save -c -t filter \ +
-| sed -n -e "/FORWARD.*ESTABLISHED/p")+
-| ${IPT}-restore -c -T filter +
-done +
-EOF+
  
-uci -q delete firewall.estab +# Append the MAC address to the list 
-uci set firewall.estab="include+uci add_list wireless.@wifi-iface[0].maclist="11:22:33:44:55:66
-uci set firewall.estab.path="/etc/firewall.estab+uci add_list wireless.@wifi-iface[0].maclist="aa:bb:cc:dd:ee:ff" 
-uci set firewall.estab.reload="1" + 
-uci commit firewall +# Check settings 
-/etc/init.d/firewall restart +uci show wireless.@wifi-iface[0] 
-</code>+ 
 +# Save and apply 
 +uci commit wireless 
 +wifi reload 
 +</code>  
 + 
 +You need to apply this for all wireless interfaces accessible by the user. 
 +Typically the 5 Ghz band is ''@wifi-iface[0]'' and the 2.4 Ghz band is ''@wifi-iface[1]''.
  
  • Last modified: 2023/10/14 05:53
  • by vgaetera