> On 04 Sep 2015, at 16:06, Zachary McGibbon <zachary.mcgib...@gmail.com> wrote: > > 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.
That sounds like a lot of problems in case your routing fails. Similar to how DNS might cause troubles when depending on the FQDN, and not putting real ip addresses in your host definitions. > > 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? I’m not sure which problem you are trying to solve. Maybe a little picture could help understand the issue and the proposted solution of yours? Kind regards, Michael -- Michael Friedrich, DI (FH) Senior Developer NETWAYS GmbH | Deutschherrnstr. 15-19 | D-90429 Nuernberg Tel: +49 911 92885-0 | Fax: +49 911 92885-77 GF: Julian Hein, Bernd Erk | AG Nuernberg HRB18461 http://www.netways.de | michael.friedr...@netways.de ** OSBConf 2015 - September - osbconf.org ** ** OSMC 2015 - November - netways.de/osmc ** _______________________________________________ icinga-users mailing list icinga-users@lists.icinga.org https://lists.icinga.org/mailman/listinfo/icinga-users
