So far, we've got Shorewall running smoothly and we've learned how to work with port access, both with macros that Shorewall has provided and with our own macros that we've made ourselves. Now it's time to learn what to do when things don't go according to plan. In this article, we'll take a look at Shorewall logging and how to interpret it to help troubleshoot problems.
If you've been following along from the beginning, then you've gotten Shorewall installed, running, and have worked with some of the basic rules and macros. In this article, we'll get into what we have to do when we have to deal with ports that aren't included in the Shorewall defaults.
The configuration of Shorewall continues. After reading this, you should have a better understanding of working with Shorewall's rules file and utilizing the default macros that Shorewall makes available to you.
If you've gotten this far, you've should have successfully gotten Shorewall installed on your slice. Now we'll learn how to configure it, providing a powerful and simple mechanism for managing your slice's firewall.
So you're ready to start installing applications on your slice and, rightly, you want to make sure that you're nice and secure. IPTables, right? Well, sure, but the only thing is that IPTables can be a messy beast to deal with. That's where Shorewall comes in.
Shorewall is the common name for the Shoreline firewall, a “wrapper” for IPTables that will handle all the heavy lifting for you. This article will get you started, showing you how to get Shorewall on your system.