[ZBXNEXT-138] Cannot bind to multiple network interfaces (Debian bug #500148) Created: 2009 Oct 13  Updated: 2011 Dec 22  Resolved: 2010 Jun 03

Status: Closed
Project: ZABBIX FEATURE REQUESTS
Component/s: Agent (G), Proxy (P), Server (S)
Affects Version/s: None
Fix Version/s: 1.8.3

Type: Change Request Priority: Minor
Reporter: Christoph Haas Assignee: Aleksandrs Saveljevs
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Debian 5.0


 Description   

A Debian user has reported the following issue at the Debian bug tracker (http://bugs.debian.org/500148):

Zabbix agent (and possibly zabbix_server, but I havent checked this)
doesn't appear to be able to bind to multiple network interfaces.
It's either all (0.0.0.0) or just one.

I have tried using:

ListenIP=127.0.0.1,192.168.1.10,10.0.0.1

or

ListenIP=127.0.0.1 192.168.1.10 10.0.0.1

or

ListenIP=127.0.0.1
ListenIP=192.168.1.10
ListenIP=10.0.0.1

but with the latter try, it'll only bind to 10.0.0.1.

 Comments   
Comment by richlv [ 2009 Oct 13 ]

from the downstream report :
"One of the requirements for TCP/IP ports usage in a vserver is that the port isn't bound to 0.0.0.0 in the host, so you typically bind to only the IPs you are interested in. So I wanted to do a bind on the public IP and another one to the private IP."

Comment by Alexei Vladishev [ 2009 Nov 22 ]

I moved it to feature requests. I do not see any bug here.

Comment by Aleksandrs Saveljevs [ 2010 Jun 02 ]

Available in pre-1.8.3 in r12472.

Comment by Aleksandrs Saveljevs [ 2010 Jun 03 ]

If ListenIP configuration parameter is not specified, daemons crash.

Comment by Aleksandrs Saveljevs [ 2010 Jun 03 ]

Fixed in pre-1.8.3 in 12504.

Comment by Alexander Vladishev [ 2010 Jun 14 ]

Fixed compilation on Windows platforms in r12733.

Generated at Sat Apr 20 07:32:21 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.