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

Setting host as Monitored IP makes it unreachable?

Scheduled Pinned Locked Moved Routing and Multi WAN
4 Posts 3 Posters 766 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.
  • J
    jobe
    last edited by Feb 19, 2018, 5:25 PM

    Hello,
    in my setup I have a network interface dedicated to reach a single host on a different network. I set that interface configuring the IP and its related gateway, then I put the remote host IP in "monitor IP" field. With this setup, that host was not reachable from my network, neither with ping or other protocols like FTP; moreover, the firewall itself was not able to reach that monitor IP, so the gateway was marked as unreachable.
    I tried then to disable the monitor IP feature for that gateway, and that host became reachable from my network, firewall included. Is it an expected behavior? Or I misconfigured something?

    1 Reply Last reply Reply Quote 0
    • J
      johnpoz LAYER 8 Global Moderator
      last edited by Feb 19, 2018, 6:17 PM

      Well if the host doesn't answer ping then monitor would think the gateway is down and nothing would work.  If you want to be able to monitor it has to answer ping and out of the box monitor will send a zero sized ping which some devices don't like and will not answer.  You can adjust that.

      An intelligent man is sometimes forced to be drunk to spend time with his fools
      If you get confused: Listen to the Music Play
      Please don't Chat/PM me for help, unless mod related
      SG-4860 24.11 | Lab VMs 2.7.2, 24.11

      1 Reply Last reply Reply Quote 0
      • J
        jobe
        last edited by Feb 26, 2018, 12:37 PM Feb 26, 2018, 12:34 PM

        I did not manage to get this working…Trying to ping with a zero sized ping (ping -s 0) gave the same behaviour, everything works until I set the remote host IP in "monitor IP" field.

        In my environment I have a master-slave pfSense setup, with CARPs configured...maybe this causes the issue? [Previously I had another issue related to CARPs, solved with the help of this forum: https://forum.pfsense.org/index.php?topic=143072.0]

        Here are the IPs involved:
        10.2.14.251 - Physical IP address of master pfSense
        10.2.14.253 - CARP address of the master/slave cluster
        10.2.14.254 - Remote non-pingable gateway
        10.2.14.212 - Remote host pingable IP. It becomes not pingable when it is set as "monitor IP" for .254 gateway.

        Executing some tcpdumps [tcpdump -i igb5 host 10.2.14.212] , I noticed that with "Gateway monitoring" disabled, the system has this behaviour:

        There are only interactions between CARP IP and and remote host IP.

        With monitoring enabled, here is the result:

        There are many attempts from the physical IP addres, that do not receive any answers from .212 .

        Moreover, I noticed that this line is added to routing table when monitoring is enabled:

        10.2.14.212	10.2.14.254	UGHS	2139	1500	igb5
        

        Do you have any clue?

        1 Reply Last reply Reply Quote 0
        • L
          luckman212 LAYER 8
          last edited by Jan 15, 2022, 2:27 PM

          This may help:

          https://github.com/pfsense/pfsense/pull/4551

          1 Reply Last reply Reply Quote 0
          • First post
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
            [[user:consent.lead]]
            [[user:consent.not_received]]