Recommended Posts

I have used my WRT610N for months without reboots but to save power, I turn off the router when I and all my devices sleep at night. :)

For those in the US who might be wondering, some countries have on/off switches for AC power plugs. Heard US doesn't have them? You just "plug and play"?

System Up Time : 97 Days 6 Hours 33 Minutes 38 Seconds (Now : Tue Feb 21 2012 14:44:37)

This is from the work router - RV082 v3, think that's the actual time it was last upgraded to the latest build for IPv6 and another HTTPs patch that was annoying us. Also the dual-WAN portion i think got some tweak or something. Eitherway, haven't needed to change anything just yet.

Which router? Have access to hundreds of them ;)

Here are couple that have been on a while ;)

uptime is 2 years, 8 weeks, 3 days, 9 hours, 40 minutes

System returned to ROM by power-on

System restarted at 22:27:50 est Wed Dec 23 2009

uptime is 2 years, 37 weeks, 1 day, 5 hours, 55 minutes

System returned to ROM by power-on

System restarted at 10:25:26 EDT Sat Jun 6 2009

  • 8 months later...

Router (Netgear WGR614):System Up Time 17 days 13:26:15 ( think it rebooted itself....) That's not good... I had it on for months...

Wifi Access Point (Amped Wireless AP20000G): 18day:16h:59m:46s

Re-arranged my setup the other day when I was hooking up my new external hard drive to the server. Before this it had been on for about a month or so.

Firmware: DD-WRT v24-sp2 (10/10/09) micro

Time: 21:15:56 up 2 days, 3:40, load average: 0.68, 0.42, 0.18

I set my router to reboot every Sunday just to keep things smooth. I randomly get an issue where my Xbox 360 couldn't connect to the internet, this weekly reboot seemed to stop that. I am selling my Xbox soon so might turn off the weekly reboots, to be honest it don't affect much as its like 4am on Sunday so might keep it!

Probably 3 days or something as we had Hurricane Sandy the other week, power was out longer than UPS could handle too but since it came back i've been playing with upgrades/updates for devices since my uptime was lost anyways :D

Before that however it was like close to 200 days or something.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • According to Microsoft, Cause: One of the drivers controlling the device notified the operating system that the device failed in some manner.   https://support.microsoft.com/en-us/topic/error-codes-in-device-manager-in-windows-524e9e89-4dee-8883-0afa-6bca0456324e
    • This looks awesome, I will request access via Steam later this afternoon!
    • Personally, I’ve found that it’s usually worth investing in the infrastructure you don’t want to replace later, especially cabling. Running Cat6A (or better, depending on your needs) during an upgrade is relatively inexpensive compared to having to re-cable a few years down the road. For switches I try to balance current specs with realistic growth. If my budget allows it Ill choose switches with higher uplink speeds which leaves room for expanding later on, but I don’t necessarily overspend on access ports if the endpoints won’t benefit from them anytime soon. One lesson I’ve learned is that planning for scalability pays off. It’s much easier to add devices, VLANs, or higher-bandwidth workloads when your network infrastructure already supports it than to replace hardware later.  What is your budget like?
    • I hate the term, "future-proof." We saw it back in the 90's / 2000's, if not before. You cannot future-proof anything, since there is no definition of how far into the future you plan on prepping for. Best idea is to tell us what you currently have and what its use is at the moment, and we can then offer ideas about some areas that might need an upgrade and other areas that can be left alone.
    • I can agree that it is being used in a small capacity. I worked for a company where their engineers still used XP, and when asked why it was because their sensor software wasn't compatible with newer operating systems and the software was discontinued so they couldn't upgrade the software. Given that the sensors were still in use by companies, they had to continue using XP to support the sensor, otherwise the price to the company would have gone into the millions or billions. Our response was simple: Ok, you can keep the XP machine. But we're removing it from the network. "But then it can't access the Internet or folder shares!" Yup, kinda the point. If someone wants to continue using an unsecure OS they can do, I have no problem with that. But it should be isolated. Simple. I had a fight with a guy in the engineering department for weeks before he finally relented. But we digress.   What do I plan on doing to commemorate the anniversary? Nothing. I have fond memories of the OS, but at the end of the day it's just an OS. If I had some time I might see if I could install it on my Raspberry Pi for a laugh. But my reflex memory with today's OS ideas would probably get me frustrated and I'd uninstall it after 5 mins.
  • Recent Achievements

    • Reacting Well
      NovaEdgeX earned a badge
      Reacting Well
    • Week One Done
      NovaEdgeX earned a badge
      Week One Done
    • One Year In
      BA the Curmudgeon earned a badge
      One Year In
    • Conversation Starter
      rosiecharles earned a badge
      Conversation Starter
    • First Post
      KMilenkoski1202 earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      539
    2. 2
      +Edouard
      269
    3. 3
      PsYcHoKiLLa
      154
    4. 4
      Steven P.
      99
    5. 5
      macoman
      66
  • Tell a friend

    Love Neowin? Tell a friend!