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_config_examples [2020/10/06 03:34] – obsolete proto=tcpudp to avoid luci-specific compatibility issues: https://forum.openwrt.org/t/is-tcpudp-a-valid-protocol-name/76048 vgaeteradocs:guide-user:firewall:fw3_configurations:fw3_config_examples [2022/10/30 21:06] – [Firewall IPv4 examples] vgaetera
Line 1: Line 1:
-====== fw3 IPv4 configuration examples ====== +====== IPv4 firewall examples ====== 
-This section contains a collection of useful [[docs:guide-user:firewall:overview|firewall3]] configuration examples based on the UCI configuration files.+This section contains a collection of useful [[docs:guide-user:firewall:overview|firewall]] configuration examples based on the UCI configuration files.
 All of these can be added on the LuCI //Network -> Firewall -> Traffic Rules// page. All of these can be added on the LuCI //Network -> Firewall -> Traffic Rules// page.
  
Line 16: Line 16:
 The ''enabled'' option in each rule is toggled between tests to verify the specific rule causes the expected behavior - on will cause packets to be accepted or not, off will cause the opposite behavior. The ''enabled'' option in each rule is toggled between tests to verify the specific rule causes the expected behavior - on will cause packets to be accepted or not, off will cause the opposite behavior.
  
-:!: Before modifying rules, make sure to back-up your current ''/etc/config/firewall''!+:!: Before modifying rules, be sure to back-up your current ''/etc/config/firewall''!
  
 ===== Opening ports on the OpenWrt router ===== ===== Opening ports on the OpenWrt router =====
Line 55: Line 55:
 It will not match any other src IP address. It will not match any other src IP address.
  
-:!: When using an IPv4 address set the family to **ipv4**, otherwise fw3 warns ''! Skipping due to different family of ip address''.+:!: When using an IPv4 address set the family to **ipv4**, otherwise firewall warns ''! Skipping due to different family of ip address''.
  
 ===== Block WAN-side networks and ports ===== ===== Block WAN-side networks and ports =====
Line 136: Line 136:
  
 ===== Block access to certain domains based on their names ===== ===== Block access to certain domains based on their names =====
-An example is give at [[docs:guide-user:firewall:fw3_configurations:fw3_parent_controls#blocking_ips_based_on_their_domainnames_fqdn_hostnames|Blocking IPs based on their hostname]] This is really useful if large CDNs need to be filtered based on their names. It is also capable to filter DDNS hosts. It has also the advantage to allow for other subdomains (like www.) by just filtering the root-domain-name (like example.com).+An example is give at [[docs:guide-user:firewall:fw3_configurations:fw3_parent_controls#blocking_ips_based_on_their_domainnames_fqdn_hostnames|Blocking IPs based on their hostname]] This is really useful if large CDNs need to be filtered based on their names. 
 +It is also capable to filter DDNS hosts. 
 +It has also the advantage to allow for other subdomains (like www.) by just filtering the root-domain-name (like example.com).
  
-===== Block access to the Internet for a specific station on certain times =====+===== Block access to the Internet for a specific LAN station between certain times =====
 The following rule can be used for parental access control. The following rule can be used for parental access control.
  
Line 157: Line 159:
  
 When this rule is enabled, it will block all TCP and UDP access from STA2 to the internet on weekdays between 21:00 and 09:00. When this rule is enabled, it will block all TCP and UDP access from STA2 to the internet on weekdays between 21:00 and 09:00.
-By default, the time will be UTC unless the ''utc_time'' option is cleared.+By default, the time will be UTC unless the ''utc_time'' option is cleared (''0'').
  
 These time/date matches use the netfilter ''xt_time'' kernel module, which is included in the release. These time/date matches use the netfilter ''xt_time'' kernel module, which is included in the release.
 Check ''/proc/modules'' to confirm it is loaded. Check ''/proc/modules'' to confirm it is loaded.
 +
 +From LuCI this rule can be added by following "Firewall->Traffic Rules" and creating a new rule
 +with the desired MAC address and an action of "block" or "reject."
  
 :!: Remove the time and day options to always block WAN-side access for the station. :!: Remove the time and day options to always block WAN-side access for the station.
 +
 +:!: This rule can be created for a single MAC address, not a range.
  
 :!: this type of rule is very useful for mobile devices like smartphones and tablets. :!: this type of rule is very useful for mobile devices like smartphones and tablets.
-A lot can change in a smartphone but the wifi MAC is always the same.+A lot can change in a smartphone but the wifi MAC is **almost** always programmed at the factory. 
 +The MAC **can** be modified by a sophisticated user by doing something similar to the Linux commands: 
 + 
 +<code bash> 
 +root> ip link set wlan0 down 
 +root> ip link set address "de:ad:be:ef:00:01" wlan0 
 +root> ip link set wlan0 up 
 +</code> 
 + 
 +An alternative mechanism to block multiple LAN MACs can be found in the LuCI "Wireless->Interface Edit->MAC Filter" section. 
 +Set the filter for "Allow all except listed" and add multiple LAN MACs. 
 +In the ''/etc/config/wireless'' file, this creates a "list maclist" entry for the interface.
  
 ===== IPSec passthrough ===== ===== IPSec passthrough =====
Line 246: Line 264:
  # let it pass  # let it pass
 </code> </code>
- 
-This will create a lot of "automatic" iptables rules (because automatic scripting is not as efficient as raw iptable commands in ''/etc/firewall.user'') but those rules will be more clear in the luci webinterface and also more readable for less expert users. 
  
 In general remember that forwardings are relying how routing rules are defined, and afterwards which zones are defined on which interfaces. In general remember that forwardings are relying how routing rules are defined, and afterwards which zones are defined on which interfaces.
Line 313: Line 329:
  option mtu_fix '1'  option mtu_fix '1'
  option conntrack '1'  option conntrack '1'
 +</code>
 +
 +===== Allow HTTP/HTTPS access from Cloudflare =====
 +Here is an example that allows HTTP/HTTPS access from Cloudflare.
 +Use if your webserver is behind the Cloudflare proxy.
 +
 +<code bash>
 +cat << EOF >> /etc/firewall.user
 +uci -q delete firewall.cf_proxy.dest_ip
 +for IPV in 4 6
 +do for IP in $(uclient-fetch -O - \
 +"https://www.cloudflare.com/ips-v${IPV}")
 +do uci add_list firewall.cf_proxy.dest_ip="${IP}"
 +done
 +done
 +/etc/init.d/firewall reload
 +EOF
 +uci -q delete firewall.cf_proxy
 +uci set firewall.cf_proxy="rule"
 +uci set firewall.cf_proxy.name="Allow-Cloudflare-Proxy"
 +uci set firewall.cf_proxy.src="wan"
 +uci add_list firewall.cf_proxy.dest_port="80"
 +uci add_list firewall.cf_proxy.dest_port="443"
 +uci set firewall.cf_proxy.proto="tcp"
 +uci set firewall.cf_proxy.target="ACCEPT"
 +uci commit firewall
 +/etc/init.d/firewall restart
 </code> </code>
  
  • Last modified: 2023/10/14 06:21
  • by vgaetera