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
Next revisionBoth sides next revision
advanced-firewall [2022/01/21 02:31] – formatting hogwildadvanced-firewall [2022/01/21 02:49] – old revision restored (2022/01/21 02:45) hogwild
Line 3: Line 3:
 The Firewall page allows you to configure options to protect/facilitate certain network communications.\\  \\ The Firewall page allows you to configure options to protect/facilitate certain network communications.\\  \\
  
-{{:pasted:20220118-182859.png}}\\  \\ +{{:pasted:20220118-182859.png}}\\  \\ **WAN interfaces respond to ping and traceroute** - When enabled, this allows your device will reply to certain ICMP/UDP packets so that //ping //and //traceroute //from Internet hosts will work.
- +
-**WAN interfaces respond to ping and traceroute** - When enabled, this allows your device will reply to certain ICMP/UDP packets so that //ping //and //traceroute //from Internet hosts will work.+
  
 **Limit communication to **- Specifies the maximum number of requests per second to which the Firewall will reply. Setting a limit number is recommended to prevent DDoS attacks.\\ **Limit communication to **- Specifies the maximum number of requests per second to which the Firewall will reply. Setting a limit number is recommended to prevent DDoS attacks.\\
Line 11: Line 9:
  \\  \\
  
-{{:pasted:20220118-183317.png}}\\  \\+{{:pasted:20220118-183317.png}}\\
  
-**Enable TCP SYN cookies** - Enabling this protects the router from SYN Flood attacks via a well-known technique called "SYN cookies". This technique encodes info from the SYN packet into the response (SYN/ACK). Despite being a standard technique, enabling this will create some secondary limitations that my not be well-handled by some old TCP/IP stacks.+**Enable TCP SYN cookies** - Enabling this protects the router from SYN Flood attacks via a well-known technique called "SYN cookies". This function encodes information from the SYN packet into the response (SYN/ACK). Despite being a standard technique, enabling this will create some secondary limitations that may not be handled well by some old TCP/IP stacks.
  
 **Enable DCSP Fix** - This enables a workaround for a well-known issue related to DSCP (packet marking) when connected to the Comcast ISP. **Enable DCSP Fix** - This enables a workaround for a well-known issue related to DSCP (packet marking) when connected to the Comcast ISP.
  
-**IPv6 IPSec Passthrough** - FIXME\\+**IPv6 IPSec Passthrough** - FIXME\\ \\ 
 + 
 + \\
  
 {{:pasted:20220118-184523.png}}\\ {{:pasted:20220118-184523.png}}\\
  
-**NAT loopback** - also known as "Hairpinning", this technique allows LAN devices to access another LAN device via the WAN interface of your router. This is common practice, for example when connecting to the DDNS domain of your router from the LAN (for administration purposes). This legacy setting is rarely, if ever needed nowadays Also, this function can create a bottleneck on fast connections.+**NAT loopback** - also known as "Hairpinning", this technique allows LAN devices to access another LAN device via the WAN interface of your router. This is common practice, for example when connecting to the DDNS domain of your router from the LAN (for administration purposes). This legacy setting is rarely, if ever needed nowadays. It also can create a bottleneck on fast connections.
  
   * All   * All
Line 27: Line 27:
   * Disabled   * Disabled
  
-**NAT target** - Defines the way NAT is implemented for the sake of Hairpinning. Masquerade is the default however this involves an additional lookup ad the mapping of done towards an interface. SNAT is faster (if ever measurable) as the NAT mapping point directly to the destination IP hence bypassing the lookup stage.+**NAT target** - Defines the way NAT is implemented for the sake of Hairpinning. Masquerade is the default, however this involves an additional lookup ad the mapping of done towards an interface. SNAT is minimally minutely faster as the NAT mapping points directly to the destination IP and so it bypasses the lookup stage.
  
  \\  \\
  
-Multicast\\  {{:pasted:20220118-185509.png}}\\  \\+Multicast\\ {{:pasted:20220118-185509.png}}\\  \\
  
 **Enable IGMP proxy** - Runs the IGMP (Internet Group Management Protocol) for your router.\\  **LAN0/LAN1/LAN2/LAN3** - where enabled the bridges will partecipate in IGMP subscription using the router as a proxy between the LANs selected. This essentially allows IGMP to work between VLANs.\\  **Enable quick leave** - This is a feature of IGMP v2 and allows the router to stop streaming of the multicast IP as soon as the end device sends the quick leave IGMP packet.\\  **Custom Configuration** - This option allows you to set up some advanced parameters for the IGMP proxy daemon. Make sure to consult the official documentation.\\ **Enable IGMP proxy** - Runs the IGMP (Internet Group Management Protocol) for your router.\\  **LAN0/LAN1/LAN2/LAN3** - where enabled the bridges will partecipate in IGMP subscription using the router as a proxy between the LANs selected. This essentially allows IGMP to work between VLANs.\\  **Enable quick leave** - This is a feature of IGMP v2 and allows the router to stop streaming of the multicast IP as soon as the end device sends the quick leave IGMP packet.\\  **Custom Configuration** - This option allows you to set up some advanced parameters for the IGMP proxy daemon. Make sure to consult the official documentation.\\
Line 39: Line 39:
 {{:pasted:20220118-190050.png}}\\  \\ {{:pasted:20220118-190050.png}}\\  \\
  
-**Enable Udpxy** - Similarly to IGMP proxy Udpxy allows multicast communication between sender and receiver sitting in different VLANs. NOTE: since the behavior is pretty much identical you should use either but not both at the same time.+**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.
  
-**Upstream interface** - leave empty for default - Defines where the stream source is expected to live.+**Upstream interface** - Defines where the stream source is expected to live. (Default: blank).
  
-**LAN0/LAN1/LAN2/LAN3** - this is where the stream clients are expected to live.+**LAN0/LAN1/LAN2/LAN3** - This is where the stream clients are expected to live.
  
-**Enable client statistics** - As the option suggest if enabled statistical information about the clients is collected.+**Enable client statistics** - Enabling this causes FreshTomato to collect statistical information about Udpxy clients.
  
-**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 if any.+**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.
  
 **Udpxy port**- This is where you can consult the Udpxy information on your router.\\  \\ **Udpxy port**- This is where you can consult the Udpxy information on your router.\\  \\
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