Skip to content
Snippets Groups Projects
Select Git revision
  • 1a94e38d254b3622d5d53f74b3b716b0fcab0ba8
  • openEuler-1.0-LTS default protected
  • openEuler-22.09
  • OLK-5.10
  • openEuler-22.03-LTS
  • openEuler-22.03-LTS-Ascend
  • master
  • openEuler-22.03-LTS-LoongArch-NW
  • openEuler-22.09-HCK
  • openEuler-20.03-LTS-SP3
  • openEuler-21.09
  • openEuler-21.03
  • openEuler-20.09
  • 4.19.90-2210.5.0
  • 5.10.0-123.0.0
  • 5.10.0-60.63.0
  • 5.10.0-60.62.0
  • 4.19.90-2210.4.0
  • 5.10.0-121.0.0
  • 5.10.0-60.61.0
  • 4.19.90-2210.3.0
  • 5.10.0-60.60.0
  • 5.10.0-120.0.0
  • 5.10.0-60.59.0
  • 5.10.0-119.0.0
  • 4.19.90-2210.2.0
  • 4.19.90-2210.1.0
  • 5.10.0-118.0.0
  • 5.10.0-106.19.0
  • 5.10.0-60.58.0
  • 4.19.90-2209.6.0
  • 5.10.0-106.18.0
  • 5.10.0-106.17.0
33 results

22b970264

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    Pablo Neira Ayuso authored
    This new attribute allows us to uniquely identify a rule in transaction.
    Robots may trigger an insertion followed by deletion in a batch, in that
    scenario we still don't have a public rule handle that we can use to
    delete the rule. This is similar to the NFTA_SET_ID attribute that
    allows us to refer to an anonymous set from a batch.
    
    Signed-off-by: default avatarPablo Neira Ayuso <pablo@netfilter.org>
    1a94e38d
    History
    Name Last commit Last update