I just noticed the following error after booting my system
iptables v1.4.4: Couldn't load target `input_EXT':/usr/lib/xtables/libipt_input_EXT.so: cannot open shared object file: No such file or directory
I cannot find any reference on this on the forum or else on the internet. Is this a major problem or just a notification that can be ingnored, and how can it be solved? Thanks.
Hey I have a question… Did you set up IPtables manually?
I’ve had something similar and I’ve found this post couple of years ago.
I hope it helps…
Here is the link
No. I only used Yast to edit the external zone. Obviously iptables is looking for a non-existing module, and I have no clue how to solve this.
sorry, but I have to ask you another question? Can you go online and does error show up in a boot time when all that fancy stuff is written on the screen or it’s present when you log into the system?
The reason why I’m asking you this is because some stuff in a boottime is displayed as an error but is being restored later while system is up.
If you can’t go online, you can see more info about iptables in manpages
Also you can try to do some of following.
In terminal login as root and then
/usr/sbin/iptables-save -t sometablename
#or you can use
Then reboot system and see if it works… Sometimes the error message doesn’t have to be related to a certain module but to some wrong procedure or call.
That’s all I can help you with… Perhaps someone has some more experience with this and will be able to help you more. I hope I’m not too assailant. Tony
Yes, I can go online. And yes, the error shows up at boot time. Using runlevel 3, I see the errormessages as last just before the login prompt.
tabletpc:~ # iptables-save
# Generated by iptables-save v1.4.4 on Sat Jan 23 01:00:24 2010
:input_ext - [0:0]
-A INPUT -i eth0 -j input_ext
-A INPUT -i wlan0 -j input_ext
# Completed on Sat Jan 23 01:00:24 2010
I don’t know, but given this output, does not finding the module input_ext mean trouble, i.e. does it harm the integrity of the firewall?
Rebooting after iptables --flush doesn’t solve the matter.
That’s all I can help you with…