I added an issue to Jira regarding this with an included patch on trunk:

https://issues.apache.org/jira/browse/KAFKA-675

This saves us the hassle of firewalling Kafka in our environments which is
a definite win.  We have a patched 0.7.2 version which works fine for us.



On Fri, Dec 14, 2012 at 2:32 PM, Matan Amir <matan.amir@voxer.com> wrote:

> While hostname is useful to direct traffic via Zookeeper to specific
> hostname/IP it does not cause Kafka to only listen on that IP.  It will
> still bind to all interfaces on the box.
>
> I guess the solution is to firewall it for now...
>
>
> On Thu, Dec 13, 2012 at 10:16 PM, Jun Rao <junrao@gmail.com> wrote:
>
>> In  0.7, you can set hostname in the broker config.
>>
>> Thanks,
>>
>> Jun
>>
>> On Thu, Dec 13, 2012 at 11:50 AM, Matan Amir <matan.amir@voxer.com>
>> wrote:
>>
>> > Hi All,
>> >
>> > I've scanned the code a little (0.7.2) but couldn't find a parameter to
>> > force the broker to bind to a specific network interface rather than
>> listen
>> > on all.  Was this added to 0.8?  I was hoping for something like ZK's
>> > clientPortAddress configuration parameter.
>> >
>> > Cheers,
>> > Matan
>> >
>>
>
>