xt_unregiste...ble_pre_exit(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

okay so bestie, welcome to the xt_unregiste...ble_pre_exit(9) page from the Kernel API Manual β€” yes, that truncated title is the whole vibe, iykyk πŸ’…

πŸŽ€ NAME πŸŽ€

xt_unregister_table_pre_exit β€” pre-shutdown unregister of a table. yup, that's the entire assignment: pre-shutdown unregister of a table, and it ate. πŸ’–

✨ SYNOPSIS ✨

here's the exact signature, no cap:

void xt_unregister_table_pre_exit (struct net *net , u8 af , const char
       *name );

πŸ’… ARGUMENTS πŸ’…

three args, let's go:

  • net β€” network namespace 🌐
  • af β€” address family (e.g., NFPROTO_IPV4, NFPROTO_IPV6) 🧚
  • name β€” name of the table to unregister πŸŽ€

🌸 DESCRIPTION 🌸

okay so what does it actually do? It unregisters the specified netfilter table from the given network namespace, and it also unregisters the hooks from netfilter core: no new packets will be processed. literally no new packets, bestie 😭πŸ”₯

This must be called prior to xt_unregister_table_exit from the pernet .pre_exit callback. After this call, the table is no longer visible to the get/setsockopt path. In case of rmmod, the module exit path must have called xt_unregister_template prior to unregistering pernet ops to prevent re-instantiation of the table. periodt. πŸ’…

See also: xt_unregister_table_exit πŸ‘‘

πŸ¦‹ SEE ALSO πŸ¦‹

Kernel file ./net/netfilter/x_tables.c plus these iconic little references:


mwah πŸ’‹ this page comes from ./net/netfilter, is dated October 2026, and answers to xt_unregiste...ble_pre_exit(9) β€” bye bestie, go unregister responsibly 🫢✨

πŸ“¦ where this page comes from