Xymon Mailing List Archive search

Xymon Server Multihomed

3 messages in this thread

list Denis · Mon, 17 Oct 2011 14:54:45 +0200 (CEST) ·
Hi,

I'm searching an easier way to configure my xymon 4.3.5 server other than specifying @IP at each test necessary in hosts.cfg.
My configuration is with two IPs. 
I'm on Debian squeeze.
One for the real physical IP and another with an alias (which i try to use with my xymon server).
Even if i set a DNS name, a reverse DNS, force the IP in xymonserver.cfg some tests like ssh are not working.
My configuration of hosts.cfgwas clear and simple until today, i don't want to complexify it with @1.2.3.4 on all tests necessary.

Is there another way to configure it ?
At least is it possible to apply it for a complete line or a group ?

Kind regards,

Denis
list Denis · Thu, 20 Oct 2011 10:36:31 +0200 ·
Hi,

I'm searching an easier way to configure my xymon 4.3.5 server other than specifying @IP at each test necessary in hosts.cfg.
My configuration is with two IPs. I'm on Debian squeeze.
One for the real physical IP and another with an alias (which i try to use with my xymon server).
Even if i set a DNS name, a reverse DNS, force the IP in xymonserver.cfg some tests like ssh are not working.
My configuration of hosts.cfgwas clear and simple until today, i don't want to complexify it with @1.2.3.4 on all tests necessary.

Is there another way to configure it ?
At least is it possible to apply it for a complete line or a group ?

Kind regards,

Denis
list Jeremy Laidman · Fri, 21 Oct 2011 11:40:09 +1100 ·
quoted from Denis
On Mon, Oct 17, 2011 at 11:54 PM, Denis <user-41ff130ea0ee@xymon.invalid> wrote:
I'm searching an easier way to configure my xymon 4.3.5 server other than specifying @IP at each test necessary in hosts.cfg.
I think there are only two ways to do this: append "@IP" to every
test; and define FPING to be "xymonping --source=IP".  Obviously, the
latter only works with ping/conn tests, and I don't think it gets used
if "--ping" is on the xymonnet command-line (in tasks.cfg).  From
reading the source code, I can't see any other mechanism for
overriding the O/S-provided address.

There's probably a way to do this using policy routing.  If a policy
route is selected, and the "src" hint is defined in the route table
entry, then it will be used for the source IP address.  A route table
entry can be selected based on a "mark" applied by netfilter
(iptables).  You can mark a packet based on things like the PID, UID
and GID of the process, and the process command-line.  It sounds like
a lot of fun, but it's not something I'd want on my networks.

J