an idea to LOG target

[Maciej Soltysiak]

> 	That sounds like a good idea. It might also provide a solution to
> the LOG&DROP problem everyone was talking about. Fabrice MARIE posted a patch
> which added a --drop argument to LOG, and he also posted a translation of
> the LOG target as the log match. But if you use a config file, then you
> could simply use this:
>
> 	drop=0
> 	addr1=10.0.0.1
> 	addr2=20.0.0.2
>
> 	Then, when you compile LOG and log, simply hardlink them to the same
> name (examples anyone?. Then, when you add a LOG or log rule, it reads the
> config file and sets various stuff in the info structure. That way, you could
> set a default of whether to drop packets after logging them or not, and simply
> override it at the command line. The only drawback I see is how to properly
> protect the config file (locking).
>
> 	Is this a good idea, anyone?
>
> Brad
I belive it's a great idea. I've seen --drop and i think it's a good way
to overcome log&drop problem :)

I guess it's not hard to code this 'log configuration' with --drop add-on