-
I can confirm this on a fresh install of IPCop v1.9.7 as well.
If looks like the libipt_recent is not included in the list of files to be packaged onto the install tarball..
2009-08-19 19:10:15 UTC in IPCop Firewall
-
That file is not missing on IPCop 1.4.21, and those commands work without error.
So either this is a bug that has been fixed or you have filesystem corruption leading to missing files. I suggest you boot from a Live CD and run fsck on all filesystems, then if there are no problems upgrade to the current version of IPCop.
Upgrading will also fix a lot of other bugs and security problems, so...
2009-08-07 09:18:38 UTC in IPCop Firewall
-
The problem was that glibc was built with the --host and --build options defaulting to the current CPU. Both of these have now been set to i486-pc-linux-gnu which seems to fix the problem.
I have test revision 1421 and it now boots on a Pentium 200 CPU. The first fix for this has been introduced in 1351. The bug was probably introduce with the 2.7 glibc in 1152.
More details in the...
2008-06-01 09:15:20 UTC in IPCop Firewall
-
Tests show that init is not run because busybox fails to run on Pentium (i586) CPUs with error message "Illegal instruction".
The problem appears to be with the C libraries, because all binaries tested fail to run on recent IPCop builds, but do work when copied to machine running different version of Linux (eg Debian 4.0). Similarly binaries from Debian can be run on IPCop with i686 CPUs, but...
2008-04-27 22:02:16 UTC in IPCop Firewall
-
On Pentium CPUs the IPCop kernel does not run the initramfs, stoppping at this point:
Freeing unused kernel memory: 276k freed
input: AT Translation Set 2 keyboard as
This has been known to fail when booting from an install CDROM, PXE and hard disk with kernel & initramfs built from SVN r1301.
Machines known to fail are a Pentium 200 with 128MB RAM on Intel HX...
2008-04-24 17:22:26 UTC in IPCop Firewall
-
Thanks for the information from 'top'.
They show that each httpd process is using less than 3MB. Snort is using 56MB.
I think any problems you are having with lack of memory is due to Snort.
The next time there is a problem try switching off Snort and then check the memory use of httpd.
For reference here is the memory usage on the Pentium 75 firewall that has been running for 4...
2008-03-29 17:13:33 UTC in IPCop Firewall
-
> It's a 2-4k increase depending on which pages I browse.
Do you mean 2 to 4 kilobytes of memory? That's a very small increase.
Also which memory column is showing the increase?
> I had top running in a ssh session while browsing.
Then you should be able to highlight the relevant lines and copy them.
> Posting hard numbers is probably meaningless as it's somewhat dependant on...
2008-03-29 14:40:51 UTC in IPCop Firewall
-
Also if it is not a problem for you then please could you close this bug report as I don't have permission to do so.
Thanks.
2008-03-29 01:06:01 UTC in IPCop Firewall
-
Thanks for the bug report, but it's almost certainly not a memory leak in httpd.
Linux uses spare RAM as a disk cache. If you want details on the memory usage with and without buffers and cache run 'free -t' at the command line. If you want information about how much memory httpd is using then run 'top' and look at the various memory columns.
Searching the archives of the ipcop-user...
2008-03-29 01:03:18 UTC in IPCop Firewall
