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 01:50] – 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: |
- | **WAN interfaces respond | + | **Limit communication |
- | **Limit communication to **- Specifies | + | \\ |
+ | |||
+ | **Enable TCP SYN cookies: | ||
+ | |||
+ | **Enable DCSP Fix: **Checking this enables a workaround for packet marking, a well-known issue related to DSCP when connected to Comcast. | ||
+ | |||
+ | **Allow DHCP Spoofing: ** | ||
+ | |||
+ | **Smart MTU black hole detection: | ||
+ | |||
+ | |||
+ | ===== NAT ===== | ||
+ | |||
+ | **NAT loopback:** This technique allows LAN devices to access each other via the router' | ||
+ | |||
+ | * All | ||
+ | * Forwarded Only | ||
+ | * Disabled | ||
+ | |||
+ | \\ | ||
+ | |||
+ | {{:: | ||
+ | |||
+ | **NAT target** - This defines the way NAT is implemented for use during loopback. Masquerade is the default, but involves an additional lookup. ad the mapping of done towards an interface. SNAT is minutely faster, as the NAT mapping points directly to the destination IP and so it bypasses the lookup stage. However, SNAT is less reliable than Masquerade. | ||
\\ | \\ | ||
- | {{: | ||
- | **Enable | + | ===== Multicast ===== |
+ | |||
+ | \\ \\ {{: | ||
+ | |||
+ | **Enable | ||
+ | |||
+ | LAN0 - LAN3 Specifies which bridges will participate in IGMP, with the router | ||
+ | |||
+ | * 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 | ||
+ | |||
+ | **Custom Configuration** - This option allows you to set advanced parameters for the IGMP proxy daemon. Consult official IGMP documentation before using this.\\ | ||
+ | |||
+ | \\ {{: | ||
+ | |||
+ | **Enable Udpxy** - Like IGMP proxy, Udpxy allows multicast communications between devices on different VLANs. Since their behavior is very similar, you are advised to use either Udpxy or IGMP proxy, but not both at once. | ||
+ | |||
+ | **Upstream interface** | ||
- | **Enable DCSP Fix** - This enables a workaround for a well-known issue related | + | **LAN0/ |
- | **IPv6 IPSec Passthrough** - FIXME\\ | + | **Enable client statistics** - Enabling this causes FreshTomato to collect statistics about Udpxy clients. |
- | {{: | + | **Max clients |
- | **NAT loopback** - also known as " | + | **Udpxy port**- This specifies |
- | **NAT target** - Defines | + | **Efficient Multicast Forwarding (IGMP Snooping) -** IGMP snooping allows |
- | Multicast\\ | + | Caution is advised, as often, UPnP is the only significant multicast application |
- | {{: | + | If IGMP snooping is enabled on a (wireless router)/ |
- | {{: | + | **Force IGMPv2** - IGMPv2 enhances the IGMP communication supporting additional messages/ |