<?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[Set outbound interface for specific server]]></title><description><![CDATA[<p dir="auto">Hi,</p>
<p dir="auto">I have a pfsense setup with 5 (virtual) wan nics and 1 lan nic. I have to use different wan nics because I have to use specific MACs to be able to 'obtain' the IP. The IP's are in the same subnet.</p>
<p dir="auto">I have added different servers on the LAN side, and I am able to route the specific LAN IP's to the correct server without problems. The only issue I have, is that when 1 of those server does an outbound request, it always takes the primary wan interface. How can I define the exact outbound interface for each server? For instance server1 should take wan1, server2 should take wan2 etc.</p>
<p dir="auto">I tried several approaches:<br />
VIP's: not possible since the IP is already assigned to the interface<br />
Outbound NAT: I can't specify the server that should use the outbound interface<br />
Add extra gateways: not possible because the gateways from my provider are in the same subnet (and so use the same 'external' gateway)</p>
<p dir="auto">I am a bit confused, and I think I'm using a wrong approach. Can someone tell me what I should do to accomplish this?</p>
<p dir="auto">Thanks!</p>
]]></description><link>https://forum.netgate.com/topic/76460/set-outbound-interface-for-specific-server</link><generator>RSS for Node</generator><lastBuildDate>Mon, 13 Apr 2026 14:50:19 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/76460.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 01 Dec 2014 20:47:05 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Set outbound interface for specific server on Sun, 07 Dec 2014 11:11:54 GMT]]></title><description><![CDATA[<p dir="auto">In Outbound NAT you can add manual rules - I would think you can add rules with<br />
source IP = internal IP of the server<br />
destination IP = any<br />
translation address = the public IP you want</p>
<p dir="auto">At least that will translate the internal IPs to the desired external ones.<br />
But I suspect the traffic will still all go out the default interface. Your ISP may or may not accept that???</p>
]]></description><link>https://forum.netgate.com/post/499798</link><guid isPermaLink="true">https://forum.netgate.com/post/499798</guid><dc:creator><![CDATA[phil.davis]]></dc:creator><pubDate>Sun, 07 Dec 2014 11:11:54 GMT</pubDate></item><item><title><![CDATA[Reply to Set outbound interface for specific server on Tue, 02 Dec 2014 06:49:00 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/kom">@<bdi>KOM</bdi></a>:</p>
<blockquote>
<p dir="auto">Maybe this? <a href="https://doc.pfsense.org/index.php/What_is_policy_routing" target="_blank" rel="noopener noreferrer nofollow ugc">Policy-based routing</a>.</p>
</blockquote>
<p dir="auto">I could be wrong, but I believe for Policy Based Routing you need to add multiple upstream gateways. But I can't do that since all the gateways from my provider are the same for the different IP's, and pfsense does not allow that.</p>
]]></description><link>https://forum.netgate.com/post/498841</link><guid isPermaLink="true">https://forum.netgate.com/post/498841</guid><dc:creator><![CDATA[mitch2k]]></dc:creator><pubDate>Tue, 02 Dec 2014 06:49:00 GMT</pubDate></item><item><title><![CDATA[Reply to Set outbound interface for specific server on Mon, 01 Dec 2014 21:25:55 GMT]]></title><description><![CDATA[<p dir="auto">Maybe this? <a href="https://doc.pfsense.org/index.php/What_is_policy_routing" target="_blank" rel="noopener noreferrer nofollow ugc">Policy-based routing</a>.</p>
]]></description><link>https://forum.netgate.com/post/498785</link><guid isPermaLink="true">https://forum.netgate.com/post/498785</guid><dc:creator><![CDATA[KOM]]></dc:creator><pubDate>Mon, 01 Dec 2014 21:25:55 GMT</pubDate></item></channel></rss>