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.
I'm new to firestarter 1.01 and have a quick question. I'd like to control access to my server by turning ports off or on. For instance, I may want to allow ftp access from any external destination for a few hours and then be able to turn off access to port 22 completely. I can't seem to find a way to make policies for ports in this way. Am I just overlooking something?
I'm guessing that I am overlooking something seeing as how this is a very basic need for firewall configuration... but I can't find a way to do it. I don't use windows, so I can't speak to firestarer used in that os.
As far as I know, iptables doesn't have time based rules (firestarter is basically a front for iptables).
My suggestion would be to have two sets of rules, one with the port restricted and other policies implemented. Then set them up in a cron job, or using at, and have them switch when you need.
Or, just close / open the ports by manually adding / removing an iptables rule (again with a scheduled cron job or at).
Actually, I wasn't looking for time-based functionality; I was just giving an example of how I may want to turn (manually) ports on or off. I did find the port specifier though, FINALLY. Now FS is working well.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.