On 14-01-05 09:44 AM, Benjamin Swatek wrote:
Hi all,

following up on this thread: "Bridge LAN ports to act like a switch"
http://forum.pfsense.org/index.php?topic=48947.0

I am looking for a way to bridge 3 VLAN interfaces together so they act as one inside the pfSense box for the purpose of traffic shaping on the bridge. Now the 3 interfaces still need to act as single interfaces running 3 different DHCP servers on each.

I looked into the above thread, but just bridging the 3 interfaces together they loose their IP addresses, which is something that I can’t afford as they serve 3 different LANs.

I want to *join* the interfaces together inside pfSense so I can throw all the traffic together in one big queue and start shaping according to subnet and ports.

Any hints?

That thread makes my head hurt, it's a bunch of people who don't understand the difference between Layer 2 and Layer 3 arguing about how to make it work.

Here's the only hint I could find:
http://blog.davidvassallo.me/2012/10/23/traffic-shaping-pfsense/

And... the whole *point* of bridging is that you lose the individuality of each NIC at Layer 3 (where IP lives).

I think what you might want is to create 3 VLAN interfaces on the trunk port, then 1 non-VLAN interface on each of 3 independent NICs, then bridge one NIC and one VLAN together... 3 times. You'll wind up with 3 bridges.

However, comparing that to the link I provided above doesn't result in any obvious solution for you.

Another solution would simply be to route instead of bridging.

As usual, I strongly suggest referring to a primer on the OSI model and make sure you fully understand the difference between Layer 2 (ethernet) and Layer 3__ (IP), and the corollary, the difference between switching/bridging and routing. You've also got VLANs thrown in there, which actually live at layer 2 but have layer 3 implications.

Despite the fact pfSense supports traffic shaping on bridges, I'm not certain it'll be possible in your exact scenario without several more complicated steps.

--
-Adam Thompson
 [email protected]

_______________________________________________
List mailing list
[email protected]
http://lists.pfsense.org/mailman/listinfo/list

Reply via email to