the EXTERNAL listener should be EXTERNAL:SSL in production.
Hope this helps,
Tom Aley
thomas.a...@ibm.com
From: "周正虎"
To: users@kafka.apache.org
Date: 21/05/2018 23:59
Subject: Kafka behind NAT
We have kafka behind NAT with *only one broker*.
Let say we have intern
We have kafka behind NAT with *only one broker*.
Let say we have internal (A) and external (B) network.
When we try to reach the broker from external network (we use
bootstrap.servers parameter set to B address) then what is obvious the
broker responds with internal network's address (A) whi
Marcin,
The DNS seems to be your friend. /etc/hosts should be sufficient but it
might be an operational hassle.
–
Best regards,
Radek Gruchalski
ra...@gruchalski.com
On August 10, 2016 at 10:03:16 PM, Marcin (kan...@o2.pl) wrote:
We have kafka behind NAT with *only one broker*.
Let say we
We have kafka behind NAT with *only one broker*.
Let say we have internal (A) and external (B) network.
When we try to reach the broker from external network (we use
bootstrap.servers parameter set to B address) then what is obvious the
broker responds with internal network's address (A) whi
If it's the case that zookeeper can't access the brokers at their
advertised addresses (and it's just a guess---you could test it by
telnetting from zookeeper to your broker's externalip+port), you might be
able to get away with adding a route so that the traffic avoids going out
to your firewall.
Quick question,
so is there any way to set the advertised host name differently for the
zookeeper and clients?
Thanks,
Su
On Tue, Jul 7, 2015 at 5:33 PM, Su She wrote:
> Thank you Hawin and Mike for the answers.
>
> Having a public IP would be the easiest solution, but unfortunately, this
> i
Thank you Hawin and Mike for the answers.
Having a public IP would be the easiest solution, but unfortunately, this
is a lengthy process for me due to company security rules.
Since the zookeeper is behind the NAT, I guess it won't have access to the
external IP...so it seems like there isn't a st
can zookeeper access the broker through the public IP? advertised.host.name
is also what zookeeper uses to communicate to the broker, but if zookeeper
is inside the NAT it might not have a route via that external IP.
On Jul 7, 2015 2:10 PM, "Su She" wrote:
> Hello Everyone,
>
> I am in a tricky
Hi Su
Maybe you can try to use own public IP if you want to set host name to
public IP.
Or you can use private IP with load balancing configuration.
Thanks.
Best regards
Hawin
On Tue, Jul 7, 2015 at 11:09 AM, Su She wrote:
> Hello Everyone,
>
> I am in a tricky situation.
>
> I am running Ka
Hello Everyone,
I am in a tricky situation.
I am running Kafka (downloaded via binary) on a private cloud behind NAT. I
am hoping to send messages to the broker from outside the cloud. Everything
else seems to be working fine, I can send messages from instances within
the private cloud. The insta
10 matches
Mail list logo
