Differences

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

--- forward-basic [2023/10/26 16:05] – rs232
+++ forward-basic [2023/10/26 17:27] (current) – [Advanced Scenarios] -condense hogwild
@@ Line 55: / Line 55: @@
 ==== 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 possible solutions to multiplex connectivity on the very same port.
+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.
 === Reverse Proxy ===
-By definition, A proxy must speak the protocol used by the application to perform its job. 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 according to the requested domain. Nginx is able to perform this so-called reverse-proxy for HTTP/HTTPS.
+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.
 === Source Bound Redirection ===
@@ Line 69: / Line 69: @@
  {{:pasted:20231026-084901.png?750}}
-These settings would result in traffic from "source.example.com" (whatever IP address/es this resolves to) towards port 80 and 443 on the router being redirected to a specific LAN IP address matching the rule, this also means that any other source on such ports will be redirected to a different LAN IP address.
+ \\
+The settings above 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