Watchdogd - Hardware Watchdog
-
That section of the page only shows up when you're running a factory image on a platform where a supported watchdog is detected. So if you see the option, it's available on that hardware.
-
Oh interesting, ok thanks for the info. And congrats again on the amazing 2.3 release :)
-
And it's disabled by default? Is there a reason not to enable it?
That section of the page only shows up when you're running a factory image on a platform where a supported watchdog is detected. So if you see the option, it's available on that hardware.
-
I haven't tried the watchdog personally yet, but we had disabled it by default years ago on ALIX because if the system was too busy, legitimately, with passing IPsec traffic the watchdog might get missed and caused a reset. So while it's useful for many, it may not always make sense to enable it by default for every use case.
-
That section of the page only shows up when you're running a factory image on a platform where a supported watchdog is detected. So if you see the option, it's available on that hardware.
I'm running a RCC-VE 2440, same hardware as the SG-2440, right? Why don't I see it on my box?
Thanks,
Frank -
I'm running a RCC-VE 2440, same hardware as the SG-2440, right? Why don't I see it on my box?
Same hardware, not the same software.
-
I'm running a RCC-VE 2440, same hardware as the SG-2440, right? Why don't I see it on my box?
Did you try out another image on that pfSense box or did you go with the ADI image?
-
To see the Watchdog setting you have to be running the factory image for that hardware, not the CE version. If you bought an SG device, you can login to the portal and download it. If you bought the hardware with CentOS from Netgate and it's now running the pfSense CE image, you won't see that choice.
-
Is this feature considered stable and recommended to be enabled? I'm on the fence about the SG-2440 vs RCC-VE-2440 but this router is going in a remote location where remote hands don't really exist so stability is extremely important. If the watchdog makes even 1 save it more than paid for itself in the additional cost.
-
I've had it enabled on my SG-4860 at 128 seconds for about 10 days without issue.
That being said, I've never actually experienced a "lock up" of any of my SG units.
-
Is there any way to force a lock up so we can "test" the watchdog somehow?
-
Something like the FreeBSD equivalent of NotMyFault
https://blogs.technet.microsoft.com/markrussinovich/2011/01/09/blue-screens-in-designer-colors-with-one-click/
