Error message when entering iptables command (table does not exist)
I have been trying to install Spotify, but when logging in I get a message saying I have an error 101
. This appears to be related to either my proxy settings or to my firewall. Following instructions from another similar question I've entered the following into a terminal iptables -L
and it has returned this message which sounds a bit worrying!
FATAL: Error inserting ip_tables (/lib/modules/3.5.0-25-generic/kernel/net/ipv4/netfilter/ip_tables.ko): Operation not permitted
iptables v1.4.12: can't initialize iptables table `filter': Table does not exist (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
Any idea's what the solution is to both my apparent lack of firewall and to solving my ability to get into Spotify?
I think you needed to use the sudo command and the error message is just a badly worded way of telling you that you don't have the correct permission to run the command you wanted to run.
Here is a link to some instructions on how to get a firewall going with iptables.
I know this is an old thread, but maybe this will help someone. The error message reflects that there are missing kernel files. You can rectify this on any version of Ubuntu with the following command:
sudo apt-get install linux-image-$(uname -r)
The iptables
command administers your 'firewall' (or in technical terms: packet filter). It needs more permissions than a normal user has. So entering the command as a normal user leads to the error message you posted. If you prepend sudo
and enter your password at the following prompt you'll get root permission for this single command. So sudo iptables -L
writes output without error message:
> sudo iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
However I doubt that this will help to find a solution for your spotify problem. It might be better to ask another question and insert the full error message in that question. Maybe we can help you better there.