<?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[Limiting Outbound Destinations]]></title><description><![CDATA[<p dir="auto">We have web server behind pfsense that needs to access a variety of sites for various services (freight calculations, sales taxes, etc).  In order to really lock down the server, I want to block all outgoing access to anything other than those sites that are explicitly allowed.</p>
<p dir="auto">On another client, we use Sonicwalls (which we are happily replacing with pfsense in our new installation).  Sonicwall does have a couple of features that make this pretty easy.  It has the ability to create an address object (think Alias in pfsense) with a wildcarded name.  So I can create an alias called UPS which points to "*.ups.com" - and the sonicwall worries about any address resolution.</p>
<p dir="auto">I can take this a step further by creating another Address Object (alias) that is a collection of other objects.  So after creating all of my allowed outgoing domains, I create a new object called "Permitted Outgoing Sites" and all of the individual go into it. I then create a single rule that has the destination of Permitted Outgoing sites and the various ports that are allowed - and just like that I'm done.  When we have a new vendor, I just add the alias, and add it to the parent record.</p>
<p dir="auto">I know I could do most of this in pfsense with inidividual entries, but it becomes a maintenance nightmare (if ip addresses change, or the vendors increase the number of web servers, etc).</p>
<p dir="auto">Am I missing something, or am I pretty much limited to creating the individual aliases?</p>
]]></description><link>https://forum.netgate.com/topic/11133/limiting-outbound-destinations</link><generator>RSS for Node</generator><lastBuildDate>Sun, 15 Mar 2026 04:53:03 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/11133.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 29 Sep 2008 00:35:25 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Limiting Outbound Destinations on Mon, 29 Sep 2008 12:39:33 GMT]]></title><description><![CDATA[<p dir="auto">Actually, you can already create an alias like 'www.ups.com' but it only gets updated with one corresponding IP once when the filters are loaded initially.<br />
IMHO further support is planned for 1.3 - but as usual with this kind of versions - don't hold me liable for it being actually implemented in release. Whenever that will be anyway…</p>
]]></description><link>https://forum.netgate.com/post/182399</link><guid isPermaLink="true">https://forum.netgate.com/post/182399</guid><dc:creator><![CDATA[jahonix]]></dc:creator><pubDate>Mon, 29 Sep 2008 12:39:33 GMT</pubDate></item><item><title><![CDATA[Reply to Limiting Outbound Destinations on Mon, 29 Sep 2008 09:25:46 GMT]]></title><description><![CDATA[<p dir="auto">You may want to use squid, with SquidGuard if the list is long (over a dozen or so I suspect).</p>
<p dir="auto">You'll need then to block outbound access to port 80 and 443 to stop people bypassing the filtering.  If you look at the various threads about Squid/SquidGuard in the packages forum you should get a good start.</p>
]]></description><link>https://forum.netgate.com/post/182382</link><guid isPermaLink="true">https://forum.netgate.com/post/182382</guid><dc:creator><![CDATA[Cry Havok]]></dc:creator><pubDate>Mon, 29 Sep 2008 09:25:46 GMT</pubDate></item></channel></rss>