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 [2023/05/28 03:57] – [Firewall] add Smart MTU black hole detection, condense hogwild | advanced-firewall [2023/05/28 04:35] – [Firewall] -format hogwild | ||
---|---|---|---|
Line 6: | Line 6: | ||
===== Firewall ===== | ===== Firewall ===== | ||
- | {{: | + | {{: |
- | **Limit communication | + | |
- | | + | **Limit communication to: **This specifies the maximum number of requests per second to which the Firewall will reply. Setting a limit number is recommended to prevent DDoS attacks.\\ \\ \\ {{: |
+ | |||
+ | \\ | ||
+ | |||
+ | **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. | **Enable DCSP Fix: **Checking this enables a workaround for packet marking, a well-known issue related to DSCP when connected to Comcast. | ||
Line 21: | Line 25: | ||
===== NAT ===== | ===== NAT ===== | ||
- | **NAT loopback:** This technique, also known as " | + | **NAT loopback:** This technique allows LAN devices to access each other via the router' |
* All | * All | ||
Line 27: | Line 31: | ||
* Disabled | * 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. | **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. | ||
\\ | \\ | ||
+ | |||
===== Multicast ===== | ===== Multicast ===== | ||
Line 37: | Line 44: | ||
\\ \\ {{: | \\ \\ {{: | ||
- | **Enable IGMP proxy** - Runs the IGMP (Internet Group Management Protocol) service | + | **Enable IGMP proxy** - Checking this enables |
- | **LAN0/ | + | LAN0 - LAN3 Specifies which bridges will participate |
- | **Enable quick leave** | + | |
+ | | ||
+ | * LAN2 - Checking this means the LAN2 bridge will participate in IGMP proxy/ | ||
+ | * LAN3 - Checking this means the LAN3 bridge will participate in IGMP proxy. | ||
- | **Custom Configuration** - This option allows you to set up advanced parameters for the IGMP proxy daemon. | + | \\ |
+ | |||
+ | **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). | ||
- | **Upstream interface** - Defines where the stream source is expected to live. (Default: blank). | + | **LAN0/ |
- | **LAN0/ | + | **Enable client statistics** - Enabling this causes FreshTomato |
- | **Enable client statistics** - Enabling this causes FreshTomato to collect statistical information about Udpxy clients. | + | **Max clients - ** This represents the maximum number of simultaneous |
- | **Max clients -** Considering this is a lightwave protocol it works well for a limited number of clients, you might want to impose a maximum number.Specifies | + | **Udpxy port**- This specifies |
- | **Udpxy port**- This is where you can consult | + | **Efficient Multicast Forwarding (IGMP Snooping) -** IGMP snooping allows |
- | **Efficient Multicast Forwarding (IGMP Snooping) -** IGMP snooping is a way to have the switch (part of the router) facilitating the discovery of multicast (IGMP) clients. The idea is to only multicast traffic towards ethernet ports where there' | + | therefore, multicast network misconfiguration or other deficiencies can appear as UPnP issues rather than underlying network issues. If IGMP snooping is enabled on a switch, or more commonly a wireless router/ |
**Force IGMPv2** - IGMPv2 enhances the IGMP communication supporting additional messages/ | **Force IGMPv2** - IGMPv2 enhances the IGMP communication supporting additional messages/ | ||