redirects: make sure one-to-one mapping is used for the port range #9
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 linux kernel provides NF_NAT_RANGE_PROTO_OFFSET flag (netfilter nf_nat_core.c for reference), to make sure that when port ranges are used, then if possible, one-to-one mapping is maintained between external port range and internal port range. But for that flag to be set, iptables extension libxt_DNAT.c requires that base port is also passed along with the port range. Therefore, make sure that if the conditions are right, then we also pass a base port to iptables. One such example where this behaviour is expected is TR-181 data model's Device.NAT.PortMapping. object's InternalPort attribute.