[
https://issues.apache.org/jira/browse/SSHD-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15933228#comment-15933228
]
Tony Bussieres commented on SSHD-656:
-------------------------------------
[~jonnyzzz]
I've ran in the same situation. I needed to get the real IP of the client that
connect to a server behind a load balancer that supports the PROXY protocol
server.
I have found this JIRA and decided to implement it.
Feel free to use / integrate :
https://gist.github.com/codingtony/a8684c9ffa08ad56899f94d3b6c2a040
If can find some time, I can give a try to add it as a module.
> Support The PROXY protocol
> --------------------------
>
> Key: SSHD-656
> URL: https://issues.apache.org/jira/browse/SSHD-656
> Project: MINA SSHD
> Issue Type: New Feature
> Reporter: Eugene Petrenko
> Priority: Minor
>
> Load Balancing and other higher availability services are included between
> client and SSHD server and works on TCP level. This makes an actual client
> address shown in the SSHD server to be a load balancer address, not a real
> client address. This makes it hard to use SSHD for multi-node production
> scenarios.
>
> There are several ways to solve the issue.
> The first one is to include complex TCP routing to have specific packets
> delivered correctly. This is too hard to setup
> It looks like using {{The PROXY Protocol}} is the possible, easy and more or
> less standard way to pass actual client/server addresses to the server over
> TCP. The protocol is implemented by a number of TCP-based servers
> (including nginx, Amazon Load Balancer, Apache, github enterprise, see the
> link below for details)
> Protocol specification is here
> http://www.haproxy.org/download/1.6/doc/proxy-protocol.txt
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
