[ZBX-3256] icmp* simple check SourceIP problem Created: 2010 Dec 02  Updated: 2017 May 30  Resolved: 2010 Dec 27

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Server (S)
Affects Version/s: 1.8.3
Fix Version/s: 1.8.4rc3

Type: Incident report Priority: Major
Reporter: Laky paxon Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Hello,

if using "SourceIP" in zabbix server configuration, there exist problem with icmp* simple check, because using fping to icmp ping with -S argument as SourceIP, but official last fping 2.4b2 version didn't have this feature.

After patching fping with patch or using fping version 2.4b2_to-ipv6 [ http://unfix.org/projects/ipv6/fping-2.4b2_to-ipv6.tar.gz ], there is exist -I argument for source interface/ip. But is needed to patch .../zabbix-1.8.3/src/libs/zbxicmpping/icmpping.c on line 64:

  • i += zbx_snprintf(params + i, sizeof(/source_ip/params) - i, " -S%s ", CONFIG_SOURCE_IP);
    + i += zbx_snprintf(params + i, sizeof(/source_ip/params) - i, " -I%s ", CONFIG_SOURCE_IP);

or exist "other version" ??



 Comments   
Comment by Laky paxon [ 2010 Dec 23 ]

ad: fping in debian 5 : fping_2.4b2-to-ipv6-15_i386.deb uses argument "-S" as source address. I using zabbix on slackware13.1 with compiled zabbix and fping from sources founded on official and community websites.

I thing, is not so "bug" - its good to write to documentation about problem of fping versions&SourceIP problem.

Comment by Aleksandrs Saveljevs [ 2010 Dec 23 ]

Added automatic detection of fping's command line option for specifying source IP address (if any).

This feature is available in development branch svn://svn.zabbix.com/branches/dev/ZBX-2394.

Comment by Aleksandrs Saveljevs [ 2010 Dec 27 ]

Merged into pre-1.8.4 in r16416.

Comment by Aleksandrs Saveljevs [ 2010 Dec 27 ]

Improvement to fping option detection are filed under ZBXNEXT-593.

Generated at Sun May 25 11:04:56 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.