Re: [PATCH] ebtables: Port ebt_[u]log.c to nf[netlink]_log
Bart De Schuymer <[email protected]>
| Newsgroups | gmane.linux.network.bridge.ebtables.devel,gmane.linux.network |
|---|---|
| Message-ID | <[email protected]> |
Op za, 08-10-2005 te 01:49 +0200, schreef Harald Welte:
> Hi Bart!
>
> The patch below is totally untested (though it compiles), and updates
> ebtables to resemble the behaviour that we now have in ipv4 (and ipv6):
> {ip,ip6,eb}tables just tell the nf_log core that they want to log a
> packet, the mechanism (syslog, nfnetlink_log, ...) is actually decided
> by nf_log.
>
> By default, everything will behave like before.
>
> Please review, and test that ebt_log and ebt_ulog are still working as
> expected. Thanks!
>
> [NETFILTER] ebtables: Port ebt_[u]log.c to nf[netlink]_log
>
> Since we now have a netfilter core logging API, we port the bridging log
> and ulog watchers to this new API.
>
> This basically means that if you use the "ebt_log" watcher, it will by
> default log to the system console, but enables a userspace logging daemon
> binds itself to PF_BRIDGE, and take over all logging.
>
> ebt_ulog also registers itself as logger with nf_log, but any packets
> explicitly send to ebt_ulog will always use the ulog mechanism and not
> handled via the generic logging handler.
>
> This change resembles the situation that is now present in ipv4.
I seem to be unable to get Davem's current git tree.
This fails miserably:
cg-clone http://www.kernel.org/pub/scm/linux/kernel/git/davem/net-2.6.git
Your patch won't apply to 2.6.13. At first I thought it was a problem
with evolution or the kernel version, but looking at the source code of
your mail, I see "=20" added here and there...
Any ideas?
cheers,
Bart
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl