5 ms·

I don't think automatic updates would be as disruptive as you think. And having the ability to disable them and apply updates manually, combined with some fore

I don't think automatic updates would be as disruptive as you think. And having the ability to disable them and apply updates manually, combined with some forewarning like you are talking about (an email that says your router will restart tomorrow at 3am unless you do it sooner), would go a really long way.

aequitas 8y ago
Don't forget that a lot of the customer base for Mikrotik is in remote locations (ie: P2P connections in rural areas) or small ISPs. Having the router in your office die on you (even during office hours) is a little different than all your customers call you the same day their only internet connection is gone.
- icebraining 8y ago
  ISPs would just have to disable it before installing the router. Still seems like a good default.
- ip26 8y ago
  I used to be a customer of a remote WISP, P2P in a rural area. I can't speak for all WISP's, but we only had service about 12 hours a day, less if it was raining. Five minutes to reboot a router would have been invisible.
  - thejrk_ 8y ago
    I used to contract with a WISP. I would regularly get calls to "reboot the router" from the owner. The "router" was a fiber switch at their CO. I would just do it when they asked. I wasn't a customer nor did I get paid enough to fix their network. Sorry if that was your connection. :)
Alupis 8y ago
A lot of Mikrotik's are installed at WISP's and other ISP's... making unplanned reboots very disruptive. Those of us using them on our corporate networks might be inconvenienced by a temporary outage, but that's unlikely at 3am... however, scheduling and doing these manually is still the best way for enterprise gear.
- lostapathy 8y ago
  I doubt that most ISPs who can't be bothered to apply security updates are going to notice a 5 minute reboot. Split the difference - email the user that an update will apply on $date unless they do it first, or if they delay it (and don't let them delay it indefinitely).
  - Alupis 8y ago
    You can already script something like this into RouterOS (Mikrotik's OS).
    - lostapathy 8y ago
      Good - they should make it the default!

aequitas 8y ago

Don't forget that a lot of the customer base for Mikrotik is in remote locations (ie: P2P connections in rural areas) or small ISPs. Having the router in your office die on you (even during office hours) is a little different than all your customers call you the same day their only internet connection is gone.

icebraining 8y ago
ISPs would just have to disable it before installing the router. Still seems like a good default.
ip26 8y ago
I used to be a customer of a remote WISP, P2P in a rural area. I can't speak for all WISP's, but we only had service about 12 hours a day, less if it was raining. Five minutes to reboot a router would have been invisible.
- thejrk_ 8y ago
  I used to contract with a WISP. I would regularly get calls to "reboot the router" from the owner. The "router" was a fiber switch at their CO. I would just do it when they asked. I wasn't a customer nor did I get paid enough to fix their network. Sorry if that was your connection. :)

Alupis 8y ago

A lot of Mikrotik's are installed at WISP's and other ISP's... making unplanned reboots very disruptive. Those of us using them on our corporate networks might be inconvenienced by a temporary outage, but that's unlikely at 3am... however, scheduling and doing these manually is still the best way for enterprise gear.

lostapathy 8y ago
I doubt that most ISPs who can't be bothered to apply security updates are going to notice a 5 minute reboot. Split the difference - email the user that an update will apply on $date unless they do it first, or if they delay it (and don't let them delay it indefinitely).
- Alupis 8y ago
  You can already script something like this into RouterOS (Mikrotik's OS).
  - lostapathy 8y ago
    Good - they should make it the default!