On Fri, Aug 05, 2005 at 11:26:07AM +0000, Bart De Schuymer wrote: > I don't think your patch will satisfy the simple and rational demand of > people using userspace logging on a bridging firewall: they like to know > what bridge port the packet arrived at/will leave by. These are the > physindev and physoutdev members of the struct ebt_ulog_packet_msg.
Ok, I'll extend nfnetlink_log.c to add TLV's for those two fields in case CONFIG_BRIDGE_NF is set. I'll send a patch later tonight. > Apart from that, I have no objection with introducing incompatibilities > between the output from the old ebt_ulog and the new one using generic > functions; as long as there is no information loss. fine :) -- - Harald Welte <[EMAIL PROTECTED]> http://gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)
pgp6PeLarZoWP.pgp
Description: PGP signature
