How to set the sourceaddress for all checks?

[Marc Powell]

> -----Original Message-----
> From: Brian A. Seklecki [mailto:bseklecki at collaborativefusion.com]
> Sent: Tuesday, June 26, 2007 9:50 AM
> To: Ingo Lantschner; Marc Powell; Hari Sekhon; Michael Silver
> Cc: nagios-users nagios-users
> Subject: Re: [Nagios-users] How to set the sourceaddress for all
checks?
> 
> On Thu, 2007-06-14 at 16:30 +0200, Ingo Lantschner wrote:
> > Hi,
> > if I  am running Nagios on a host with more than one IP address on
> 
> I've discussed, many times in the past, the need to be able to
> explicitly define the sources address that check plugins transmit from
> (TCP, ICMP, UDP at the very least) as part of the Nagios API.

Have you been discussing it in the proper forum of
nagiosplug-devel at lists.sourceforge.net? The plugins are a separate
project from nagios. Though many of the developers might hang out here,
they might not pay much attention. I'm sure they'd be happy to look at
any provided patches if you had the time.
 
> These are simple one-line changes does in setsockopt(2) and
> getaddrinfo(2)
> 
> http://netbsd.gw.com/cgi-bin/man-cgi?setsockopt++NetBSD-current
> http://netbsd.gw.com/cgi-bin/man-cgi?getaddrinfo++NetBSD-current

Being a hacker and not a coder, I don't have much to say about this
other than the current implementation is consistent and easy to support.
A non-trivial number of plugins are written in other languages that this
wouldn't apply to (PERL, shell, etc). 

--
Marc


-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null