Is kernel bridging code broke?

["Scott Ullrich" <GeekGod@xxxxxxxxxxx>]

I've been trying to compile a kernel with IPFIREWALL and BRIDGING support
but keep running into:

sh ../../conf/newvers.sh GENERIC
cc -c -O -pipe  -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
  -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -fformat-extens
ions -ansi -g -nostdinc -I. -I../.. -I../../../include -I../../contrib/dev/a
cpica -I../../contrib/ipfilter  -D_KERNEL -include
pt_global.h  -mpreferred-stack-boundary=2 -fno-common -ffreestanding  vers.c
linking kernel.debug
bridge.o: In function `bdg_forward':
/usr/src/sys/compile/WATCHER/../../net/bridge/bridge.c:843: undefined
reference to `fr_checkp'
/usr/src/sys/compile/WATCHER/../../net/bridge/bridge.c:865: undefined
reference to `fr_checkp'
/usr/src/sys/compile/WATCHER/../../net/bridge/bridge.c:882: undefined
reference to `fr_checkp'
*** Error code 1

Stop in /usr/src/sys/compile/WATCHER.

My kernel configuration is:

# diff -rub GENERIC WATCHER
--- GENERIC     2004-06-25 01:09:38.000000000 -0400
+++ WATCHER     2004-07-23 10:02:12.000000000 -0400
@@ -16,6 +16,9 @@

 makeoptions    DEBUG=-g                #Build kernel with gdb(1) debug
symbols

+options                BRIDGE
+options                IPFIREWALL

After adding IPFILTER and rebuilding everything works great.   So I am
curious if bridging support is now dependent on ipfilter or do I need to
include something such as PFHOOKS?

Just to make absolute sure I removed IPFILTER and attempted a kernel build
again with the same results.

Any ideas?

Thanks,

Scott