Issue #2699 has been updated by dillon.
Try this patch. It could be structural filler that is not being initialized, which rn_match() could barf on: http://apollo.backplane.com/DFlyMisc/pf05.patch -Matt ---------------------------------------- Bug #2699: pf(4) pass rule not beeing applied http://bugs.dragonflybsd.org/issues/2699#change-12136 * Author: ftigeot * Status: New * Priority: Normal * Assignee: * Category: * Target version: ---------------------------------------- My pf.conf contains a pass rule intended to allow email to flow between two servers. Very simplified configuration: [server1]<===>[PF box]<====>[server2] pf.conf looks like this: server1="2001:a:b:c:d" table <server2> {2001:x:y:z:t } pass in on $ext_if proto tcp from $server1 to <server2> port 25 keep state I have recently updated my pf firewall to the new multiprocessor-enabled version in DragonFly 3.9 and since then, TCP connections from server1 are blocked by the PF machine. They do not show up in a tcpdump on the PF box/server2 network interface If I replace the <server2> table by a simple $server2 variable, traffic flows as intended. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account