blog:linux:connection_tracking_1_modules_and_hooks
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| blog:linux:connection_tracking_1_modules_and_hooks [2023-08-15] – improved/fixed some statements, typos Andrej Stender | blog:linux:connection_tracking_1_modules_and_hooks [2025-10-16] (current) – INT_MAX is signed and not unsigned Andrej Stender | ||
|---|---|---|---|
| Line 106: | Line 106: | ||
| Another two hook functions get registered with MAX priority in the //Input// | Another two hook functions get registered with MAX priority in the //Input// | ||
| hook and in the // | hook and in the // | ||
| - | MAX means the highest possible | + | MAX means the highest possible |
| priority will be traversed as the very last one within the Netfilter hook and no | priority will be traversed as the very last one within the Netfilter hook and no | ||
| other hook function can get registered to be traversed after it. Those two hook functions | other hook function can get registered to be traversed after it. Those two hook functions | ||
| Line 283: | Line 283: | ||
| - | //published 2021-04-04//, | + | //published 2021-04-04//, |
blog/linux/connection_tracking_1_modules_and_hooks.1692107994.txt.gz · Last modified: 2023-08-15 by Andrej Stender
