Nagios Support Forum

Provided your nagios host can communicate with a device on another subnet, it should have no issues with nrpe. The main difficulty is going to be firewalls between them, if you have any transparent proxy servers that may be breaking ssl connections, or if there are issues with openssl on your target arm device OR the nagios machine. Based on your previous comment of check_nrpe -H localhost, it would seem that plugins compiled on the arm system and run locally are happy to communicate. However the connection from nagios to remote system does not want to work via ssl. Please return the output of the following command on both machines:
Also when your nagios machine is on the 192 subnet, please return the output of from both machines:

sreinhardt wrote:Provided your nagios host can communicate with a device on another subnet, it should have no issues with nrpe. The main difficulty is going to be firewalls between them, if you have any transparent proxy servers that may be breaking ssl connections, or if there are issues with openssl on your target arm device OR the nagios machine. Based on your previous comment of check_nrpe -H localhost, it would seem that plugins compiled on the arm system and run locally are happy to communicate. However the connection from nagios to remote system does not want to work via ssl. Please return the output of the following command on both machines:

Code: Select all

which openssl

Also when your nagios machine is on the 192 subnet, please return the output of from both machines:

Code: Select all

route

I'm sorry,I can't get your point.Do you mean that the reason why i can't monitor the arm is because the firewalls when they are in different subnet ?But my monitor host and the arm are both without the firewall, does the gateway have a firewall? Please forgive my stupid and help me !
Thank you!

If you had them on separate sets of private address space you would need something to properly route the traffic, this was likely the problem.