• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login
Netgate Discussion Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login

Firewall rule for NRPEv2?

Scheduled Pinned Locked Moved pfSense Packages
6 Posts 2 Posters 2.6k Views
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • A
    awsiemieniec
    last edited by Jan 19, 2012, 11:04 PM Jan 19, 2012, 11:02 PM

    I've installed the NRPEv2 package on my 2.0.1 version of pfSense.  I've setup the default checks, set the port to 5666 and set the two IPs.  My Nagios box can't communicate with pfS.  On the Nagios side I get:

    CHECK_NRPE: Received 0 bytes from daemon. Check the remote server logs for error messages.

    Do I need to manually set some sort of rule to allow this communication in/out of pfS?

    The binding IP address is on the same network as the Nagios server (10.1.1.0/24)

    Thanks
    AWS

    1 Reply Last reply Reply Quote 0
    • M
      marcelloc
      last edited by Jan 20, 2012, 3:35 AM

      Try to disable ssl communications between nagions and pfsense as well create a rule to permit traffic on port 5666.

      It worked for me.

      Treinamentos de Elite: http://sys-squad.com

      Help a community developer! ;D

      1 Reply Last reply Reply Quote 0
      • A
        awsiemieniec
        last edited by Jan 20, 2012, 3:35 PM Jan 20, 2012, 3:28 PM

        Can you proof my rule to allow 5666 traffic?

        Firewall / Rules / LAN:
        ID, Proto, …
        <empty>TCP Nagios * pfS 5666 * none   Pass NRPE

        above, "Nagios" is aliased to the local IP of the Nagios server, "pfS" is aliased to the LAN IP of pfSense.  My Nagios box is on the same subnet as this pfS box.  They talk via the LAN side.

        AWS</empty>

        1 Reply Last reply Reply Quote 0
        • A
          awsiemieniec
          last edited by Jan 20, 2012, 3:41 PM

          I enabled logging of the rule and I can see it is passing through:
          **Jan 20 07:40:01 LAN   10.1.1.4:46066   10.1.1.254:5666 TCP:S

          AWS**

          1 Reply Last reply Reply Quote 0
          • M
            marcelloc
            last edited by Jan 20, 2012, 3:45 PM

            Source nagios_ip
            Sourceport any

            Destination lan-address
            Destinationport 5666

            Treinamentos de Elite: http://sys-squad.com

            Help a community developer! ;D

            1 Reply Last reply Reply Quote 0
            • A
              awsiemieniec
              last edited by Jan 20, 2012, 4:59 PM

              Found the solution, from ScottWilkerson of Nagios (thread http://support.nagios.com/forum/viewtopic.php?f=6&t=4728&p=20437#p20437)

              Had to remove the $ARG2$ values on the Nagios side (plus use the firewall opening for port 5666)

              Thanks all for your suggestions/help.

              AWS

              1 Reply Last reply Reply Quote 0
              6 out of 6
              • First post
                6/6
                Last post
              Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
                This community forum collects and processes your personal information.
                consent.not_received