This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
advanced-firewall [2024/11/10 20:25] – [Firewall] hogwild | advanced-firewall [2024/11/27 00:42] (current) – [Multicast] hogwild | ||
---|---|---|---|
Line 8: | Line 8: | ||
{{: | {{: | ||
- | \\ **WAN interfaces respond to ping and traceroute: | + | \\ **WAN interfaces respond to ping and traceroute: |
+ | |||
+ | This is needed for //ping //and // | ||
\\ | \\ | ||
- | **Limit communication to: **specifies the maximum number of requests per second to which the Firewall replies. Setting a limit is recommended to prevent DDoS attacks.\\ | + | **Limit communication to: **specifies the maximum number of requests per second to which the Firewall replies. |
+ | |||
+ | Setting a limit is recommended to prevent DDoS attacks.\\ | ||
\\ | \\ | ||
- | **Enable TCP SYN cookies: | + | **Enable TCP SYN cookies: |
+ | |||
+ | It encodes information from the SYN packet into the (SYN/ACK) response. It is a standard method for preventing SYN floods. However, it has limitations that may cause issues with some old TCP/IP stacks. | ||
\\ | \\ | ||
Line 26: | Line 32: | ||
**Allow DHCP Spoofing: **makes FreshTomato accept/ | **Allow DHCP Spoofing: **makes FreshTomato accept/ | ||
- | Such behaviour is often categorized as a DHCP spoofing attack, but rarely, might be legitimate. | + | Such behaviour is often categorized as a DHCP spoofing attack, but rarely, might be legitimate. |
**Smart MTU black hole detection: | **Smart MTU black hole detection: | ||
Line 35: | Line 41: | ||
===== NAT ===== | ===== NAT ===== | ||
- | **NAT loopback:** lets LAN devices access each other via the router' | + | **NAT loopback:** lets LAN devices access each other via the router' |
+ | |||
+ | Also known as " | ||
\\ | \\ | ||
Line 49: | Line 57: | ||
\\ | \\ | ||
- | **NAT target: **defines how NAT is implemented in loopback situations. Masquerade is the default, but involves an additional lookup, and the mapping is done towards an interface. SNAT is minutely faster, as its NAT mapping points directly to the destination IP and thus bypasses | + | **NAT target: **defines how NAT is implemented in loopback situations. |
+ | |||
+ | Masquerade is the default, but involves an additional lookup, and the mapping is done towards an interface. SNAT is minutely faster, as its NAT mapping points directly to the destination IP, thus bypassing | ||
\\ | \\ | ||
Line 71: | Line 81: | ||
\\ | \\ | ||
- | **Enable quick leave:** this IGMPv2 feature lets the router stop multicasting to an IP when the device sends a "quick leave" packet. | + | **Enable quick leave:** this IGMPv2 feature lets the router stop multicasting to an IP that has sent it a "quick leave" packet. |
\\ | \\ | ||
- | **Custom Configuration: | + | **Custom Configuration: |
\\ {{: | \\ {{: | ||
- | **Enable Udpxy: **like IGMP proxy, | + | **Enable Udpxy: **like IGMP proxy, |
+ | |||
+ | Since they are similar, use one or the other, but not both at the same time. | ||
\\ | \\ | ||
- | **Upstream interface** | + | **Upstream interface: **here, enter the expected stream source location. |
+ | |||
+ | (Default: blank). | ||
\\ | \\ | ||
- | **LAN0/ | + | **LAN0/ |
\\ | \\ | ||
- | **Enable client statistics** | + | **Enable client statistics:** causes FreshTomato to collect statistics about Udpxy clients. |
\\ | \\ | ||
- | **Max clients: **the maximum number of simultaneous Udpxy clients. | + | **Max clients: **the maximum number of simultaneous Udpxy clients. |
+ | |||
+ | Udpxy is is a lightweight protocol, | ||
\\ | \\ | ||
Line 111: | Line 127: | ||
\\ | \\ | ||
- | **Force IGMPv2** | + | **Force IGMPv2: **forces IGMPv2 to be used on the network. |
+ | |||
+ | IGMPv2 enhances IGMP with additional messages/ | ||
\\ | \\ |