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.
will simply drop everything coming in. Cookies and such are stored locally and run through your browser so will be fine anyway. Have a read through "man iptables" which lists much more options, as you may want to allow specific traffic from a certain location if you wish to be able to ssh into your machine from another box a home network, for example.
So to run this at start up do you put it in a script some place? Or are the changes permenant at the command line?
If so how do you return everything to the way it was before the changes?
Don't like to change things with out knowning a recovery from the changes.
You may already have a firewall script running, to find out type this as root:
iptables -L
Usually you will have a script e.g. /etc/rc.d/init.d/rc.firewall which is started each time you boot. I don't know if Caldera uses the SysV init scripts or not, but if so then there will be run-level directories which have symlinks to the startup scripts e.g.
/etc/rc.d/rc5.d/S99firewall -> /etc/rc.d/init.d/rc.firewall
If you drop all incoming packets, then you won't be able to receive any replies to your outgoing traffic. You need something more like this as a start:
Quote:
Originally posted by aaa iptables -P INPUT DROP
iptables -A INPUT -m state --state ESTABLISHED, RELATED -j ACCEPT
That should block all outside connections.
Note that one of those rules is setting the default policy using -P (in red) and not an actual rule in the chain (-A), so make sure to enter those exactly as listed in aaa's post. Also take a look at the following guide as it will give you some basics on iptables and the various options:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.