Mikhail Sosonkin created NIFI-3506:
--------------------------------------
Summary: Issues with site-to-site setup.
Key: NIFI-3506
URL: https://issues.apache.org/jira/browse/NIFI-3506
Project: Apache NiFi
Issue Type: Improvement
Components: Core Framework
Reporter: Mikhail Sosonkin
I tried setting up a site-to-site transfer using remote ports and faced with
several issues because the two NiFi instances were firewalled off from each
other. SSH was the only thing allowed through so, I wanted to use a SOCKS proxy
via an SSH tunnel.
1 - Proxy settings didn't seem to take affect or wanted to talk using SOCKS.
2 - Trying to use port forwarding eventually worked but was difficult because:
a) The HTTP connection from Site A to Site B went thought the SSH forward,
however Site B reported the local port and Site A would try to connect to that
and fail. So I had to change local nifi port of Site B to match the forwarded
port number.
b) Site B reported it's local host name to Site A. Site A would try to use
that and fail because the name would not resolve. Problem solved by updating
/etc/hosts file to force localhost resolution.
This isn't ideal and would be a lot better if the dynamic port forwarding would
work.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
