mangle error using Shorewall v 1.4.5 on kernel 2.4.18-bf2.4-sun4u

2003-07-03 Thread John Hedge








Ive installed Shorewall on my Ultra1 running Woody
(2.4.18-bf2.4-sun4u).



Im getting the following error message when I try to
start Shorewall:

can't
initialize iptables table `mangle': Table does not exist (do you need to
insmod?)
Perhaps iptables or your kernel needs to be updated.

(The
version of iptables is the latest for Woody; i.e. 1.2.6a-5)

Is
iptables built into this kernel or do I need to insmod or is there another
issue underlying this error message?

Thanks,

John








RE: mangle error using Shorewall v 1.4.5 on kernel 2.4.18-bf2.4-sun4u

2003-07-03 Thread David Demland



John,

I have 
been working on this same problemall night. I have just found out what the 
problem is. The disk images, I downloaded and used just two days ago, are 
Debian. But it turns out that this new disk image does not have a 2.4 kernel. 
Instead it has a 2.2 kernel which does not support iptables. This was very 
disappointing to me. I have spent a whole night working on settingup a 
system with the newest version of the OS just to find out it is not the newest 
version of the OS.

Not 
only does it makeour industry, as a whole, look unprofessional, but it 
makes each of us working in this industry lose credibility. How does this set 
apart the systems that we are trying to build in Linux from other OSes? I now 
have to download the update image and see how this will install what I hope is a 
new kernel. Otherwise I am going to have to find out which kernel I need and do 
an apt-get on that exact kernel and install it my self.

In 
short I think it was stupid that the new CD images did not install the newest 
kernel. I would hope that in the future these PR issues would be looked at. If 
Linux is going to move to the next level, it is going to have to find a way to 
show medium and smaller businesses how there is a great return on the investment 
of Linux. What has just happen to me, and most likely you, does not help prove 
the lower cost of Linux.

David 
Demland

  -Original Message-From: John Hedge 
  [mailto:[EMAIL PROTECTED]Sent: Wednesday, July 02, 2003 10:26 
  PMTo: debian-sparc@lists.debian.orgSubject: mangle error 
  using Shorewall v 1.4.5 on kernel 2.4.18-bf2.4-sun4u
  
  I’ve installed Shorewall on my 
  Ultra1 running Woody (2.4.18-bf2.4-sun4u).
  
  I’m getting the following error 
  message when I try to start Shorewall:
  “can't initialize 
  iptables table `mangle': Table does not exist (do you need to 
  insmod?)Perhaps iptables or your kernel needs to be updated.”
  (The 
  version of iptables is the latest for Woody; i.e. 1.2.6a-5)
  Is 
  iptables built into this kernel or do I need to insmod or is there another 
  issue underlying this error message?
  Thanks,
  John


Re: mangle error using Shorewall v 1.4.5 on kernel 2.4.18-bf2.4-sun4u

2003-07-03 Thread Patrick Morris
Huh? I'm guessing you installed the latest stable version (though it's 
hard to know, since you never mention what version gave you trouble).  
It says right near the top of the release notes:


At install time, the kernel used is 2.2.20, however a 2.4 kernel, the 
latest stable branch is included for those who wish to benefit from it.


If you were expecting it to install with a 2.4 kernel, that's got 
nothing to do with Debian looking unprofessional, losing 
credibility, or being stupid,  and everything to do with your not 
paying attention to what you were getting before you installed it, and 
assuming it was something it isn't.


If you were expecting the latest and greatest... well, Debian stable 
isn't it, and never will be -- check out the testing or unstable 
branches, but don't flame the Debian maintainers when you didn't even 
take the time to glance at the release notes.


David Demland wrote:

Not only does it make our industry, as a whole, look unprofessional, 
but it makes each of us working in this industry lose credibility.


In short I think it was stupid that the new CD images did not install 
the newest kernel. I would hope that in the future these PR issues 
would be looked at.




This message is intended only for the use of the person(s) listed above as the 
intended recipient(s), and may contain information that is PRIVILEGED and 
CONFIDENTIAL.  If you are not an intended recipient, you may not read, copy, or 
distribute this message or any attachment. If you received this communication 
in error, please notify us immediately by e-mail and then delete all copies of 
this message and any attachments.

In addition you should be aware that ordinary (unencrypted) e-mail sent through 
the Internet is not secure. Do not send confidential or sensitive information, 
such as social security numbers, account numbers, personal identification 
numbers and passwords, to us via ordinary (unencrypted) e-mail.