This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| advanced-firewall [2026/11/10 19:04] – [NAT] -Formatting hogwild | advanced-firewall [2026/11/10 22:42] (current) – [NAT] -Condense, format NAT loopback table contents hogwild | ||
|---|---|---|---|
| Line 54: | Line 54: | ||
| ===== NAT ===== | ===== NAT ===== | ||
| - | **NAT loopback: | + | **NAT loopback:** NAT Loopback (Hairpinning) logic is implemented in the firewall subsystem using iptables rules. These rules are applied to the PREROUTING and POSTROUTING NAT table chains. |
| - | \\ | + | This table explains the options availabe for NAT loopback: |
| - | - 1. Disabled \\ Under the Hood (iptables): FreshTomato omits loopback rules in the NAT chains. \\ Behavior: When a local LAN client sends traffic destined for the router’s public WAN IP address (or DDNS domain name), the router receives it, sees that there is no active rule translating internal LAN traffic back into the LAN, and simply drops or rejects the traffic. | + | \\ |
| - | \\ | + | ^ Mode ^ Behavior |
| - | + | | **All** | Any LAN traffic sent to the router’s WAN IP is looped back to the router | |
| - | Cons: - LAN devices cannot access local servers using public domain names or public | + | | **Forwarded Only** (default) |
| - | + | | **Disabled** | No loopback NAT rules are added.LAN traffic destined for the router’s public WAN IP or DDNS name is dropped or rejected. | Creates the lowest CPU load and maximum throughput because no extra NAT inspection or packet rewriting occurs.Enforces clearer network-boundary separation. | LAN devices cannot access local servers through the public domain name/public WAN IP, nor reach the router admin interface via the WAN interface. | | |
| - | \\ \\ | + | |
| - | + | ||
| - | 2. Forwarded Only (default) | + | |
| - | + | ||
| - | Under the Hood (iptables): FreshTomato generates rules that apply loopback | + | |
| \\ | \\ | ||
| - | Matches LAN traffic | + | * < |
| - | \\ | + | * < |
| - | + | * Performance: | |
| - | Behavior: If you forward port 8443 to an internal server at 192.168.1.10: | + | * < |
| - | + | ||
| - | \\ | + | |
| - | + | ||
| - | Pros: - Security & Control: Prevents | + | |
| - | + | ||
| - | \\ | + | |
| - | + | ||
| - | Cons: - Will not work for dynamic | + | |
| - | + | ||
| - | \\ \\ | + | |
| - | + | ||
| - | 3. All \\ | + | |
| - | + | ||
| - | Under the Hood (iptables): FreshTomato | + | |
| - | + | ||
| - | \\ | + | |
| - | + | ||
| - | Behavior: | + | |
| - | + | ||
| - | \\ | + | |
| - | + | ||
| - | Pros: - "It just works" convenience—applies to UPnP mapped ports, DMZ hosts, | + | |
| - | + | ||
| - | \\ | + | |
| - | + | ||
| - | Cons: - Performance Bottlenecks (minor): Every single piece of LAN-to-" | + | |
| - | + | ||
| - | \\ | + | |
| {{:: | {{:: | ||