Operations at ruleset level - Revision history

Pablo: fix incorrect flush ruleset

2023-07-31T08:17:40Z

fix incorrect flush ruleset

← Older revision		Revision as of 08:17, 31 July 2023
Line 38:		Line 38:
	You can combine these two commands above to backup your ruleset:		You can combine these two commands above to backup your ruleset:
	<source lang="bash">		<source lang="bash">
	% echo "~~nft~~ flush ruleset" > backup.nft		% echo "flush ruleset" > backup.nft
	% nft list ruleset >> backup.nft		% nft list ruleset >> backup.nft
	</source>		</source>

Fw: xml/json export is not longer supported.

2020-11-23T16:15:39Z

xml/json export is not longer supported.

← Older revision		Revision as of 16:15, 23 November 2020
Line 45:		Line 45:
	% nft -f backup.nft		% nft -f backup.nft
	</source>		</source>
	== ~~In XML or~~ JSON format ==		== Listing in JSON format ==

	You can also export your ruleset in ~~XML or~~ JSON format.		You can also export your ruleset in JSON format, just pass the
			'--json' option:

	~~In this case, you have to issue the 'export' command:~~
	<source lang="bash">		<source lang="bash">
	% nft ~~export xml >~~ ruleset~~.xml~~		% nft --json list ruleset > ruleset.json
	~~% nft export json~~ > ruleset.json
	</source>		</source>

	~~Note that the export operation output all the tables, of all families (ip, ip6, inet, arp, bridge).~~

	~~We are working now in the 'import' operation for XML and JSON.~~

	== See also ==		== See also ==

Arturo: add see also section

2018-02-01T10:37:56Z

add see also section

← Older revision		Revision as of 10:37, 1 February 2018
Line 58:		Line 58:

	We are working now in the 'import' operation for XML and JSON.		We are working now in the 'import' operation for XML and JSON.

			== See also ==

			Some related information you may want to read:

			* [[Atomic rule replacement]]
			* [[Scripting]]

Pablo: Created page with "== Using native nft syntax == Linux Kernel 3.18 includes some improvements regarding the available operations to manage your ruleset as a whole. === listing === Listing the..."

2016-07-13T17:48:49Z

Created page with "== Using native nft syntax == Linux Kernel 3.18 includes some improvements regarding the available operations to manage your ruleset as a whole. === listing === Listing the..."

New page

== Using native nft syntax ==

Linux Kernel 3.18 includes some improvements regarding the available operations to manage your ruleset as a whole.

=== listing ===

Listing the complete ruleset:
<source lang="bash">
% nft list ruleset
</source>

Listing the ruleset per family:
<source lang="bash">
% nft list ruleset arp
% nft list ruleset ip
% nft list ruleset ip6
% nft list ruleset bridge
% nft list ruleset inet
</source>
These commands will print all tables/chains/sets/rules of the given family.

=== flushing ===

In addition, you can also flush (erase, delete, wipe) the complete ruleset:
<source lang="bash">
% nft flush ruleset
</source>
Also per family:
<source lang="bash">
% nft flush ruleset arp
% nft flush ruleset ip
% nft flush ruleset ip6
% nft flush ruleset bridge
% nft flush ruleset inet
</source>
=== backup/restore ===

You can combine these two commands above to backup your ruleset:
<source lang="bash">
% echo "nft flush ruleset" > backup.nft
% nft list ruleset >> backup.nft
</source>
And load it [[Atomic_rule_replacement|atomically]]:
<source lang="bash">
% nft -f backup.nft
</source>
== In XML or JSON format ==

You can also export your ruleset in XML or JSON format.

In this case, you have to issue the 'export' command:
<source lang="bash">
% nft export xml > ruleset.xml
% nft export json > ruleset.json
</source>

Note that the export operation output all the tables, of all families (ip, ip6, inet, arp, bridge).

We are working now in the 'import' operation for XML and JSON.