Bug#282195: kernel-image-2.6.9-1-686: ip_tables seem to be broken
On Tue, Nov 30, 2004 at 11:01:59PM +0100, Marco Nenciarini wrote:
> On Tue, Nov 30, 2004 at 01:42:10PM +0900, Horms wrote:
> > On Sat, Nov 20, 2004 at 01:06:17PM +0100, Marco Nenciarini wrote:
> > > Package: kernel-image-2.6.9-1-686
> > > Version: 2.6.9-2
> > > Severity: critical
> > > Justification: breaks unrelated software
> > >
> > > On my system (used as router for my local lan) ipmasq don't work anymore
> > > after i've installed latest kernel. If I start with 2.6.8 kernel all work ok.
> > >
> > > This is the output of ipmasq command:
> >
> > Very strange. I am not able to reproduce that problem at all.
> >
> > > FATAL: Error inserting ip_tables (/lib/modules/2.6.9-1-686/kernel/net/ipv4/netfilter/ip_tables.ko): Device or resource busy
> > > iptables v1.2.11: can't initialize iptables table `nat': iptables who? (do you need to insmod?)
> >
> > [snip]
> >
> > perhaps
> > modprobe iptable_nat
> >
> > Here is a list of the iptables modules that were inserted on my system.
> >
> > ipt_LOG 7008 4
> > iptable_mangle 2688 0
> > iptable_filter 2816 1
> > iptable_nat 26632 0
> > ip_conntrack 47892 1 iptable_nat
> > ip_tables 18560 4 ipt_LOG,iptable_mangle,iptable_filter,iptable_nat
> >
>
> All these modules require ip_tables module, but if I try to load it,
> the only result is
>
> FATAL: Error inserting ip_tables (/lib/modules/2.6.9-1-686/kernel/net/ipv4/netfilter/ip_tables.ko): Device or resource busy
>
> This is a very strange error, but I am pretty sure that the package is
> installed correctly (I have reinstalled it more and more times).
>
> On kernel 2.6.8-1-686 iptables works correctly.
>
> The only thing I can suppose is some strange incompatibility with my
> hardware (not the network card, hat is a very common rtl 8139 too).
That is unlikely, these modules don't touch hardware.
> Tell me if you need other logs or if you want I do some other tests.
I would guess that there is either some conflict with another module
(or something built into the kernel) or the module is already
in the kernel (module or otherwise).
What does lsmod look like?
--
Horms
Reply to: