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

2010-05-02 Thread Ryan Blake
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

Re: [Shorewall-users] Kernel Panic on Masq Enable with Shorewall 4.4.8 & 2.6.27.45-0.1-default #1 SMP

2010-05-02 Thread Tuomo Soini
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 seri

Re: [Shorewall-users] Kernel Panic on Masq Enable with Shorewall 4.4.8 & 2.6.27.45-0.1-default #1 SMP

2010-05-02 Thread Mac Smith
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 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? >> >

Re: [Shorewall-users] Kernel Panic on Masq Enable with Shorewall 4.4.8 & 2.6.27.45-0.1-default #1 SMP

2010-05-02 Thread Laurent CARON
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

Re: [Shorewall-users] Kernel Panic on Masq Enable with Shorewall 4.4.8 & 2.6.27.45-0.1-default #1 SMP

2010-05-02 Thread Tom Eastep
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 compatib