<?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[Can&#x27;t get packet filter to work on bridge member interfaces]]></title><description><![CDATA[<p dir="auto">Hello - I am having a terrible time getting packet filtering to work on member interfaces of a bridge. Would appreciate some additional eyeballs to review and advise.</p>
<p dir="auto">I'm using pfsense 2.4.4-p3.</p>
<p dir="auto">Tunables:<br />
net.link.bridge.ipfw = 1<br />
net.link.bridge.pfil_member = 1<br />
net.link.bridge.pfil_bridge = 0</p>
<p dir="auto">(https://www.freebsd.org/cgi/man.cgi?bridge(4) says the first tunable must be enabled for dummynet support, which is a requirement for my setup)</p>
<p dir="auto">I have a functioning WAN interface assigned on igb0.</p>
<p dir="auto">I have interface igb1.300 (VLAN 300 on igb1) defined with no IP address set. This is effectively my "LAN" interface.</p>
<p dir="auto">I create bridge0 and set igb1.300 as its only member.</p>
<p dir="auto">I create an interface for bridge0 and assign it a valid public IP address for my upstream connection (1.1.1.1/24 for example)</p>
<p dir="auto">I have a client node entering pfsense on igb1.300 with a public IP address in the same subnet (1.1.1.2/24 for example, with gateway 1.1.1.1)</p>
<p dir="auto">I create a firewall rule (pass any-any) on igb1.300. No traffic flows, and firewall logs show default deny being hit on the bridge0 interface.</p>
<p dir="auto">If I move the pass rule from igb1.300 to bridge0 it hits the pass rule and traffic flows.</p>
<p dir="auto">If I delete the bridge and use only igb1.300 with the same IP address and firewall rule directly on igb1.300 then the pass rule gets hit and traffic flows.</p>
<p dir="auto">Based on the tunables I am expecting this to function opposite to how it actually is functioning. Am I missing something in the config to make it work as expected? Are my expectations correct for how it should function?</p>
<p dir="auto">NOTE: I already know and agree in principle that bridges in pfsense are evil and should be avoided. With that said, I still need to figure out why this particular configuration is not functioning as expected. Thanks in advance.</p>
]]></description><link>https://forum.netgate.com/topic/150121/can-t-get-packet-filter-to-work-on-bridge-member-interfaces</link><generator>RSS for Node</generator><lastBuildDate>Tue, 06 Oct 2026 09:09:39 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/150121.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 31 Jan 2020 07:58:57 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Can&#x27;t get packet filter to work on bridge member interfaces on Tue, 04 Feb 2020 20:03:44 GMT]]></title><description><![CDATA[<p dir="auto">Anyone?</p>
<p dir="auto">Can anyone at least confirm that this <em>should</em> be working, despite the fact that it very much isn't working?</p>
<p dir="auto">Very much appreciate anything that can help point me in the right direction here. Everything I've found online suggests it should be working but I haven't found anything conclusive.</p>
]]></description><link>https://forum.netgate.com/post/889607</link><guid isPermaLink="true">https://forum.netgate.com/post/889607</guid><dc:creator><![CDATA[AlleyCat]]></dc:creator><pubDate>Tue, 04 Feb 2020 20:03:44 GMT</pubDate></item></channel></rss>