On Thursday 07 February 2002 13:57, Juan Quintela wrote:
>>>>>> "richard" == richard <[EMAIL PROTECTED]> writes:
>
>richard> Hi Chuck if its any help the last kernel that did not cause this problem
>richard> was 2.4.17-2.. So maybe routing through the change notes might reveal
>richard> something. 2.4.17-2 works ok with iptables..
>richard> might give a kernel guru a clue ???
>
>The only change there was the quota support, humm, that also changed
>inodes, but netfilter don't use inodes at all :(
>
>/me thinking about that.
>
>Later, Juan.
>
The starange thing is, the filters still come up and function.
Even the binary rpm works just fine, execpt for the core that it
leaves in the root direcroy on boot, or in whatever directory I'm
in at the time I manually start the bastille-firewall service.
Curiously, If the bastille-firewall service is started, and I start
it again, iptables complains about the script, but does not dump
core:
[root@localhost chas]# service bastille-firewall start
iptables: libiptc/libip4tc.c:384: do_check: Assertion `h->info.valid_hooks == (1 << 0
| 1 << 3)' failed.
/sbin/bastille-netfilter: line 578: 513 Aborted ${IPTABLES} -t
mangle -F PREROUTING
Setting up IP spoofing protection... done.
Allowing traffic from trusted interfaces... done.
Setting up chains for public/internal interface traffic... done.
Setting up general rules... done.
Setting up outbound rules... done.
[root@localhost chas]# ls | grep core
[root@localhost chas]#
Like I said before, tell me what diagnostics to run, and I'll do it...
--
*Chuck*
