There are several guides for this online, but none seem to actually apply to release version 2.0.

To setup pfsense as a transparent firewall / bridge with 2 interfaces, follow these steps from a fresh install:

1. Disable NAT (but not the firewall). See http://doc.pfsense.org/index.php/How_can_I_completely_disable_NAT%3F#Disable_NAT2. VERY IMPORTANT: As mentioned at http://forum.pfsense.org/index.php?topic=30653.0, go to the 'System -> Advanced -> System Tunables' and set net.link.bridge.pfil_bridge from 'default' to '1'3. Bridge WAN and LAN by going to 'Interfaces → Assign → Bridges'4. Create OPT iface and assign the bridge to it by 'Interfaces → Assign → Network Port'5. Add an IP address to the bridge interface; this IP is the one you will use to access the firewall long term6. Add allow all rules to ALL firewall interfaces to avoid being locked out. Ifaces OPT, WAN, and LAN7. Set WAN and LAN interface type to 'none'. (Under 'Interfaces' in GUI)8. Disable DHCP server9. The firewall should now be able to be accessed from all ifaces via the IP on the bridge from step 510. Carefully modify your firewall rules to be more restrictive. DNS, DHCP, etc.

Thank you ever so much for this guide! I have been struggeling with this for some time, and this was of great help!!

I did not however get all the way home:

I made a bridge with WAN+LAN+DMZ interfaces following your guide. I also assigned one additional interface for MGMT outside the bridge with a static IP.

1) I have made rules on all interfaces with "allow everything", but still cannot access the IP-adress I assigned to the bridge (no ping, no http(s) nothing. Neither from LAN nor WAN nor DMZ. What could be wrong? (I can only access the unit via the MGMT interface on the IP assigned to it.)

2) I want to have pfsense run a DCHP server on LAN interface only. Can this be done?

hvar: I believe there are other guides that do show how to do a bridge setup with an additional interface for management; this is the "traditional" way to setup a firewall bridge. This guide is for those wishing to setup a firewall bridge using only 2 interfaces.

For virtual environments (VMware), what does the switching look like on the ESX host? Which NICS go on which vSwitch ports etc? I know you have to enable promiscuous mode...

Example:I have 2 VM's, one is a CentOS VM with an IPV4 address (One NIC), and the other is a pfSense fw setup to be transparent (Two NICs, followed steps above). On the ESX host, I have a WAN vSwitch and a LAN vSwitch. The CentOS VM is on the LAN vSwitch (the LAN vSwitch has no uplinks at all). The pfSense VM has one NIC on the LAN vSwitch, and one NIC on the WAN vSwitch. As of right now, my CentOS VM can communicate out, but nothing can communicate in.

Hi,I have tried this setup and it worked to some extend. However, the idea is to configure limiters per host/ip based on layer 7 and/or general conditions.1. When I create a simple rule with In/Out limiters to TCP/UDP everything works fine and the traffic is limited as supposed to.2. As soon as I create L7+In/Out+TCP/UDP rule the traffic assigned to L7 rule seems to be blocked as well as some other().L7 rule is: protocol - httpvideo, structure - limiter and a precreated limiter is assigned.3. Dhcp, dhs, file sharing work fine with or without L7 rules being setup. And traffic is nicely assigned to a limiter dependent on conditions (destinations or source)

Could L7 limiters be setup in a bridge config? Has someone configured anything similar?This link states that net.link.bridge.pfil_member should be set to "0" http://doc.pfsense.org/index.php/Traffic_Shaping_GuideTo which interface a floating rule should be applied? In some cases it doubles the speed configured by the limiter.

Any info would help. Thank You.

FYI:I have also tried this config in Hyper-V and after step 7 lost connectivity to pfsense. ifconfig down/up for all interfaces did not help.

Unfortunately, I made this guide AFTER I placed the system into production. It is possible that I missed a crucial step in writing the guide.

However, I would guess that if you are having trouble connecting to the web interface after step 7, I would highly suggest that you take a close look at your firewall rules.

In my case, I actually did not add ANY rules to the interfaces; I simply started with a single "Allow All" rule in the "Floating" rules section (step 6). Later on (step 10), I added allow rules for crucial services (INCLUDING THE WEB GUI) and then removed the "Allow All" rule.