net: Add set/getsockopt options compatible with iptables. #7989
Conversation
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
Signed-off-by: Zhe Weng <[email protected]>
xiaoxiang781216
approved these changes
Dec 28, 2022
This was referenced Dec 29, 2022
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
Implemented our own
IPT_SO_SET_REPLACEoption for setsockopt andIPT_SO_GET_INFO/IPT_SO_GET_ENTRIESoptions for getsockopt, which are compatible with iptables.Currently used for NAT.
Impact
Add a method for user space to control kernel NAT/firewall(maybe).
Testing
Manually tested with our implementation of iptables (compatible version) in apps (apache/nuttx-apps#1479).