Is there a keep alive feature in Shibby Tomato?

Discussion in 'Tomato Firmware' started by Lidodil, Jan 12, 2018.

  1. Lidodil

    Lidodil Connected Client Member

    I noticed that there's a feature like that in DD-WRT, but I can't find anything similar in the Tomato/shibby admin. Ideally we could reboot the modem if there's no ping response from a set address, but rebooting tomato would be the next best thing.
     
  2. rs232

    rs232 Network Guru Member

    I don't ike the sound of it but regardless you can ping the modem IP (or any Internet IP really) and run this in the scheduler ever e.g. 60 min

    Code:
    ping -c5 192.168.1.1 >/dev/null || /sbin/reboot
    I do not suggest you use this though
     
  3. eibgrad

    eibgrad Network Guru Member

    AFAIK, there is no such feature in Tomato. But it wouldn't be hard to write one. IMO, you'd be better off w/ a script that runs continuously. Anything timed to run in cycles of less than 5 mins is NOT a proper task for the scheduler given the startup costs associated w/ any new process. And if you cut it too close, you might find the router constantly rebooting.

    I found it curious that you thought rebooting the router was the next best thing to rebooting the modem, implying the modem is the known source of the problem. In such cases, in my experience, rebooting the router rarely fixes anything. In fact, when it happens to me, my modem just keeps giving me short 60 secs leases, which my router keeps renewing. IOW, the modem and router just keep spinning their wheels until whatever is causing the hiccup (perhaps an issue w/ the ISP) clears up. It's better to just let the problem work itself out, or reboot the modem. At least this keeps the LAN available for other purposes.

    Where I *have* seen the keepalive (watchdog) effective is when the router is configured as a wireless bridge. If the AP of the primary router has an issue, or the primary router is rebooted, *sometimes* the wireless bridges can't get reestablished w/ the primary AP unless they reboot. I've seen this a lot on dd-wrt in particular. But for the purposes of the WAN, I'm not convinced its effective *if* the source of the problem is the modem, or something further upstream.
     
    Last edited: Jan 12, 2018
    Monk E. Boy likes this.
  4. Lidodil

    Lidodil Connected Client Member

    Thanks. I'll try to leave it as is and see how it goes. I've left a shibby tomato version running on an original Linksys WRT54G for years without frequent reboots. Hopefully this will be as stable on the new router I got.
     
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice