Differences

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

--- forward-basic [2023/10/26 17:16] – [Advanced Scenarios] -clarity hogwild
+++ forward-basic [2024/11/27 01:45] (current) – [Advanced Scenarios] hogwild
@@ Line 7: / Line 7: @@
 ==== NAT ====
-NAT (Network Address Translation) is a feature which allows multiple LAN clients with private (non-routable) IP addresses to connect to the Internet via a single public IP address. NAT re-addresses outgoing packets to the Internet from private LAN clients with FreshTomato's public (WAN) address. Conversely, NAT re-addresses incoming packets coming from the Internet with the private IP address of the correct LAN client. All this is transparent. The hosts on the LAN and the Internet never know it's happening. In other words, NAT takes traffic from network 1 and makes it appear on network 2 as if it's coming from the router IP address on network 2. The cache of address mappings and open/closed connections is called the NAT Table.
+NAT (Network Address Translation) is a feature that allows multiple LAN clients with private (non-routable) IP addresses to connect to the Internet via a single public IP address.
-Connections initiated on the Internet will not reach a LAN IP address, as the PAT (Port Address Translation) table doesn't contain references to those connection attempts. By coincidence, this acts as minimal security feature.
+NAT re-addresses outgoing packets to the Internet from private LAN clients with FreshTomato's public (WAN) address. Conversely, NAT re-addresses incoming packets coming from the Internet with the private IP address of the correct LAN client. All this is transparent. The hosts on the LAN and the Internet aren't aware it's happening.
+NAT takes traffic from network 1 and makes it appear on network 2 as if it's coming from the router IP address on network 2. The store of address mappings and open/closed connections is called the NAT Table.
+Connections initiated via the Internet won't reach a LAN IP address, as the PAT (Port Address Translation) table doesn't contain references to those connection attempts. As a side effect, this minimally increases security.
  \\
 ==== PAT ====
-There are several types of NAT. The most common and relevant for FreshTomato is PAT (Port Address Translation). By default, FreshTomato performs PAT translation. With PAT, translation happens not only between private and public IP addresses, but also between ports. For example, a request for an Internet connection from 192.168.0.100 to google.com will create a NAT mapping to allow the return packets to be sent to the correct LAN device on the correct port. However, in some cases, you may want to have one port on the WAN always mapped/redirected to a single LAN client.
+There are several types of NAT. The most common and relevant for FreshTomato is PAT (Port Address Translation). PAT is FreshTomato's default. With PAT, translation happens not only between private and public IP addresses, but also between ports. For example, a request for an Internet connection from 192.168.0.100 to google.com will create a NAT mapping to allow the return packets to be sent to the correct LAN device on the correct port. However, in some cases, you may want to have one port on the WAN always mapped/redirected to a single LAN client.
-NOTE: There is an obsolete setting in the Miscellaneous section of some older versions in of the //Advanced///[[advanced-routing|Routing]] menu that suggests FreshTomato can operate in Gateway mode or Router mode. Ignore this, and leave it set to "Gateway", regardless of your configuration.
+Note that there's an obsolete setting in the [[advanced-misc|Miscellaneous]] menu of some old versions that suggests FreshTomato can operate in Gateway mode or Router mode. Ignore it, and leave it set to "Gateway", regardless of your configuration.
  \\
@@ Line 25: / Line 30: @@
  \\
-**On:** Checking this enables the settings in that row of the table. (Default: Off).
+**On:** checking this enables the settings in that row of the table. (Default: Off).
-**Protocol:** This selects which transport layer protocols are forwarded. (Default: UDP)
+ \\
+**Protocol:** here, select which transport layer protocols are forwarded. (Default: UDP)
   * UDP - only UDP connections are forwarded
@@ Line 39: / Line 46: @@
  \\
