> > And, i should really run ULOG to be optimal for realtime logging?
> >
>
> You've already seen what can happen if you don't.
Doh, I forgot to ask do I need to add anything to my kernel for ULOG support,
after looking at the kernel config the line that says:
< > ULOG target support
When you look at the help for that option it says:
CONFIG_IP_NF_TARGET_ULOG:
This option enables the old IPv4-only "ipt_ULOG" implementation
which has been
obsoleted by the new "nfnetlink_log" code (see
CONFIG_NETFILTER_NETLINK_LOG).
This option adds a `ULOG' target, which allows you to create rules in
any iptables
table. The packet is passed to a userspace logging daemon using
netlink multicast sockets; unlike the LOG target which can only be
viewed through syslog.
So, originally I didn't enable ULOG support (at least that option)
because it appears to be outdated. But maybe ULOG will work in
Shorewall without enabling anything?
But, after looking at a few docs, it seems I do need to enable the ULOG support?
BB
--
Have Mercy & Say Yeah
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Shorewall-users mailing list
Shorewall-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/shorewall-users
