Monitored Host

I am seeing radios disabling their WLAN where I have set up Monitored Host.

Pretty sure its not doing what its supposed to.

What I am expecting is for the AP to send pings to a target on an interval I SET.

Then it should not take action until a threshold is met.

Like here is how I think its supposed to work.
Ping host. On INTERVAL. Here it would be 60 seconds.
Attempts I would guess relates to HOW MANY FAILURES IN A ROW before shutting down the WLAN.

So if I were to set these parameters to 60 and 5.
I would expect 5 CONTINUOUS minutes of missed pings.
At the 6th minute where the host didn’t ping. THEN I WOULD EXPECT THE RADIO TO DISABLE.

This doesn’t seem to be the case at all…
Here is what my router sees.

09:17:53 firewall,info Monitored Host forward: in:bridge out:ether1-WAN1, connection-state:new src-mac b4:a2:5c:e8:99:7c, proto ICMP (type 8, code 0), 192.168.101.252->96.xxx.xxx.xx8, len 84
09:17:53 firewall,info Monitored Host forward: in:bridge out:ether1-WAN1, connection-state:new src-mac b4:a2:5c:e8:99:7c, proto ICMP (type 8, code 0), 192.168.101.252->96.xxx.xxx.xx8, len 84
09:17:54 firewall,info Monitored Host forward: in:bridge out:ether1-WAN1, connection-state:established,snat src-mac b4:a2:5c:e8:99:7c, proto ICMP (type 8, code 0), 192.168.101.252->96.xxx.xxx.xx8, NAT (192.168.101.252->96.xxx.xxx.xx4)->96.xxx.xxx.xx8, len 84
09:17:54 firewall,info Monitored Host forward: in:bridge out:ether1-WAN1, connection-state:established,snat src-mac b4:a2:5c:e8:99:7c, proto ICMP (type 8, code 0), 192.168.101.252->96.xxx.xxx.xx8, NAT (192.168.101.252->96.xxx.xxx.xx4)->96.xxx.xxx.xx8, len 84
09:17:55 firewall,info Monitored Host forward: in:bridge out:ether1-WAN1, connection-state:established,snat src-mac b4:a2:5c:e8:99:7c, proto ICMP (type 8, code 0), 192.168.101.252->96.xxx.xxx.xx8, NAT (192.168.101.252->96.xxx.xxx.xx4)->96.xxx.xxx.xx8, len 84
09:17:55 firewall,info Monitored Host forward: in:bridge out:ether1-WAN1, connection-state:established,snat src-mac b4:a2:5c:e8:99:7c, proto ICMP (type 8, code 0), 192.168.101.252->96.xxx.xxx.xx8, NAT (192.168.101.252->96.xxx.xxx.xx4)->96.xxx.xxx.xx8, len 84
09:17:56 firewall,info Monitored Host forward: in:bridge out:ether1-WAN1, connection-state:established,snat src-mac b4:a2:5c:e8:99:7c, proto ICMP (type 8, code 0), 192.168.101.252->96.xxx.xxx.xx8, NAT (192.168.101.252->96.xxx.xxx.xx4)->96.xxx.xxx.xx8, len 84
09:17:56 firewall,info Monitored Host forward: in:bridge out:ether1-WAN1, connection-state:established,snat src-mac b4:a2:5c:e8:99:7c, proto ICMP (type 8, code 0), 192.168.101.252->96.xxx.xxx.xx8, NAT (192.168.101.252->96.xxx.xxx.xx4)->96.xxx.xxx.xx8, len 84
09:17:57 firewall,info Monitored Host forward: in:bridge out:ether1-WAN1, connection-state:established,snat src-mac b4:a2:5c:e8:99:7c, proto ICMP (type 8, code 0), 192.168.101.252->96.xxx.xxx.xx8, NAT (192.168.101.252->96.xxx.xxx.xx4)->96.xxx.xxx.xx8, len 84
09:17:57 firewall,info Monitored Host forward: in:bridge out:ether1-WAN1, connection-state:established,snat src-mac b4:a2:5c:e8:99:7c, proto ICMP (type 8, code 0), 192.168.101.252->96.xxx.xxx.xx8, NAT (192.168.101.252->96.xxx.xxx.xx4)->96.xxx.xxx.xx8, len 84

So I am guessing my idea of how this works is wrong.

Could someone explain what exactly its supposed to do and when. Then I can make parameters that fit my needs

Monitored Host parameter explanation :

Host => IP Address or hostname that should be reachable for this WLAN to be active

Interval (Duration in Seconds) => Its an Interval in seconds where device (AP) will check the reachability of the IPaddress/hostname mentioned in the “Host” Section at regular interval

Attempts (1-20) => Its a number of attempts via ping to check the reachability of monitored host configured.

For Example :
If somebody set the monitored host parameter as follow :’

Host : 8.8.8.8
Interval : 60 seconds
Attempts : 5

Now Device Behavior will like this :

  • At an interval of every 60 seconds (1 minute) Device will check the reachability of the host 8.8.8.8 via ping request/reply

  • Number of Ping request = Number of attempts configured

  • Now Device will send 5 ping request (Attempts) at an interval of 1 seconds and verify the reachability by the reply message

  • If got the reply from host it will mark host is reachable and WLAN will be in Up state

  • Scenario 1 : Host reachable

  • If host is reachable it will again wait for 60 seconds and then repeat the above process in loop until host is reachable

  • Scenario 2: Host become unreachable

  • If host is unreachable then it will make the WLAN down immediately after attempting the 5 ping request for reachability check

  • Since host is unreachable so device will not receive any reply from host, therefore immediately after attempting the 5 ping check it will make WLAN down

  • Device will keep check the host reachability after making the WLAN down , but the duration or interval this time will be half of the configured value in Interval section

  • Now at an interval of every 30 seconds it will check the Host reachability

  • NOTE : Once Host become reachable, device will follow the scenario 1 again

What is the fail threshold?
What is the timeout length?

All 5 pings need to make it?

Thought I might bump this up.

I have one access point in a group that I am thinking about how to route its VLANs.

I was thinking about using monitored host to shut down a few SSIDs when the main ISP goes down. So only one SSID would stay on when the system only has the back up.

Need to know how many pings have to miss before the SSID shuts off and how it comes back.