-**Src Address**: (Optional). This will restrict the rule so it's applied only from specific source addresses. DNS hostnames, FQDN names and IP addresses are all valid here. Leaving this empty configures port forwarding to be "from any address".
+**Src Address**: this option restricts the rule so it's applied only from certain source addresses.
-**Ext Port:** This defines a mapping to the (external) port the Internet connection expects to use. It can be a single port or a range, with syntax: "FromPort-ToPort".
+DNS hostnames, FQDN names and IP addresses are valid here. Leaving this empty configures port forwarding "from any address".
-**Int Port:** (Optional). Here, you can specify a different (internal) port for the target LAN IP address. Leaving this empty uses the same port as the Ext Port setting\\ (Default: empty).
+ \\
-**Int Address:** This specifies the internal address to which the port on the LAN the traffic should be redirected.
+**Ext Port:** defines a mapping to the (external) port the Internet connection is expecting.
-**Description:** Here, enter any text to help you remember the reason for the mapping. Most users enter the application name, or protocol used, such as "RDP" or "Mail Server".
+This can be a single port/range, with syntax: "FromPort-ToPort".
  \\
+**Int Port:** this option lets you specify a different (internal) port for the target LAN IP address.
+Leaving this empty uses the same port as the Ext Port setting (Default: empty).
  \\
+**Int Address:** specifies the internal address to which the port on the LAN the traffic should be redirected.
+ \\
+**Description:** here, enter any text to remind you of the reason for the mapping.
+Most users enter the application name or protocol used. For example: "RDP" or "Mail Server".
+ \\
+ \\
 ==== Advanced Scenarios ====
-As we know, only one given socket (port/protocol combination) can be forwarded at any given time. For example, if port 80 is already redirected to 192.168.1.10, this port is now "taken" from the router's pool and all inbound connections will be redirected to the mapped LAN IP address. However, there are two ways to allow you to multiplex connectivity on the same port.
+Only one given socket (port/protocol combination) can be forwarded at a given time. For example, if port 80 is already redirected to 192.168.1.10, this port is now "taken" from the router's pool and all inbound connections will be redirected to the mapped LAN IP address. However, there are two ways to allow you to multiplex connectivity on the same port.
 === Reverse Proxy ===
-In order to perform its job, a proxy must speak the protocol used by the application. For example, an HTTP proxy cannot serve SMTP.  If you needed to redirect, say,  HTTP to multiple internal hosts from the same external port, a reverse proxy is a good solution. According to HTTP v1.1, the target hostname must be included in the HTTP client request. This allows a proxy to fetch such information, and redirect it according to the requested domain. Nginx is able to perform this so-called reverse-proxy for HTTP/HTTPS.
+To do its job, a proxy must speak the protocol used by the application. For example, an HTTP proxy cannot serve SMTP.  If you need to redirect, say,  HTTP to multiple internal hosts from the same external port, a reverse proxy is a good solution. According to HTTP v1.1, the target hostname must be included in the HTTP client request. This allows a proxy to fetch such information, and redirect it to to the requested domain. Nginx is able to perform this reverse-proxy for HTTP/HTTPS.
 === Source Bound Redirection ===
-If the source IP and/or FQDN is well-known, you can create multiple port mapping references on the same port:protocol combination as long as the source is defined differently.  The following settings would work fine:
+If the source IP and/or FQDN is well-known, you can create multiple port mapping references on the same port:protocol combination, as long as the source is defined differently.  The following settings would work fine:
  \\
@@ Line 71: / Line 95: @@
  \\
-The above settings above would cause traffic from "source.example.com" (its IP address/es) towards ports 80 and 443 on the router, to be redirected to a specific LAN IP address in that rule. They would also cause any other traffic on such ports that was not from source.example.com to be redirected to a different LAN IP address.
+The above settings would cause traffic from the IP address(es) of "source.example.com" towards ports 80 and 443 on the router, to be redirected to the specific LAN address in that rule. They would also cause traffic on such ports that was //not// from source.example.com to be redirected to a different LAN IP address.
  \\
+ \\ \\

FreshTomato Wiki

User Tools

Site Tools

Differences

Page Tools