[
https://issues.apache.org/jira/browse/FLINK-15911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17305874#comment-17305874
]
Xintong Song commented on FLINK-15911:
--------------------------------------
bq. 1、all 0 has some security risks.
Could you explain in specific what security risks are caused by listening to
0.0.0.0? Are all of your Yarn NM's exposed via external IP addressed? Shouldn't
it be the responsibility of something like a firewall to prevent unwanted
accesses?
bq. 2、i think add new config, like network.allow.listen.0, default true. if
false, we shold use other address
The question is which "other address" should be used?
> Flink does not work over NAT
> ----------------------------
>
> Key: FLINK-15911
> URL: https://issues.apache.org/jira/browse/FLINK-15911
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Coordination
> Affects Versions: 1.10.0
> Reporter: Till Rohrmann
> Assignee: Xintong Song
> Priority: Blocker
> Labels: pull-request-available, usability
> Fix For: 1.11.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently, it is not possible to run Flink over network address translation.
> The problem is that the Flink processes do not allow to specify separate bind
> and external ports. Moreover, the {{TaskManager}} tries to resolve the given
> {{taskmanager.host}} which might not be resolvable. This breaks NAT or docker
> setups where the external address is not resolvable from within the
> container/internal network.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
