<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Suggestion - Multiple Monitor IPs]]></title><description><![CDATA[<p dir="auto">Greetings all, I apologize if this exists already, I have searched the forums.</p>
<p dir="auto">Would it be useful to have more than one IP address used for monitoring connectivity on an interface? For use in load balancing or in particular fail over scenarios; just in case the machine which is at the address that is being used for monitoring goes down/has ping blocked or other; either way loses connectivity resulting in essentially a false positive regarding loss of connectivity.</p>
<p dir="auto">So essentially the method used to check connectivity (not high latency at this stage &amp; excuse the extreme crudity) would go from;</p>
<p dir="auto">If no ping response from ip0, loop ping response check on this interface X times then trigger failover.</p>
<p dir="auto">to</p>
<p dir="auto">If no ping response on ip0 AND no ping response on ip1 on this interface, loop ping response X times then trigger failover.</p>
<p dir="auto">Am I missing something or could this well have it's uses?</p>
]]></description><link>https://forum.netgate.com/topic/48351/suggestion-multiple-monitor-ips</link><generator>RSS for Node</generator><lastBuildDate>Mon, 20 Apr 2026 07:27:08 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/48351.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 06 Sep 2012 14:50:14 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Suggestion - Multiple Monitor IPs on Thu, 06 Sep 2012 15:49:44 GMT]]></title><description><![CDATA[<p dir="auto">Your best bet would probably be to contact the author of apinger (util used by pfSense to monitor gw up/down status)</p>
]]></description><link>https://forum.netgate.com/post/354658</link><guid isPermaLink="true">https://forum.netgate.com/post/354658</guid><dc:creator><![CDATA[dhatz]]></dc:creator><pubDate>Thu, 06 Sep 2012 15:49:44 GMT</pubDate></item></channel></rss>