Basically, my issue stems from the latest Boxee firmware from 2 weeks ago, that since then, its been causing my DIR 655 to reset itself, thereby disabling my whole home internet. It eventually turns back on again after a while, but the process doesn't stop.
Basically, my DIR 655 is connected, hard wired to my boxee. I also have a NAS 323 hard wired to my router. I've had this setup on my boxee, reading all my movies/shows from my NAS without any issues for the past 10 months. Then the firmware from 2 weeks ago on the boxee started to cause my router to reset. Don't know how or why. Boxee support is trying to help, but they can't figure it out. And its not happening to anyone else.
I thought it was a hardware router failure, so I bought another of the same model to try that out, same thing happened though. When I rolled back my boxee firmware to the previous version, it no longer causes my router to reset.
Now, besides me trying to figure out how to correctly block the boxee from updating on the router. Is there anything I can do on the router to tell it to prevent it from letting the boxee forcing it to reset? Any thoughts/ideas?
To answer some questions from Fuzz,
I'm on High Speed DSL. My internet provider modem is acting as a bridge to my DIR 655. Its been working fine for the past 10 months.
I've also done the following:
Ensure DNS IP addresses are being filled in under Setup/Internet/Manual? You can find these under Status/Device Info/Wan section.
Turned off ALL QoS
Turned off Advanced DNS Services if you have this option under Setup/Internet/Manual.
Turned on DNS Relay under Setup/Networking.
Setup DHCP reserved IP addresses for all devices on my router.
Ensure devices are set to auto obtain an IP address.
I have Set Firewall settings to Endpoint Independent for TCP and UDP..
Basically, I've put my boxee back to my previous firmware, and this doesn't cause my router to reset and disable my internet. But I don't get how/why a firmware update can trigger my router to do this?
Any other thoughts or ideas? I did capture some router logs when this last happened last night, but I'm trying to decipher it as a non techie, its not easy
