Re: [Fwbuilder-discussion] fwb2: bug: custom log headers overwriting logged ACTION

[Vadim K. <va...@vk...>]

On Jul 8, 2004, at 11:31 PM, OpenMacNews wrote:

> hi,
>
> typical default log entry is
>
>        .... RULE 10 -- DENY ....   (header + action)
>
> if define custom log header in RuleOptions
>
>       LogHeader =3D [MY LABEL]
>
> i'd expect to see in logs
>
>        .... [MY LABEL] DENY ....  (header + action)
>
> where toggling the ACTION to, e.g., ACCEPT would, after install, show
>
>        .... [MY LABEL] ACCEPT ....  (header + action)
>
>
>
> instead, my logs are simply showing:
>
>        .... [MY LABEL] ....  (header, NO action)
>
> i.e., no display of ACTION taken.
>

reading users guide :


5.10.1.7. Custom Logging Prefixes

The custom string may show up in the log together with information=20
logged for each rule that has the =92logging=92 option activated. =
Firewall=20
Builder supports the following macros in the log prefix that are=20
expanded at the compile time:

%N rule number in the GUI.
%A rule action
%I interface the rule is associated with
%C (iptables only) iptables chain that this rule generated code for.


display of action is done by means of the custom logging prefix. There=20=

is a default prefix that prints rule number and rule action. Apparently=20=

you erased it and replaced it with your own, that is why you did not=20
get an action printed in the log.

--vk