<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Overlapping Port Forward Destination on Single Source?]]></title><description><![CDATA[<p dir="auto">For the purposes of 'simplicity'...<br />
I have a service running on port 5555</p>
<p dir="auto">I have two external clients:</p>
<p dir="auto">Employee 1: 10.1.0.100<br />
Employee 2: 20.1.0.200</p>
<p dir="auto">I have one external IP:<br />
30.1.0.100 (CARP)</p>
<p dir="auto">I have two internal resources:</p>
<p dir="auto">System 1: 192.168.1.100<br />
System 2: 192.168.1.200</p>
<p dir="auto">I am trying to NAT:<br />
Source: 10.1.0.100:<em>Any</em> -&gt; Destination: 30.1.0.100:5555<br />
Translated IP: 192.168.1.100:5555</p>
<p dir="auto">Source: 20.1.0.200:<em>Any</em> -&gt; Destination: 30.1.0.100:5555<br />
Translated IP: 192.168.1.200:5555</p>
<p dir="auto">If I set the Destination to "WAN Address" it works.  If I try to set it to "WAN CARP: 30.1.0.100" it says it can't do it because of overlapping destination addresses.  Why can I use the WAN Network or WAN Address but not the actual WAN's CARP address?  Is that a bug or is my logic broken?</p>
<p dir="auto">Since both use different Source IPs for the filter there should never be a conflict between the rules right?</p>
]]></description><link>https://forum.netgate.com/topic/166493/overlapping-port-forward-destination-on-single-source</link><generator>RSS for Node</generator><lastBuildDate>Wed, 16 Sep 2026 10:37:07 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/166493.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 13 Sep 2021 00:47:34 GMT</pubDate><ttl>60</ttl></channel></rss>