<?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[Topology Question]]></title><description><![CDATA[<p dir="auto">Greetings,</p>
<p dir="auto">I'm a network and pfSense noob, but getting there. I've read a lot and this forum is by far the best source of good advice I've found.</p>
<p dir="auto">I have a home business and want to keep my biz and home stuff separate. I built a Qotom i7 router and installed pfSense without a hitch. I've setup pfSense for a dual-Lan configuration using two switches, one for each LAN. My home LAN is on the pre-configured NIC and matched the same basic rule set on the biz LAN to get it up.</p>
<p dir="auto">I created the attached topology diagram to help guide me along the way and to seek advice on what I might be screwing up. My home LAN is more complex with IOT devices that I want to block from WAN access (cameras and such) so I'm using a managed switch with a Ubiquiti WAP to serve up wireless access.</p>
<p dir="auto">The firewall rules on each LAN lie ahead as does the setup of the managed switch; those look pretty daunting to me. Before I get to those, I wanted to get some feedback on whether my topology is correct and doable, and how I should plan the next steps in terms of programming pfSense... pitfalls to watch for and things I need to ensure I get right.</p>
<p dir="auto">I would be very grateful for any advice on the layout and the order of tackling what lies ahead when implementing.  Thanks in advance - hopefully the feedback will help others as well.</p>
<p dir="auto"><img src="/assets/uploads/files/1568908046458-topology_150.png" alt="Topology_150.png" class=" img-fluid img-markdown" /></p>
]]></description><link>https://forum.netgate.com/topic/146658/topology-question</link><generator>RSS for Node</generator><lastBuildDate>Wed, 09 Sep 2026 07:38:50 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/146658.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 19 Sep 2019 15:47:34 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Topology Question on Sat, 21 Sep 2019 21:03:17 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/tman222">@<bdi>tman222</bdi></a><br />
It sure does - helps a lot. Yes, I have  a dedicated management PC with the Unifi Controller installed. I will be sure to set up Port 4 correctly.  Cheers!</p>
]]></description><link>https://forum.netgate.com/post/866336</link><guid isPermaLink="true">https://forum.netgate.com/post/866336</guid><dc:creator><![CDATA[traderyoda]]></dc:creator><pubDate>Sat, 21 Sep 2019 21:03:17 GMT</pubDate></item><item><title><![CDATA[Reply to Topology Question on Sat, 21 Sep 2019 18:32:14 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/traderyoda">@<bdi>traderyoda</bdi></a> - If you keep VLAN 80 (management) untagged, you would still be fine even if the Ubiquiti AP does not support tagged traffic on its management interface.  When you setup the Ubiquiti switch just make sure to configure port 4 to pass VLAN 80 untagged traffic along with VLAN 81 - 83 tagged traffic.  I assume you'll have the Unifi Controller sitting on VLAN 80 as well then?</p>
<p dir="auto">Hope this helps.</p>
]]></description><link>https://forum.netgate.com/post/866319</link><guid isPermaLink="true">https://forum.netgate.com/post/866319</guid><dc:creator><![CDATA[tman222]]></dc:creator><pubDate>Sat, 21 Sep 2019 18:32:14 GMT</pubDate></item><item><title><![CDATA[Reply to Topology Question on Sat, 21 Sep 2019 17:27:48 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/tman222">@<bdi>tman222</bdi></a><br />
Thanks for the feedback - at least I'm on the right track.</p>
<p dir="auto">I did plan port 1 as a trunk. I was concerned about managing the AP with tagged traffic and found a lot of confusion, but I thought that Ubiquiti updated their controller software to add this feature last year. I don't have the 'Pro" version of the AP and my version might not permit this - it's a concern. Thanks for the tip about IoT devices - I'll check. My biggest concern are cameras; I have 3 Dahua units.</p>
<p dir="auto">Every time I convince myself that I understanding tagged/untagged I find myself quickly confused again!</p>
]]></description><link>https://forum.netgate.com/post/866314</link><guid isPermaLink="true">https://forum.netgate.com/post/866314</guid><dc:creator><![CDATA[traderyoda]]></dc:creator><pubDate>Sat, 21 Sep 2019 17:27:48 GMT</pubDate></item><item><title><![CDATA[Reply to Topology Question on Sat, 21 Sep 2019 16:14:01 GMT]]></title><description><![CDATA[<p dir="auto">Hi <a class="plugin-mentions-user plugin-mentions-a" href="/user/traderyoda">@<bdi>traderyoda</bdi></a> - Overall, I think this will work.  Looking at the home side of your network I had a couple questions though (things that weren't quite clear from the diagram):</p>
<p dir="auto">Are you planning on passing all tagged and untagged (regular) traffic through port 1 for your home network (i.e. VLAN 80 - 86), making port 1 essentially a trunk port?  If yes, will VLAN 80 be untagged traffic and the rest tagged?  Keep in mind that the Ubiquiti AP does not support tagged VLAN traffic for its management interface (at least this was the case a couple years ago; it may change changed since then).  Using tagged VLAN traffic for the different wireless networks (SSID's) on the AP will work fine though.  Also, make sure that any IoT devices you are planning on using supported tagged VLAN traffic - not all of them do.</p>
<p dir="auto">Hope this helps.</p>
]]></description><link>https://forum.netgate.com/post/866299</link><guid isPermaLink="true">https://forum.netgate.com/post/866299</guid><dc:creator><![CDATA[tman222]]></dc:creator><pubDate>Sat, 21 Sep 2019 16:14:01 GMT</pubDate></item></channel></rss>