• When monitoring an alternate IP address, and the DHCP address changes, the monitoring fails and interface is marked offline.  Even though it is very much still online.

    Making a change to the alternate monitor IP address starts it working again and marks the interface online.

    Is this a bug?

    Kind of an interesting situation here:
    ISP has started giving me an address and gateway from a new range.  192.183.x.x.  The assigned gateway in that range (192.183.x.1) does not respond to ping.  But it is not the real gateway.  As shown by a trace route the real gateway is still the one from the previous range (50.53.x.1).  And it still responds to ping.  So using that as the alternate monitor IP.  But anytime the new IP address changes the monitoring fails until it's given a kick by changing the alternate monitor IP and back again.

  • I've got the same problem. The providers gateway does not accept ICMP packets, so i have to use an alternate monitor ip. :-(

    Does anyone got a workaround for it?

  • Rebel Alliance Developer Netgate

    If you use an alternate monitor IP that's out on the Internet somewhere it should work around those quirks.

    Setting an alternate monitor IP is the correct workaround for a gateway that does not respond to ping.

  • I use google DNS for the Monitor ip. It should be "out enough"  :)

    Still doesn't work. Every time i get a new IP, the interface is marked as offline, but it isn't.