<?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[Bridging Physical LAN with VLAN]]></title><description><![CDATA[<p dir="auto">Hi guys,</p>
<p dir="auto">Not sure if in the correct section nor certain on the exact terminology/wording for PFSense.</p>
<p dir="auto">I'm operating in a limited environment (equipment wise) with a client.</p>
<p dir="auto">They have a PFSense box with 4 NICs.</p>
<p dir="auto">Current setup:<br />
NIC1 - WAN port hooked upto DSL service<br />
NIC2 - LAN hooked upto an unmanaged switch<br />
NIC3 - Technically classed as a WAN as its setup as a client to get access onto another clients network/subnet as a route out.<br />
NIC4 - Unused currently - Wanting to be used as a VLAN trunk port for VLAN 10 / LAN and VLAN 20 / NIC3 network</p>
<p dir="auto">We have tested setting up VLANs for the 2 networks but the issue is:<br />
We are wanting to bridge together each tagged vlan and the physical port eg, VLAN 10 tagged on NIC4 with NIC2 LAN and VLAN 20 tagged on NIC4 and NIC3 network.</p>
<p dir="auto">I thought this would be an easy task but my fiddling with bridges doesn't seem to work how I want it.</p>
<p dir="auto">I'm used to linux bridging where I can have multiple physical and virtual interfaces all together.</p>
<p dir="auto">Hoping someone understands what I am trying to do and can assist.</p>
]]></description><link>https://forum.netgate.com/topic/95932/bridging-physical-lan-with-vlan</link><generator>RSS for Node</generator><lastBuildDate>Tue, 21 Apr 2026 22:42:12 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/95932.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 24 Feb 2016 12:36:15 GMT</pubDate><ttl>60</ttl></channel></rss>