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.

Introduction to Linux - A Hands on Guide

This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.

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?