Luis R Finotti wrote:
Dear Rogério and all,
Rogério Brito wrote:
On Jun 04 2005, Luis R Finotti wrote:
After that iptables is not working anymore. Here is a the errors
that I get:
(...)
Before you try more drastic changes (like installing a new kernel -- see
below), can you try running "depmod" as root?
If you have problems trying to insert the module after that, then, please
report back.
I still get the same error messages...
The problem loading the ip_conntrack module you are seeing is
quite possibly due to a mismatch between the installations of the kernel
that you had.
Hmm... It is funny that it also does not work with the 386 kernel...
Although I am not sure I ever tried to ran iptables with that kernel
before, but I thought I did.
Another possibility would be to install another completely different
version of the kernel (like, say, 2.6.11, which has many improvements
over
2.6.8, BTW).
I am a little afraid to plunge into installing myself (not from a .deb).
But I might get some free time soon... :-) I would prefer to fix this
problem though... Could a purge/reinstall the (same) kernel solve this?
(...)
OK, I tried that (purge/reinstall) and it did not work.
If it helps, and any one is willing to look at it, I posted some logs here:
http://www.math.ohio-state.edu/~finotti/iptables/
* iptables.sh and iptables2.sh are two sets of rules that I've tried.
(Both with the errors from the original post.)
* dmesg.out is the output of dmesg.
* log.messages is part of /var/log/messages
* depmod.ip_conntrack.error is the result of "depmod -v | grep ip_conntrack"
Does any one have any suggestion?
Best to all,
Luis
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
