> I have looked through the lists but haven''t found a
> definitive answer to this one.
>
> Core 4
> kernel-2.6.12-1.1398_FC4.i686
>
> Shorewall runs fine on Fedora Core 4 with the plain 2.6
> kernel. When I try and start/stop it using the
> kernel-smp-2.6, which is the default off a fresh install
> of core 4 on my P4 server, I get an error when I start or
> stop shorewall. This error is with setenforce 0
>
> ipt_owner: pid, sid and command matching is broken on SMP
>
> I am not convinced I see enough of a performance boost on
> my machine to run the smp kernel so my current solution is
> to run the plain kernel. I was just curious if this was a
> misconfiguration on my end or a known issue that was being
> addressed.
>
> Nathan
>
What your seeing is shorewall loading the module, and testing the results
for the "Shorewall has detected the following iptables/netfilter
capabilities"
part of the start up sequence. The error your seeing, relates to this
module
being broken under SMP, yes it''s a kernel/iptables bug (no sure which),
try
googling for it. What I''m concerned about, does the SMP kernel when
booted
and shorewall started, show "Owner Match: Available" in the start
sequence?
Is the ipt_owner then shown as loaded when checked with lsmod? This could
be bad, if you use owner match support under SMP.
Jerry
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click