Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
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.
So I'm in the process of trying to write some iptable rules. I'm not new to linux by any means, but I do need some help.
iptables -A forward -i eth0 -o eth2 -j accept
this is the rule I am trying to write to be able to get the traffic from eth0 to go out through eth2, I still have to write it to be able to allow it to come back in again, but the problem I am running into is that when I hit enter it gives me this:
iptables v1.3.5: Couldn't load target `accept':/lib/iptables/libipt_accept.so: cannot open shared object file: No such file or directory
Yes, I am logged in as the root account. There are no other accounts set up on this particular machine because I'm the only one with access to it. It might help to know that this is a virtual machine and not a physical machine.
You need to type "ACCEPT" (in all uppercase letters), not "accept". That's causing your error. Still, this command won't make any difference unless you've got your routes or relevant NAT rules set.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.