Netonix Forums

confirmed not working as expected on my bench.

current sequence of operations:

WD timeout -> port disabled for (time) seconds.

(time) timeout -> port enabled for (interval) seconds.

(interval) timeout -> port disabled for (time) seconds.

This is the exact issue, is a loop, it start with a delay defined by startup time, later make Ping every x period, goes down the time defined in down time and start again powering on the device for startup time.

Repeating this forever and ever until Ping is restored.

I'll see what I can do for the next release.

Eric Stern wrote:I'll see what I can do for the next release.

Using ping watchdog as you prescribed may be one approach but perhaps something like UniFi Wireless' "Uplink Connectivity Monitor" could be useful. Basically, the way it works in UniFi, if a predefined upstream IP, such as the default gateway or last hop before the internet goes down, then it disables the SSIDs on all UAPs. Of course that is not exactly how one would want it to act on a WISP network but rather have the option to drop PoE.

Maybe you could have it alongside the "follow link state" feature request where when one port drops link, another defined port is also dropped, either by link state or by PoE cut.

thanks for the suggestion...

Hello.

Think in other idea, to power up some equipment it other equipment fail, for example, you have in the same tower two APs, one powered down and the other powered UP, if the powered UP AP fail, for some reason, you can enable another AP.

This is only a "NOT" before the rule.

"Do not power up this port if IP X.Y.W.Z is responding to ping"

How very strange...come on this forum looking for exactly this and it's right at the top.

We've been doing this on solar sites for redundant backhaul links using digital-loggers (would still use them if they supported gigabit) or Mikrotik scripts. I don't the idea of some "central" controlling software to be honest....

On a linux box (or windoze + plink) or tower mikrotik I guess a watchdog script could be written to login to the Netonix via SSH and switch on/off AP's as required?

Any news with this?

CuninganReset wrote:Any news with this?

This is not possible with the current watch dog rules, to my knowledge anyway.

This would require a rework of the watchdog feature which is something that has been thrown around - Making a more advanced type of watchdog similar to a script or advanced logic triggers.

This might be something we will do in the future but is not on the immediate list of things to do.

Right now we are trying to finalize v1.4.7 which is needed to change the current default firmware used in production which is currently an OLD v1.4.2 and we are forced to ship WS-26 with v1.4.7rcXX.

Next on the list to do in v1.4.8rc1 is ring protection and get ready for the new line of products that use a different switch core making way for SFP+ down the road and will require a different firmware than the current ones use.

You could script this desired function on a linux box and have it login to the switch and turn on and off POE based on your own criteria. Using other machines to make changes to the switch config has been explained on several threads.

Ok thanks for considering it, I am not in a hurry and can wait.
Thanks for all!