<?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[Bound several public address to the same WAN interface, outgoing ip?]]></title><description><![CDATA[<p dir="auto">I need to NAT several public IPs to different internal networks.</p>
<p dir="auto">Setting two address to the same phisical</p>
<p dir="auto">So I set, for example, a second IP to the WAN interface (first IP is 194.176.12.1 - for example):</p>
<p dir="auto">ifconfig em1 194.176.12.2 netmask 255.255.255.192</p>
<p dir="auto">When I navigate, sometime I have 194.176.12.1, sometime I have 194.176.12.2. How can I force the outgoing IP for my internal network?<br />
How can I force the outgoing IP for a specific natting?</p>
<p dir="auto">Any conseil will be appreciated.</p>
]]></description><link>https://forum.netgate.com/topic/4354/bound-several-public-address-to-the-same-wan-interface-outgoing-ip</link><generator>RSS for Node</generator><lastBuildDate>Tue, 21 Apr 2026 14:10:54 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/4354.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 30 Apr 2007 16:45:49 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Bound several public address to the same WAN interface, outgoing ip? on Thu, 03 May 2007 10:29:50 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/cmb">@<bdi>cmb</bdi></a>:</p>
<blockquote>
<p dir="auto">Never use ifconfig aliases. They won't survive a reboot, aren't necessary, and is the wrong way to setup additional IP's on pfsense. See the Virtual IP page. Then look at the NAT page, Outbound tab. You'll need to enable Advanced Outbound NAT, and put in your NAT rules as desired.</p>
</blockquote>
<p dir="auto">Thank you,<br />
now 1:1 NAT works!  :)</p>
<p dir="auto">I have not used Outbound tab because from which I understood "Automatic outbound NAT rule generation (IPSEC passthrough)" is sufficient.</p>
<p dir="auto">I also had to create a rules on the WAN interface to allow traffic from * to the destination internal address, it works, is it the correct way to let packet pass?</p>
<p dir="auto">Thank you in advance.</p>
<p dir="auto">Davide.</p>
]]></description><link>https://forum.netgate.com/post/153992</link><guid isPermaLink="true">https://forum.netgate.com/post/153992</guid><dc:creator><![CDATA[davidemiccone]]></dc:creator><pubDate>Thu, 03 May 2007 10:29:50 GMT</pubDate></item><item><title><![CDATA[Reply to Bound several public address to the same WAN interface, outgoing ip? on Mon, 30 Apr 2007 20:57:48 GMT]]></title><description><![CDATA[<p dir="auto">Never use ifconfig aliases. They won't survive a reboot, aren't necessary, and is the wrong way to setup additional IP's on pfsense. See the Virtual IP page. Then look at the NAT page, Outbound tab. You'll need to enable Advanced Outbound NAT, and put in your NAT rules as desired.</p>
]]></description><link>https://forum.netgate.com/post/153854</link><guid isPermaLink="true">https://forum.netgate.com/post/153854</guid><dc:creator><![CDATA[cmb]]></dc:creator><pubDate>Mon, 30 Apr 2007 20:57:48 GMT</pubDate></item></channel></rss>