Well I use Draytek with DDNS for some people and it seems stable, they only start crashing when you start using advanced features like VPN and custom routing etc (Not that I am excusing that, you understand, but the OP probably isn't going to be using those features).

In reply to a post by pmb00cs:

Someone else in this thread mentioned Draytek, and I have one of their routers, and am very happy with it, however, I very much doubt it would have prevented your issue. It sounds to me, like you have exhausted the running memory of the router, and caused it to crash. The RTSP connection you had to your cameras is a control connection, and the video data would have been sent over another protocol, I suspect something UDP based (but I could well be wrong) and UDP connection tracking is harder for a router to perform than TCP connection tracking, and so will have used more memory than the router would otherwise have used.

So you are saying a different router would also have exhausted the running memory in the same manner the Netgear one would? I don't think that is very likely.

Yes, I am.

Now it may have taken longer, or the memory exhaustion of this netgear may have been a long time coming. I do not know how long the netgear has been running, nor do have any experience of that model of netgear to offer a reasonable estimate of how long it will have taken to run out of memory.

What I can say is I have yet to come across a router that has perfect memory allocation and reclamation features, such that it is immune to memory exhaustion. They tend to have features that mitigate the damage such an event causes, and monitoring of their memory usage to alert their administrators to the risk, allowing steps to be taken to prevent issues.

If you have a router that takes longer to exhaust it's memory than it is ever likely to be on for then you would never see any memory exhaustion issues, and that, in my experience, applies to the design of every consumer, and soho, grade router out there.

I am also speculating that memory exhaustion is the cause of the crash. It just seems, in my llimited knowledge of this event, to be the most likely cause. It could also be caused by corruption of the running config, or a change to the connection parameters set by the ISP (ie the router is running fine, but currently unable to connect to the internet for one of many reasons), or a hardware failure, or a prolonged power outage at the OP's home, or one of any number of possible other causes, all of which would effect even the most expensive router, just the more expensive routers may be effected less often by some of them, or handle them better, or just differently.

The only answer is a remote reboot switch using telephone or mobile for home situations

http://www.amazon.co.uk/GSM-TIMER-SWITCH-CONTROLLER-...

http://www.technotrend.co.uk/pages/ss_products/phone...

This seems to be the cheapest solution as already proposed http://www.amazon.co.uk/Mercury-350-103-TMR-1-Timer-...