New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

direct-tcpip driven gateways didn't actually use the gateway #776

Closed
bitprophet opened this Issue Nov 15, 2012 · 0 comments

Comments

Projects
None yet
1 participant
@bitprophet
Member

bitprophet commented Nov 15, 2012

Due to an incredibly boneheaded mistake, the gateway connection used the gateway info as the host key but still made a connection to the real target and cached that instead.

So the gatewaying behavior worked -- two cached connections were involved with one passed in as the socket and so on -- but the end result was gatewaying to the target via itself, not via the configured gateway.

This issue description is already about 10x longer than the fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment