search for: mbuff

...t this snip: depmod: *** Unresolved symbols in /lib/modules/2.2.19-rtl/net/smc91111.o depmod: proc_dointvec_R7aaff751 depmod: proc_dostring_R90015efc depmod: unregister_sysctl_table_Rbb90d4ef depmod: register_sysctl_table_R3a74e1c1 depmod: *** Unresolved symbols in /lib/modules/2.2.19-rtl/misc/mbuff.o depmod: mem_map_R3362b304 depmod: *** Unresolved symbols in /lib/modules/2.2.19-rtl/misc/rtl_fifo.o depmod: __wake_up_R0e58d99a depmod: register_chrdev_R0429f8ef depmod: interruptible_sleep_on_timeout_Re25f7722 depmod: __pollwait_R2cf42003 Here are the modules I use (ls -Rla /lib/modules/2....

...> Likewise, Rod Grimes suggested: > ------------------ > No, but it should be trivial to patch the code to allow your !any, if > you consider that !any is the same as =null: > > ipfw count ip from any to any in recv null > > Ie, the recv keyword looks at the ifp in the mbuff, the ifp will be null > for packets originated on the local machine. /usr/src/sys/netinet/ip_fw2.c -- seemed to be the place, but the start of the s/r that caught my eye is not immediately suggesting that there is a way to match a null ifp without patching code as its trapped before the ch...