Question
problem with iptables and ubuntu Ubuntu 13.10
- Posted on March 21, 2014
Asked by benoit.asserin
Hello all,
When trying to check iptables i’m getting this message: $iptables -L ERROR: could not insert ‘ip_tables’: Operation not permitted iptables v1.4.18: can’t initialize iptables table `filter’: Table does not exist (do you need to insmod?) Perhaps iptables or your kernel needs to be upgraded.
some more info: $lsb_release -d Description: Ubuntu 13.10
$lsmod Module Size Used by floppy 69370 0
my system uname is: $uname -r 3.11.0-18-generic
I did a: $sudo apt-get install linux-image-$(uname -r) Which make the /lib/modules/3.11.0-18-generic folders
rebooted and still the same.
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Want to learn more? Join the DigitalOcean Community!
Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.
Same problem after an upgrade.
Solved with:
@Max Polk, thanks a lot for your answer. <br>I just found the problem. <br> <br>$uname -a <br>3.11.0-18-generic #32-Ubuntu SMP Tue Feb 18 21:11:14 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux <br> <br>but <br> <br>$file /sbin/init <br>sbin/init: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), <br> <br>I was running a 64bit kernel on a 32bit system…tssss… Always check your basic stuff first… <br> <br>Once shutdown and hypervisor setup to run in 32bit and the right kernel, i was ok and running again flawless. <br> <br>Thanks a lot to you all. <br>
I had this problem earlier. In my case, the kernel I elected to use when booting my droplet was an older kernel. Then I performed various updates which included installing a newer kernel. When you do that, all the libraries are setup for the new kernel, but digital ocean doesn’t use the new kernel, it uses the one you specify in your droplet configuration. <br> <br>When I bumped the droplet configuration kernel up to the same one I had just updated to in my instance, iptables began to work again. <br> <br>Now here’s the key. When you get this working again, setup your kernel package to be “fixed” and not auto-upgradable. If you decide to upgrade, in the future, you have to do both, pick the droplet configuration kernel version you like, and then in your package manager, remove the old and pick the “fixed” package that exactly corresponds.