I'm looking for a way to setup Icinga checks to run from one Icinga server via a second ISP.
Currently, I'm doing this with a second Icinga server that has specific routes setup in the routing table and then returns the results to the main server with NSCA. What I'm looking to do is to have this all one one Icinga server. I guess what I would need would be some kind of TCP wrapper to run before a check command and change the default route for that specific process and then still return the result properly back to Icinga. Of course there is the option of adding a route before running the check command, but this wouldn't work because I am running the same check on my local LAN as well, for example checking the availability of our web site or DNS from outside our network. Has anyone else done anything like this before? Thanks - Zachary
_______________________________________________ icinga-users mailing list icinga-users@lists.icinga.org https://lists.icinga.org/mailman/listinfo/icinga-users