This repository was archived by the owner on Jul 20, 2024. It is now read-only.
Use eth0 for output #52
Open
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.
The only requirement for NAT to work is a functional internet connection, so as the NAT EC2 instance is running on a public subnet, we don't actually need a EIP to get a public IP and therefore an internet connection. (Also they're a very limited resource to be required by a "cheap" NAT solution)
Update the SNAT scripting to use
eth0
for the upstream internet connection instead of deconfiguring it.I haven't tested DNAT port forwarding with this, but it should still work as it did before once an EIP is connected to the "floating"
eth1
interface as Linux's routing shouldn't care.Upgrading to this set of changes will break any system that expects to have an open port on the same IP as it sends from. The fix is to update the DNAT rules to use
eth0
instead ofeth1
.This depends on #51.