Report this

What is the reason for this report?

problem with iptables and ubuntu Ubuntu 13.10

Posted on March 21, 2014

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.

did you install ipatbles?? or varified you have it on your OS? <br> <br>did you read this tut: <br> <br>https://www.digitalocean.com/community/articles/how-to-set-up-a-firewall-using-ip-tables-on-ubuntu-12-04 <br> <br>if you have done all, then do you use root as your user or custom user? <br> <br>if custom user, then make sure the user has privileges to execute commands.

@FMCB <br> <br>Yes iptables is installed, which makes me be able to see this error and i’m using root to execute them. <br> <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.

The developer cloud

Scale up as you grow — whether you're running one virtual machine or ten thousand.

Get started for free

Sign up and get $200 in credit for your first 60 days with DigitalOcean.*

*This promotional offer applies to new accounts only.