FreshTomato Wiki

User Tools

Site Tools

Trace:
advanced-firewall

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Last revisionBoth sides next revision
advanced-firewall [2023/05/28 04:05] – [NAT] -condense hogwildadvanced-firewall [2023/05/28 05:05] – [Multicast] -clarity of IGMP Snooping and Force IGMPv2 details hogwild
Line 6: Line 6:
 ===== Firewall ===== ===== Firewall =====
  
-{{:pasted:20220118-182859.png}} \\  \\ **WAN interfaces respond to ping and traceroute:  **If enabled, this allows your device to reply to ICMP ping and traceroute request packets from Internet hosts. This is necessary for //ping //and //traceroute to //work from the Internet.+{{:pasted:20220118-182859.png}} \\
  
-**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.\\   \\   \\  {{:pasted:20220118-183317.png}}\\+ \\ **WAN interfaces respond to ping and traceroute:  **If enabled, this allows your device to reply to ICMP ping and traceroute request packets from Internet hosts. This is necessary for //ping //and //traceroute to //work from the Internet.
  
- \\  \\ **Enable TCP SYN cookies:  **Enabling this protects the router from SYN Flood attacks via the "SYN cookies" technique. This function encodes information from the SYN packet into the (SYN/ACK) response. This is a standard method for preventing SYN floods. However, it has certain limitations which may cause issues with some old TCP/IP stacks.+**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.\\   \\   \\ {{:pasted:20220118-183317.png}}\\ 
 + 
 + \\ 
 + 
 +**Enable TCP SYN cookies:  **Enabling this uses the "SYN cookies" technique to protect the router from SYN Flood attacks. This function encodes information from the SYN packet into the (SYN/ACK) response. This is a standard method for preventing SYN floods. However, it has certain limitations which may cause issues with some old TCP/IP stacks.
  
 **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 27: Line 31:
   * Disabled   * Disabled
  
- \\+\\ 
 + 
 +{{::advanced-firewall-nat.jpg?454}} \\ \\
  
 **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.
Line 40: Line 46:
 **Enable IGMP proxy** - Checking this enables the IGMP (Internet Group Management Protocol) service. **Enable IGMP proxy** - Checking this enables the IGMP (Internet Group Management Protocol) service.
  
-LAN0 - LAN3 Specifies which bridges will be participate in IGMP using the router as a proxy between the LANs selected. This allows IGMP to work between VLANs.+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 specifies the LAN0 bridge will participate in IGMP. +  * LAN0 - Checking this means the LAN0 bridge will participate in IGMP proxy. 
-  * LAN1 - Checking this specifies the LAN1 bridge will participate in IGMP. +  * LAN1 - Checking this means the LAN1 bridge will participate in IGMP proxy. 
-  * LAN2 - Checking this specifies the LAN2 bridge will participate in IGMP +  * LAN2 - Checking this means the LAN2 bridge will participate in IGMP proxy. 
-  * LAN3 - Checking this specifies the LAN3 bridge will participate in IGMP+  * LAN3 - Checking this means the LAN3 bridge will participate in IGMP proxy.
  
  \\  \\
  
-**Enable quick leave** - This is a feature of IGMP v2. This allows the router to stop the streaming of a multicast to an IP address as soon as that end device sends the quick leave IGMP packet.+**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 up advanced parameters for the IGMP proxy daemon. Please consult the official IGMP documentation before finalizing these settings.\\   \\+**Custom Configuration** - This option allows you to set advanced parameters for the IGMP proxy daemon. Consult official IGMP documentation before using this.\\   \\
  
  \\ {{:pasted:20220118-190050.png}}\\  \\  \\ {{:pasted:20220118-190050.png}}\\  \\
  
-**Enable Udpxy** - Like IGMP proxy, Udpxy allows multicast communications between senders and receivers in different VLANs. Since their behavior is almost identical, it is recommended you use either Udpxy or IGMP proxy, but not both at the same time.+**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** - Here, enter the stream source is expected to live. (Default: blank). 
 + 
 +**LAN0/LAN1/LAN2/LAN3** - This specifies the location the streaming clients are expected to be found. 
 + 
 +**Enable client statistics** - Enabling this causes FreshTomato to collect statistics about Udpxy clients.
  
-**Upstream interface** - Defines where the stream source is expected to live. (Default: blank).+**Max clients - ** This represents the maximum number of simultaneous Udpxy clients. Udpxy is is a lightweight protocol, and only works well for a limited number of clients. For this reason, you might want to impose a maximum limit.
  
-**LAN0/LAN1/LAN2/LAN3** - This is where the stream clients are expected to live.+**Udpxy port**- This specifies the port on which you can recive Udpxy information from your router.\\  \\   \\  {{:pasted:20220118-190844.png}}\\  \\
  
-**Enable client statistics** - Enabling this causes FreshTomato to collect statistical information about Udpxy clients.+**Efficient Multicast Forwarding (IGMP Snooping) -** IGMP snooping makes the router's switch facilitate discovery of Multicast IGMP clients. This will help to send multicast traffic only towards ports with at least one multicast subscriber.
  
-**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 the maximum number of simultaneous Udpxy clients.+However, caution is advised. Often, UPnP or DLNA is the only significant multicast application in use on a home network. Thus, multicast configuration issues or other deficiencies can appear as UPnP issues, but are actually underlying network issues.
  
-**Udpxy port**- This is where you can consult the Udpxy information on your router.\\  \\   \\  {{:pasted:20220118-190844.png}}\\  \\+Enabling IGMP snooping on a wireless router's/switch will interfere with UPnP/DLNA device discovery. Specifically, the SSDP protocol transmissions. If IGMP snooping is incorrectly or incompletely configured (say, without an active querier or IGMP proxy), this make UPnP appear unreliable.
  
-**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's at least one group joiner (a.k.a. subscriber client). Beware, UPnP is often the only significant multicast application in use in digital home networks; 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/switch, it will interfere with UPnP/DLNA device discovery (SSDP) if incorrectly or incompletely configured (e.g. without an active querier or IGMP proxy), making UPnP appear unreliable. Typical scenarios observed include a server or client (e.g. smart TV) appearing after power on, and then disappearing after a few minutes (often 30 by default configuration) due to IGMP group membership expiring. On this very topic please beware of the wireless multicast forwarding under [[advanced-wireless|Advanced Wireless]]+A common symptom of this is a network host (say, a Smart TV) which appears after it's powered on, but then "disappears" from the network after a few minutes. To be more precise, often this period is 30 minutes. This is because the defaut setting for when IGMP group membership will expire. Please be aware of the wireless multicast forwarding setting in the the //Advanced///[[advanced-wireless|Wireless]] menu.
  
-**Force IGMPv2** - IGMPv2 enhances the IGMP communication supporting additional messages/behavior to optimise the end-to-end communication between client and server. Possibly the most important being the "Group Leave" message which is lacking instead in IGMP v1.\\   \\+**Force IGMPv2** - IGMPv2 enhances IGMP with additional messages/behavior to optimize end-to-end client-server communication. Perhaps the most important of these additional messages is the "Group Leave" message. This message did not exist in previous IGMP versions.\\   \\
  
  
advanced-firewall.txt · Last modified: 2023/05/28 05:39 by hogwild

Page Tools

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki