fix(vm): enable NFT_LOG kernel module for nftables bypass detection#1391
Merged
Conversation
The nftables log statement requires CONFIG_NFT_LOG, which was not included in the VM guest kernel config. Without it, nft rejects rules containing the log keyword with "No such file or directory".
russellb
requested review from
a team,
derekwaynecarr,
maxamillion and
mrunalp
as code owners
Collaborator
|
/ok to test f16f5d6 |
drew
approved these changes
May 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
CONFIG_NFT_LOG=yto the VM kernel config fragment so that nftableslogexpressions work inside the guest kernelnftrejects rulesets containinglogwith "No such file or directory" because the kernel lacks thenft_logmodulevm-runtimekernel must be rebuilt with this config before log-based bypass detection worksTest plan
FROM_SOURCE=1 mise run vm:setupand verifiedCONFIG_NFT_LOG=yin the resulting.configmise run gateway:vmusing the locally built kernellogexpressions load without error (previously failed with "No such file or directory")dmesginside the VM guest after triggering a direct connection bypassrelease-vm-kernelworkflow produces a kernel with NFT_LOG support (needed for CI and downloaded runtimes)🤖 Generated with Claude Code