It's worth noting that --status-senders limits what IP addresses can send
updates on behalf of other IP addresses. It does not stop hosts from
sending updates from their own IP address, even if not listed in
--status-senders. So I could just set --status-senders=127.0.0.1 and it
should not stop me getting updates from any devices.
On 20 February 2015 at 09:45, Eli via Xymon <xymon at xymon.com> wrote:
---------- Forwarded message ----------
From: Eli <user-eeb3a3c6c848@xymon.invalid>
To: Torsten Richter <user-c862b499d9fa@xymon.invalid>
Cc: xymon at xymon.com
Date: Thu, 19 Feb 2015 15:45:45 -0700
Subject: Re: [Xymon] Blocking unwanted agents reporting
Thanks much that helpful. I wish I can block by host name. :)
Torsten Richter <user-c862b499d9fa@xymon.invalid> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Eli,
take a look at the manpage of xymond.
There are several command line options for this binary which control who
can send status messages, maintenance commands or admin commands to the
server.
In your case you might want to add something like
--status-senders=IP/MASK
to tasks.cfg into the [xymond] block to allow status updates only from
IP/MASK.
HTH
Torsten
On 19.02.2015 16:57, Eli via Xymon wrote:
- --
+---------------------------------------------------------+
| E-mail : user-c862b499d9fa@xymon.invalid |
| |
| Homepage: http://www.richter-it.net/ |
+---------------------------------------------------------+
Download my public key from:
http://gpg-keyserver.de/pks/lookup?search=0x899093AC&op=get
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
iEYEARECAAYFAlTmCtsACgkQ7DlmxomQk6xWEgCePYNSNc3IPASBFcJqvZaXD5yn
3yMAoLNWKvC7ps7gINSvpVwLR06HQKHp
=jH6r
-----END PGP SIGNATURE-----