Element timeouts - Revision history

Nevola: complete description of timeout and expires in a set

2020-04-06T08:06:29Z

complete description of timeout and expires in a set

@@ Line 1: / Line 1: @@
-The '''set''' infrastructure support establishing timeouts. A given '''set element''' which is given a '''timeout''' will be deleted from the '''set''' after the timeout expires.
+The '''set''' infrastructure support establishing timeouts. A given timed '''set element''' has 2 attributes:
 Example, with per-element timeout:
@@ Line 17: / Line 20: @@
 </source>
-'''timeout''' and '''expires''' parameters cannot be modified in this case. The element should be recreated again if you need to reset them. In order to be able to reset it from packet path among other things you can use this feature by [[Updating sets from the packet path]].
+'''timeout''' and '''expires''' parameters cannot be modified in this case. The element should be recreated again if you need to reset them.

Nevola at 17:52, 5 April 2020

2020-04-05T17:52:38Z

← Older revision		Revision as of 17:52, 5 April 2020
Line 1:		Line 1:
	The set infrastructure support establishing timeouts. A given set element which is given a timeout will be deleted from the set after the timeout expires.		The '''set''' infrastructure support establishing timeouts. A given '''set element''' which is given a '''timeout''' will be deleted from the '''set''' after the timeout expires.

	Example, with per-element timeout:		Example, with per-element timeout:

	<source lang="bash">		<source lang="bash">
	% nft add table inet ~~filter~~		% nft add table inet myfilter
	% nft add set inet ~~filter~~ myset {type ipv4_addr\; flags timeout\; }		% nft add set inet myfilter myset {type ipv4_addr\; flags timeout\; }
	% nft add element inet ~~filter~~ myset {10.0.0.1 timeout 10s }		% nft add element inet myfilter myset {10.0.0.1 timeout 10s }
	% nft list ruleset		% nft list ruleset
	table inet ~~filter~~ {		table inet myfilter {
	set myset {		set myset {
	type ipv4_addr		type ipv4_addr
Line 17:		Line 17:
	</source>		</source>

	~~Among~~ other things you can use this feature by [[Updating sets from the packet path]].		'''timeout''' and '''expires''' parameters cannot be modified in this case. The element should be recreated again if you need to reset them. In order to be able to reset it from packet path among other things you can use this feature by [[Updating sets from the packet path]].

Arturo: add pointer to Updating sets from the packet path

2017-01-05T10:57:50Z

add pointer to Updating sets from the packet path

← Older revision		Revision as of 10:57, 5 January 2017
Line 16:		Line 16:
	}		}
	</source>		</source>

			Among other things you can use this feature by [[Updating sets from the packet path]].

Arturo: Create page with a very basic syntax reference to element timeouts.

2016-10-28T07:20:10Z

Create page with a very basic syntax reference to element timeouts.

New page

The set infrastructure support establishing timeouts. A given set element which is given a timeout will be deleted from the set after the timeout expires.

Example, with per-element timeout:

<source lang="bash">
% nft add table inet filter
% nft add set inet filter myset {type ipv4_addr\; flags timeout\; }
% nft add element inet filter myset {10.0.0.1 timeout 10s }
% nft list ruleset
table inet filter {
set myset {
type ipv4_addr
flags timeout
elements = { 10.0.0.1 timeout 10s expires 8s}
}
}
</source>