If you want to use different interfaces with the same security protocol, you can specify listener names. You can then also configure different security properties for internal/external if you need.
listeners=INTERNAL://1.x.x.x:9092,EXTERNAL://172.x.x.x:9093 advertised.listeners=INTERNAL://1.x.x.x:9092,EXTERNAL://172.x.x.x:9093 listener.security.protocol.map=INTERNAL:SSL,EXTERNAL:SSL inter.broker.listener.name=INTERNAL On Wed, May 31, 2017 at 6:22 PM, Raghav <raghavas...@gmail.com> wrote: > Hello Darshan > > Have you tried SSL://0.0.0.0:9093 ? > > Rajani had suggested something similar to me a week back while I was > trying to get a ACL based setup. > > Thanks. > > On Wed, May 31, 2017 at 8:58 AM, Darshan <purandare.dars...@gmail.com> > wrote: > >> Hi >> >> Our Kafka broker has two IPs on two different interfaces. >> >> eth0 has 172.x.x.x for external leg >> eth1 has 1.x.x.x for internal leg >> >> >> Kafka Producer is on 172.x.x.x subnet, and Kafka Consumer is on 1.x.x.x >> subnet. >> >> If we use advertised.listeners=SSL://172.x.x.x:9093, then Producer can >> producer the message, but Consumer cannot receive the message. >> >> What value should we use for advertised.listeners so that Producer can >> write and Consumers can read ? >> >> Thanks. >> > > > > -- > Raghav >
