[re-send due to sf.net foo] 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. This is part of system-service abstraction. Big shops do it. It should probably be transmitted not as a "flag" or "argument" to the API but as an exported environmental variable to the sub-process. The most common situation where this is a perquisite is a mission critical Nagios deployment in an enterprise environment where Nagios runs in an Active-Standby server configuration. The present Active server possesses the High-Availability Layer 3 IP address of the cluster. All firewalls, ACLs, policies in the network expect to see Monitoring traffic sourced from the shared Layer 3 address. 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 ~BAS > the same physical network (trough aliases like eth0:1): Can I set the > IP-source-address used for running the network-related-checks in one > point? If yes, where please :-) > > Thanks in advance, Ingo -- Brian A. Seklecki <[EMAIL PROTECTED]> Collaborative Fusion, Inc. ------------------------------------------------------------------------- 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@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