[Nagiosplug-devel] [ nagiosplug-Patches-777416 ] check_ping for IPv6

SourceForge.net noreply at sourceforge.net
Fri Jul 25 08:53:04 CEST 2003


Patches item #777416, was opened at 2003-07-25 01:32
Message generated for change (Settings changed) made by undrgrid
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=397599&aid=777416&group_id=29880

Category: Enhancement
Group: None
>Status: Closed
>Resolution: Rejected
Priority: 3
Submitted By: Hendra (ardhen)
Assigned to: Jeremy T. Bouse (undrgrid)
Summary: check_ping for IPv6

Initial Comment:
Hi,

This is a patch for "check_ping.c" to support IPv6.

This patch works for nagios-plugins-1.3.1 (tarball). And 
tested under BSD.

You may need to define check_ping6 into Nagios's 
checkcommands.cfg







----------------------------------------------------------------------

>Comment By: Jeremy T. Bouse (undrgrid)
Date: 2003-07-25 08:52

Message:
Logged In: YES 
user_id=10485

Upon examination of the patch supplied there were no changes
that aren't already in the current CVS HEAD revision. Also
the code was very un-portable as the IPv6 command is hard
coded into it whereas the current CVS HEAD tests along with
the IPv4 ping command in the configure script. CVS HEAD also
has -4 (--use-ipv4) and -6 (--use-ipv6) to specify IPv4 or
IPv6 as the new resolver function in CVS HEAD resolves to
both IPv6 and IPv4 hostnames as provided by DNS.

----------------------------------------------------------------------

Comment By: Jeremy T. Bouse (undrgrid)
Date: 2003-07-25 08:39

Message:
Logged In: YES 
user_id=10485

As the one that's already coded the AF-independent code in
the CVS tree I will look at the patch to see if there is
anything not already in the code that might be useful. Also
if you want to submit patches in the future I would
recommend reading the Developers Guide
[http://nagiosplug.sourceforge.net/developer-guidelines.html]
as patches should be applied against the CVS HEAD not the
release. The code in CVS HEAD is very different from the
1.3.1 release and thus the patch itself is fairly unlikely
to be able to be applied as is.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=397599&aid=777416&group_id=29880




More information about the Devel mailing list