This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
clearing_iptables [2023/05/08 04:30] – -grammar, condense bulleted points at bottom hogwild | clearing_iptables [2024/10/31 21:09] (current) – hogwild | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ===== Clearing iptables custom commands prior to re-applying new ones ===== | + | ===== Clearing iptables custom commands prior to applying new ones ===== |
- | Let's say, for example, | + | As an example, let's say that you wanted to use some custom iptables commands in a script, such as the firewall script. |
- | \\ | + | \\ You can remove previously-added iptables |
- | + | ||
- | You can remove | + | |
\\ | \\ | ||
Line 13: | Line 11: | ||
\\ | \\ | ||
- | This command here below will check what iptables **-A** (append) or **-I** (insert) have been used in the current Script/ | + | The commands |
+ | |||
+ | You might have created custom tables in which to use advanced iptables commands. This is usually | ||
+ | |||
+ | \\ Here are a few rules to remember when using these commands: | ||
\\ | \\ | ||
- | Remember that: | + | * First, you need to dereference the custom table from the built-in one, \\ using the above method. |
+ | * A table must then be emptied with the **-F** (Flush) switch/ | ||
+ | * Only then will you be allowed to remove the table by using the command: \\ " | ||
- | * You need to first dereference the custom table from the built-in one first (using the above approach). | + | \\ |
- | * A table must then be emptied with the **-F** (Flush) switch/ | + | |
- | * Only at this point will you be allowed to remove the table with the command: | + | |