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.
how can we help you with so little information?? what do you even mean by "nothing happens"? does "iptables -L" list ruels? what are you expecting to happen? do you realise that the "#" symbol is not meant to actaully be typed by yourself, it's meant to signify a prompt, and if you type it will turn your command into a comment and be ignored.
with redhat there must be at list one saved iptables rule so the iptables service could start.
try doing the following:
Code:
iptables -A INPUT -i lo -j ACCEPT
service iptables save
service iptables start
this will add one rule and should start iptables.
as acid_kewpie said, you should at least mention some info about your dist. and what meant by no thig happened, I can realize what you mean by no thing happened because i ran into the same thing in the past.
mose probably the # mark is your problem. The # is not and should not be a part of your command. it simply is there to act as a konsole prompt to make your reading easier and to let you know that it is a command you can type.
so basically, if you type
Code:
service iptables start
or
Code:
/etc/init.d/iptables start
your iptables should start with no doubt. still if you are unsure try
this doens't sound like a problem at all. run "service iptables start" ni a console and copy and paste the entire thing here, including data before and after the command being executed.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.