[
https://issues.apache.org/jira/browse/KAFKA-6496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16349848#comment-16349848
]
Ronald van de Kuil commented on KAFKA-6496:
-------------------------------------------
I did a test with Kafka behind a physical router with a NAT port forward.
With wireshark I saw it return the internal IP address of the kafka server as
part of the handshake. I did not get the communication to work. That was some
months ago.
The floating IP to fixed iP assignment is like NAT.
That is why I expect the same for accessing kafka from a place outside the
openstack tenant is similar. The IP address that will be returned during the
handshake will be the internal IP adresses which will not be resolvable.
> NAT and Kafka
> -------------
>
> Key: KAFKA-6496
> URL: https://issues.apache.org/jira/browse/KAFKA-6496
> Project: Kafka
> Issue Type: Improvement
> Affects Versions: 1.0.0
> Reporter: Ronald van de Kuil
> Priority: Critical
>
> Hi,
> As far as I know Kafka itself does not support NAT based on a test that I did
> with my physical router.
>
> I can imagine that a real use case exists where NAT is desirable. For
> example, an OpenStack installation where Kafka hides behind floating ip
> addresses.
>
> Are there any plans, to make Kafka NAT friendly?
>
> Best Regards,
> Ronald
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
