This repository has been archived by the owner on Jul 20, 2024. It is now read-only.
Fix NAT not working 2022-07 #51
Open
Conversation
This file contains 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
This was referenced Jul 26, 2022
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
At some point in the past, reverse path protection was enabled for Amazon Linux 2 AMIs, which causes the host to silently drop all NAT traffic.
My investigation of this issue also uncovered the requirement to disable source/destination checks on the ENIs attached to the NAT box.
This pull request adds patches to brute-force disable reverse path protection and brute-force enable source/destination checks.
This is probably overkill to actually fix the issues, but it works.