iptables can't initialize iptables table `filter': Bad file descriptor
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
ts7000:~# iptables -L
iptables v1.3.6: can't initialize iptables table `filter': Bad file
descriptor
Perhaps iptables or your kernel needs to be upgraded.
This is the first time I have used iptables. Is there something else that needs to be done before I can run the above command?
I am constrained to use the kernel (although I can reconfigure it and rebuild it), as it was custom-configured for my platform, but I tried to manually build and install version 1.4.9.1 of iptables and received the same error. I also read that the "Bad file descriptor" error can sometimes mean file system corruption, so I ran fsck on the file system and it is clean.
If anyone can suggest things to try to resolve this problem, I'd be very grateful.
As an update, someone suggested that there might be an issue with EABI vs. OABI on the ARM platform, so I reconfigured iptables with --enable-static and --disable-dynamic, since I think that there is not an issue as long as iptables doesn't try to build linking to the EABI-built kernel libraries. After rebuilding, I tried to run "iptables -L" again and this time received a different error:
"getsockopt failed strangely: invalid argument"
As before, if anyone has any suggestions on how I might resolve this error to get iptables working, I'd be very appreciative.
As an update, someone suggested that there might be an issue with EABI vs. OABI on the ARM platform, so I reconfigured iptables with --enable-static and --disable-dynamic, since I think that there is not an issue as long as iptables doesn't try to build linking to the EABI-built kernel libraries. After rebuilding, I tried to run "iptables -L" again and this time received a different error:
"getsockopt failed strangely: invalid argument"
As before, if anyone has any suggestions on how I might resolve this error to get iptables working, I'd be very appreciative.
Thanks,
Don
Hi,
I have met the same problem, would you please let me know if you have solution finally?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.