- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Not as a way to bash support, of course. After all, at least they're trying to remedy. But maybe as a way to highlight the scope of the problem and get Verizon to wholly focus on this.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Bump. Anyone have anything new to share?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Just more observations of problems. 😞
I've been digging through the router's system logs and it seems like most of what's in there is inaccurate. For example 80% of the log entries are for Dec 2014! Excuse me but that's still 11 months in the future. Those incorrect log entries seem to persist between reboots too. The only usable log entries start at the last reboot and contain nothing that would indicate what the problem is. Presumably the problem would be in the last entry of the log before it rebooted.
I do see errors in the security log as the DNS server tries to resolve the IP address of a PC that's no longer on my network. Its happening quite frequently but I don't think its related to the problem at hand. Most likely some device had a drive mapped, or DLNA info stored for that old PC which is now in the scrap pile of antiquated equipment known as my attic. 🙂
Anyone else here using the undocumented setting to get DLNA to work on this router? I remember setting it maybe a year ago. I'm wondering if this has anything to do with the problem. FWIW that URL is
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I haven't messed with IGMP proxy at all, but it seems to come pre-enabled on the Rev. I. From what little I know about it, I think you would want it enabled unless you're experiencing DLNA issues like you said. Still, I suppose it couldn't hurt to turn it off and see if it makes a difference with the chronic rebooting issue. We've tried just about everything else.
As for strange log entries, oh yeah, I've got TONS. Most are cache entry/mac errors that seem to come every few minutes. This router has no shortage of weird stuff going on.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I checked that setting which I'd disabled almost a year ago and it had been enabled again. I disabled it and the router has been up now for over 7 hours. I think that might be a record for me. I'm doing any victory dance though until it stays up for a couple of days.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@g00py wrote:
Bump. Anyone have anything new to share?
Just an FYI:
I won't have much to add here anymore as long as my Rev. F keeps working as well as it has since replacing the Rev. I. It's only had one reboot since the switch and that was deliberatly because of me. So nearly 140 hours of it working smoothly. Again, this totally points to the Rev. I as being the sole problem here as far as I'm concerned.
I'll keep tabs on you guys to see if a fix comes down the pipe though. Good luck.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Chuckh1958: Good luck! Please post your findings.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Happy, interruption-free computing, sangs.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content