This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
advanced-firewall [2024/10/13 00:50] – [Multicast] -grammar 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 | ||
\\ | \\ | ||
- | **Limit communication to: **Specifies | + | **Limit communication to: **specifies |
+ | |||
+ | 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. | ||
\\ | \\ | ||
- | **Enable DCSP Fix: **Enables | + | **Enable DCSP Fix: **enables |
\\ | \\ | ||
- | **Allow DHCP Spoofing:** | + | **Allow DHCP Spoofing: **makes FreshTomato accept/ |
- | \\ | + | Such behaviour is often categorized as a DHCP spoofing attack, but rarely, might be legitimate. Using this lowers security.\\ |
- | **Smart MTU black hole detection: | + | **Smart MTU black hole detection: |
+ | |||
+ | For details on MTU and black holes, see this blog post: [[https:// | ||
===== NAT ===== | ===== NAT ===== | ||
- | **NAT loopback: | + | **NAT loopback: |
+ | |||
+ | Also known as " | ||
+ | |||
+ | \\ | ||
* All | * All | ||
Line 45: | Line 57: | ||
\\ | \\ | ||
- | **NAT target** | + | **NAT target: **defines how NAT is implemented in loopback |
+ | |||
+ | 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 54: | Line 68: | ||
\\ \\ {{: | \\ \\ {{: | ||
- | **Enable IGMP proxy** | + | **Enable IGMP proxy: **enables the Internet Group Management Protocol service. |
- | LAN0 - LAN3 specifies | + | LAN0 - LAN3 specify |
- | | + | \\ |
- | * LAN1 - Causes the LAN1 bridge to participate | + | |
- | * LAN2 - Causes the LAN2 bridge to participate | + | |
- | * LAN3 - Causes the LAN3 bridge to participate | + | * LAN1 - Causes the LAN1 bridge to join in IGMP proxy. |
+ | * LAN2 - Causes the LAN2 bridge to join in IGMP proxy. | ||
+ | * LAN3 - Causes the LAN3 bridge to join in IGMP proxy. | ||
\\ | \\ | ||
- | **Enable quick leave** | + | **Enable quick leave:** this IGMPv2 |
\\ | \\ | ||
- | **Custom Configuration** | + | **Custom Configuration:** lets you configure |
\\ {{: | \\ {{: | ||
- | **Enable Udpxy** | + | **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 |
+ | |||
+ | (Default: blank). | ||
\\ | \\ | ||
- | **LAN0/ | + | **LAN0/ |
\\ | \\ | ||
- | **Enable client statistics** | + | **Enable client statistics:** causes |
\\ | \\ | ||
- | **Max clients | + | **Max clients: **the maximum number of simultaneous Udpxy clients. |
+ | |||
+ | Udpxy is is a lightweight protocol, | ||
\\ | \\ | ||
- | **Udpxy port**- Specifies | + | **Udpxy port: **specifies |
+ | |||
+ | \\ | ||
- | **Efficient Multicast Forwarding (IGMP Snooping) | + | **Efficient Multicast Forwarding (IGMP Snooping): **IGMP snooping makes the router' |
- | However, caution is advised. IGMP Snooping can interfere with functioning of UPnP or DLNA. This can make Multicast configuration errors or deficiencies appear as UPnP issues. Enabling IGMP snooping on a router' | + | However, caution is advised. IGMP Snooping can interfere with functioning of UPnP or DLNA. This can make Multicast configuration errors or deficiencies appear as UPnP issues. Enabling IGMP snooping on a router' |
A common symptom of this is a network host (say, a Smart TV) which appears after it's powered on, but then " | A common symptom of this is a network host (say, a Smart TV) which appears after it's powered on, but then " | ||
Line 103: | Line 127: | ||
\\ | \\ | ||
- | **Force IGMPv2** | + | **Force IGMPv2: **forces IGMPv2 to be used on the network. |
+ | |||
+ | IGMPv2 enhances IGMP with additional messages/ | ||
\\ | \\ | ||
Line 113: | Line 139: | ||
MRT (Maximum Response Time) field. This new field in query messages specifies how much time hosts have to respond to the query. | MRT (Maximum Response Time) field. This new field in query messages specifies how much time hosts have to respond to the query. | ||
- | Querier election process. When two routers are on the same subnet, only one should send query messages. Having an " | + | Querier election process. When two routers are on the same subnet, only one should send query messages. Having an " |
+ | |||
+ | \\ | ||
+ | |||
+ | | ||