Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[richv]

I installed version 1.12b5 the day it was released and it seemed to be working fine.  Today the router disappeared from the network.  This is the same "bug" I was seeing before after I installed v1.11.

The router sites remotely in my home and having to reset it every two-three days is difficult.  I hope this gets resolved soon.

[cerjzc]

Upgraded to 1.12 a couple days ago and 2 days in a row it has disappeared/hung up and I have to pull the power cable and reinsert it.  I have now disabled DNS Relay again which is what had worked on 1.11 for several months.

I hope at least with DNS relay off again it will continue to work as it did in 1.11.

Thanks,
Jeff

[rhn]

The 5ghz seems to be the one that disappears on me.  It has very similar settings to my 2.4 ghz network.  I stopped using it because it was flaky.  I wonder if some of you are having problems because of that?  The 2.4 network seems to work rather well.  I'm annoyed though that I can't rely on the 5 ghz at the moment.  But then again, this is so far a world better than 1.11 was.

[hogdoc]

Day 2 with 1.12b and so far stable and no locks ups. I have not activated port forwarding yet as when I do I lose my wireless status info. Also noticed the wireless connection is not restarting randomly as stated in the log with 1.11. Speeds are stable with better uploads for 450kbps to 2000kbps. I also did a fresh install and NOT a restore config file as mentioned earlier. Hope that helps others.

[KaarSar]

Is it better than the original 1.01?
What I mean is, is it worth updating? Or should I wait until this beta turns official?

[mikeny]

Well it's too bad they didn't fix the 'wireless client info' bug.  I will pass and stick to 1.01 on my replaced router.  You guys are very brave.  If I was on 1.11, I would try it.  It's working great with 1.01 so I'm going to stay on the sidelines.  Thanks for testing.

[fatalad]

ru fi oh, you should probably put this firmware up and take down 1.11.  I think this firmware is ready for prime time. Theirs probably a lot of people that are having issues that don't even go to the forum for help and they might just return the router and get a different brand

[hogdoc]

For gods sake, STICK with 1.01!! Don't upgrade unless you have issues and the beta is final and working fine for a few months. I was not having any issues with 1.01 and just upgraded to fix any potential bugs, what a mistake. Why in the hell would d-link make the firmware non-downgradable?? It was either go for 1.12 or else my router was facing an untimely accidental death for a warranty replacement as tech support on the phone was hopeless and worthless. At least we have a moderator who is addressing the issues and I think we all appreciate his/her work. I just wish there were more of them around to work on this issue.  

[hogdoc]

WELL IT CRASHED!! Not only a few hours on my last post the router crashed again after 2 days. This time it did it while I was on. I noticed the web pages were getting slow to load. I tried to login to the router and no dice. Could still login into other intranet devices like Vonage Box. Then the router crashed with no internet pages loading but strangely enough my streaming Pandora was still playing! Rebooted and back to normal. Ru fi oh, this is not ready for prime time and this is unacceptable performance as I need a reliable router. Looks like this router is going to have to die for a replacement! Good luck to all that are in my shoes!!

[richv]

I experienced the exact same thing as hogdoc.

It appears as if the router is doing a slow meltdown.  Not everything stops working once you can no longer address the router directly but eventually it completely collapses.

I have the dlink network monitor widget up all the time and it loses the router before the, it seems, the degregation begins.  It seems that applications already communicating with sites continue to work and the internet connection slows down.

I saw that applications such as pandora, netflix, news widgets, weather bugs and such continued to work as long as I didn't stop and restart the programs/device after web pages stopped loading.

When the router is working, it's great.  However, this slow meltdown is unacceptable and must be fixed.

[claykin]

For gods sake, STICK with 1.01!! Don't upgrade unless you have issues and the beta is final and working fine for a few months. I was not having any issues with 1.01 and just upgraded to fix any potential bugs, what a mistake. Why in the hell would d-link make the firmware non-downgradable?? It was either go for 1.12 or else my router was facing an untimely accidental death for a warranty replacement as tech support on the phone was hopeless and worthless. At least we have a moderator who is addressing the issues and I think we all appreciate his/her work. I just wish there were more of them around to work on this issue.  

My guess as to why firmware is not downgradable is due to Dlink probably changing the CPU (Ubicom) microcode along with the new firmware installation.  The old firmware likely won't work with the modified microcode.

I think that Dlink's engineers are beginning to realize the shortcomings of the Ubicom CPU solution.  While a great CPU from a performance perspective, I think they are experiencing issues programming to it.  This may be part of the reason why Dlink chose to abandon it and go with the Atheros CPU for the B1 revision.

Can't say for sure, but since Dlink isn't forthcoming about the limitations, I just thought I'd share my experience.  I formerly worked for a company that did software/hardware design using MIPS CPU's.

[claykin]

I experienced the exact same thing as hogdoc.

It appears as if the router is doing a slow meltdown.  Not everything stops working once you can no longer address the router directly but eventually it completely collapses.

When the router is working, it's great.  However, this slow meltdown is unacceptable and must be fixed.

Could be a memory leak where the kernel is losing needed RAM space and being forced to shutdown services to the point where the router becomes unusable.  Dlink should be able to resolve this.

Maybe Ubicom's new Linux toolset will give Dlink the freedom their engineers need to manipulate this CPU properly.

[DanGarion]

I have an RMA ready to send in if this one doesn't fix it...

[user11]

Four days of no issues, then the dreaded 1.11 firmware lockup symptom in 1.12b5, solution was to disable dns relay again. Maybe it's time to RMA.

[wfdavis]

Same here, 4 days and got up this morning and the router was locked out. Had to pull the plug and reboot. DNS relay was enabled. Guess I'll have to disable it again. Anyone know where I can order a B1 version? I'm reading that the B1 is working great with the 202 firmware.

W