Re: nftables 0.9.3, sets with concatentation

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Stefan Hartmann <stefanh@xxxxxxxxxxxx> wrote:
> I have successfully migrated from a cisco IOS router to a new GNU/Linux
> Debian box with nftables 0.9.3.
> 
> At now I am trying to simplify the configuration with sets.
> E.g.
> table ip FILTER4 {
> 	set s4_ICMP-RELATED {
> 		type icmp_type
> 		elements = { destination-unreachable,
> 			     time-exceeded }
> 
> and using this set
> ...
> chain ACL4-IN_IF2 {
> 		ct state invalid log prefix "NFT: FILTER4/ACL4-IN_IF2: ct invalid: " drop
> 		ct state established,related accept
> 		icmp type @s4_ICMP-RELATED accept
> 		...
> 
> This works perfectly with sets without concatenation.
> 
> 
> For the sake of a well-arranged ruleset,
> it would be nice to have a concatenated set like
> 	set s4_MISC-SERVICES {
> 		type inet_proto . inet_service
> 		elements = { udp . 69, tcp . 23 ]
> 
> and then use this set like
> 	ip daddr $IP4_IF2 . dport @s4_MISC-SERVICES accept

try
 ... IF2 . th dport ..

(th == transport header).



[Index of Archives]     [Linux Netfilter Development]     [Linux Kernel Networking Development]     [Netem]     [Berkeley Packet Filter]     [Linux Kernel Development]     [Advanced Routing & Traffice Control]     [Bugtraq]

  Powered by Linux