932
edits
Changes
m
Revising better practices.
<table border="1" cellspacing="0" cellpadding="5" >
<tr><td>'''Tip'''</td><td>'''Explanation'''</td></tr>
<tr> <td>'''Always start with back-up the default iptables settings'''</td><td>When you install Iptables iptables in CentOS it already has some rules predefined.<br/>You will always get Make a copy of the default file that creates these rules (including the ones that allow communication with your other machines). This way you can always restore them to have a functional machine even if you restart the iptables servicecompletely mess up your rules.</td></tr>
<tr> <td>'''Place your iptables commands (i.e. Rules) within a bash script'''</td><td>If you need to reset iptables, then you can run a shell script to quickly re-apply rules to save time.</td></tr>
<tr> <td>'''Don't Panic if disconnected from a VM'''</td><td> Some of the traffic between your host and VirtManager goes through IPtables.<br> When you mess with IPtables rules on the host, you might end up losing the console connection to the virtual machines.<br>'''Don't worry, iptables rules the virtual machines are still running and you can still use themonce you re-establish your connection'''.</td></tr>
<tr> <td>'''If your most recent iptables Rule messes up your system'''</td><td>'''Reload the default rules'''. You can do that by restarting the iptables and libvirtd services (you can also do that at the beginning of your shell script).<br>Then '''run your script with all the working iptables commands''' that you already finished.<br>'''Return to work on creating the rule that didn't work'''.</td></tr>
</table>
===Creating Customized Chains===