This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
advanced-firewall [2022/01/21 03:05] – deleted screenshot caption-it was redundant hogwild | advanced-firewall [2023/05/28 04:44] – [Multicast] -clarity-IGMP snooping hogwild | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== Firewall ====== | ||
+ | |||
+ | The Firewall page allows you to configure options to protect or facilitate various types of network communications. | ||
+ | |||
+ | |||
===== Firewall ===== | ===== Firewall ===== | ||
- | The Firewall page allows you to configure options to protect/ | + | {{: |
- | {{: | + | \\ **WAN interfaces respond to ping and traceroute: |
- | **Limit communication to **- Specifies | + | **Limit communication to: |
- | **Enable DCSP Fix** - This enables a workaround for a well-known issue related to DSCP (packet marking) | + | \\ |
+ | |||
+ | **Enable TCP SYN cookies: | ||
+ | |||
+ | **Enable DCSP Fix: | ||
+ | |||
+ | **Allow DHCP Spoofing: ** | ||
+ | |||
+ | **Smart MTU black hole detection: | ||
+ | |||
+ | |||
+ | ===== NAT ===== | ||
- | **IPv6 IPSec Passthrough** - FIXME\\ \\ | + | **NAT loopback:** This technique allows LAN devices to access |
* All | * All | ||
Line 15: | Line 31: | ||
* Disabled | * Disabled | ||
- | **NAT target** - Defines | + | \\ |
+ | |||
+ | {{:: | ||
+ | |||
+ | **NAT target** - This defines | ||
\\ | \\ | ||
- | \\ {{: | ||
- | **Enable IGMP proxy** - Runs the IGMP (Internet Group Management Protocol) service on the router. | + | ===== Multicast ===== |
- | **LAN0/ | + | \\ \\ {{: |
- | **Enable | + | **Enable |
- | **Custom Configuration** - This option allows you to set up advanced parameters for the IGMP proxy daemon. | + | LAN0 - LAN3 Specifies which bridges will participate in IGMP, with the router acting as a proxy between selected LANs. This allows IGMP to work between VLANs. |
+ | |||
+ | * LAN0 - Checking this means the LAN0 bridge will participate in IGMP proxy. | ||
+ | * LAN1 - Checking this means the LAN1 bridge will participate in IGMP proxy. | ||
+ | * LAN2 - Checking this means the LAN2 bridge will participate in IGMP proxy/ | ||
+ | * LAN3 - Checking this means the LAN3 bridge will participate in IGMP proxy. | ||
+ | |||
+ | \\ | ||
+ | |||
+ | **Enable quick leave** - This is a feature of IGMP v2 and later. Enabling this allows the router to stop streaming multicast to an IP address as soon as that device sends a "quick leave" IGMP packet. | ||
+ | |||
+ | **Custom Configuration** - This option allows you to set advanced parameters for the IGMP proxy daemon. | ||
\\ {{: | \\ {{: | ||
- | **Enable Udpxy** - Like IGMP proxy, Udpxy allows multicast communications between | + | **Enable Udpxy** - Like IGMP proxy, Udpxy allows multicast communications between |
+ | |||
+ | **Upstream interface** - Here, enter the stream source is expected to live. (Default: blank). | ||
+ | |||
+ | **LAN0/ | ||
+ | |||
+ | **Enable client statistics** - Enabling this causes FreshTomato to collect statistics about Udpxy clients. | ||
- | **Upstream interface** - Defines where the stream source | + | **Max clients - ** This represents |
- | **LAN0/ | + | **Udpxy port**- This specifies |
- | **Enable client statistics** - Enabling this causes FreshTomato | + | **Efficient Multicast Forwarding (IGMP Snooping) -** IGMP snooping allows the router' |
- | **Max clients -** Considering this is a lightwave protocol it works well for a limited number of clients, you might want to impose | + | Caution |
- | **Udpxy port**- This is where you can consult the Udpxy information on your router.\\ | + | If IGMP snooping is enabled on a (wireless |
**Force IGMPv2** - IGMPv2 enhances the IGMP communication supporting additional messages/ | **Force IGMPv2** - IGMPv2 enhances the IGMP communication supporting additional messages/ | ||