Shorewall users - May 2010 - Kernel Panic on Masq Enable with Shorewall 4.4.8 & 2.6.27.45-0.1-default #1 SMP

All,

I have been using Shorewall successfully for years on many different machines
and configurations.  However, I just built a new box and wanted to setup
shorewall on it.  I''m running SuSE Linux Enterprise Server 11 and
Shorewall 4.4.8 (latest version as of this e-mail) using the RPM download.  I am
able to install Shorewall just fine and I''m able to setup everything
except for masquerading.  When I enable masq from eth0 -> eth1 or by
specifying my internal IP address range, within seconds of loading shorewall,
the kernel panics and causes a dump.  I also tried the same configuration using
openSUSE 11.3 and, while the kernel did not panic, I was never able to get
masquerading to work.  Essentially I''m trying to get the box to act as
a router.  I read through this listserv to no avail and I al
 so see that you request specific dump information.  However, I''m not
sure it will be saved as the machine crashes when I start it.  Would you need
the dump file?

Please advise as I would really like to use Shorewall!

~Ryan

____________________________________________________________
Send your photos by email in seconds...
TRY FREE IM TOOLPACK at http://www.imtoolpack.com/default.aspx?rc=if3
Works in all emails, instant messengers, blogs, forums and social networks.

------------------------------------------------------------------------------

Ryan Blake wrote:
> However, I''m not sure it will be
> saved as the machine crashes when I start it.  Would you need the
> dump file?
> 
> Please advise as I would really like to use Shorewall!
Contact suse folks. Shorewall can''t cause kernel panic by any means.
Kernel panic means there is a serious bug in kernel so this is SuSE issue.

Btw. 4.4.8 is not latest shorewall. 4.4.8.4 is.

-- 
Tuomo Soini <tis@foobar.fi>
Foobar Linux services
+358 40 5240030
Foobar Oy <http://foobar.fi/>

------------------------------------------------------------------------------

I agree there''s no way IPTABLES could cause kernel panic

What do u say tom

Mac

Sent from my iPhone

On 02-May-2010, at 1:44 PM, Tuomo Soini <tis@foobar.fi> wrote:
> Ryan Blake wrote:
> 
>> However, I''m not sure it will be
>> saved as the machine crashes when I start it.  Would you need the
>> dump file?
>> 
>> Please advise as I would really like to use Shorewall!
> 
> Contact suse folks. Shorewall can''t cause kernel panic by any
means.
> Kernel panic means there is a serious bug in kernel so this is SuSE issue.
> 
> Btw. 4.4.8 is not latest shorewall. 4.4.8.4 is.
> 
> -- 
> Tuomo Soini <tis@foobar.fi>
> Foobar Linux services
> +358 40 5240030
> Foobar Oy <http://foobar.fi/>
> 
>
------------------------------------------------------------------------------
> _______________________________________________
> Shorewall-users mailing list
> Shorewall-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/shorewall-users
------------------------------------------------------------------------------

On 02/05/2010 11:44, Mac Smith wrote:
> I agree there''s no way IPTABLES could cause kernel panic
It happened to me a while ago when I was playing with different iptables 
versions and different kernels.

The userland was simply not compatible with the kernel.

I however doubt of such problems with a distribution like suse, debian, ...

My 0.02€

Laurent

------------------------------------------------------------------------------

On 05/02/2010 04:48 AM, Laurent CARON wrote:
> On 02/05/2010 11:44, Mac Smith wrote:
>> I agree there''s no way IPTABLES could cause kernel panic
> 
> It happened to me a while ago when I was playing with different iptables 
> versions and different kernels.
> 
> The userland was simply not compatible with the kernel.
> 
> I however doubt of such problems with a distribution like suse, debian, ...
The kernel in OpenSuSE 10 also panicked with Shorewall; that was the
result of Shorewall loading an untested combination of kernel modules.
You can *try* to work around the problem by:

a) Setting LOAD_HELPERS_ONLY=Yes in shorewall.conf and
b) Reboot the box.

Regardless of the outcome, the problem should be reported to SuSE.

-Tom
-- 
Tom Eastep        \ When I die, I want to go like my Grandfather who
Shoreline,         \ died peacefully in his sleep. Not screaming like
Washington, USA     \ all of the passengers in his car
http://shorewall.net \________________________________________________

------------------------------------------------------------------------------