Any attempt to use ULOG as a target in an iptables command (i.e. -j ULOG) results in the following error message; iptables: Invalid argument Kernel module support for ULOG is enabled.
Looks a bit like the limit problem we had on sparc64. The netfilter people were able to give me a patch back then. Maybe reporting the bug to that ML would help. Or some C guy could check the current sparc64_limit_fix.patch.bz2 fix and find out if the ULOG problem is a similar problem. (The fact that the limit patch is still needed after a year shows that sparc issues don't have high priority on netfilter)
Yeah, seems to be a sparc64 thing. sparc works ok with -j ULOG, though ulogd bus errors as soon as it gets data.
Based on this post to the ulogd ml <http://lists.gnumonks.org/pipermail/ulogd/2003-December/000458.html>, I created a patch for this fix. However, the kernel does panic with the following message after a rule with -j ULOG is applied; Unable to handle kernel NULL pointer dereference tsk->{mm,active_mm}->context = 00000000000007b6 tsk->{mm,active_mm}->pgd = fffff8003f4e9000 Kernel panic: Aiee, killing interrupt handler! In interrupt handler - not syncing I posted to the ulogd ml with this info, waiting to see if i get a response.
Created attachment 27222 [details, diff] patch to allow -j ULOG rules to not return invalid argument
iptables support for ULOG was fixed in 1.2.11 ulogd still has issues, but that is for another bug.
