Using Firestarter ... Can I Add/Drop rules from a terminal prompt?
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.
Using Firestarter ... Can I Add/Drop rules from a terminal prompt?
I'm very impressed with Firestarter, but would like to add and drop some rules depending on what I'm doing. My actual goal is to attach scripts containing the rules related to certain programs to the starting and stopping of those programs.
Using an 'iptables -A INPUT ...' command, I can see the rule is displayed in an 'INPUT' chain, but when I add the rule using Firestarter's GUI, It gets added to an 'INBOUND' chain. (I suppose the 'INBOUND' chain is a user defined chain initialized by Firestarter. Problem is, my 'iptables -A INPUT ...' command does not work, and using the GUI does. I tried changing my command to 'iptables -A INBOUND ...', but that generates an error.
you should be able to change iptables whever irrespective of firestarter, but last time i used it, firestarter uses it's own fixed startup script, so each reload of firestarter will nuke any external changes you made to it. no biggy though, i'm sure.
as far as the error, i'd have to assume that you're using the wrong syntax... what IS the error? you could always make that change in firestarter, and diff the before and after versions of firstarters config to see what's actually been changed and what the iptables command it actually uses is. After all, that's all it is... just a command wrapper.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.