Add REMOTE_PORT from connection to environment #25
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.
I've added REMOTE_PORT into export of variable to the environment.
It is very useful if you transparent redirect connection from multiple
destinations to one service. (for example every outgoing SMTP connect
should go to 10.0.0.1)
If you want to process the connection from a script behind xinetd and
want to know the original destination you have to parse the output of
'/proc/net/nf_conntrack' which is hard if you want to assign at least
two connection from the same host to the same service. If you want to
make something while the connection is open you need to know REMOTE_HOST
and REMOTE_PORT.