Print

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

[tentimes]

I would be grateful for any update at all from the Dlink staff. Dying here with 1.32NA and would love to know if an update is coming soon.

[davevt31]

They don't give estimates when firmware will be put out.  When its ready they will post it.

[tentimes]

Can we not let them answer this? They might give more information. I am in no doubt that you have no idea when the next firmware might be released, but I suspect they might have a better idea, even if it's a very rough ball-park estimate.

[davevt31]

That question has been asked and answered the same way for the 2 years that I have been on this board.  No estimates on when firmware will be done.

[tentimes]

This istuation is a little different from the last 2 years though, we have a really troublesome firmware and I think we need an update on how things are going on the fix. No harm in asking. If you don't want to know then that's ok.

[davevt31]

It's not that I don't want to know about new firmware, it's just the way that things are done.  It's the same way with game producers, everyone wants to know when the next patch for a game is coming out.  The answer is always the same in both instances, it will come out when its done.

Also, not everyone is having trouble with this firmware, which makes doing a new one even harder.  If there was a specific thing that they need to work on, that is a lot easier to fix than some people having this problem, others having a different one and even others having no issues.

[verizonfan]

x2 for an update.  Let D-Link provide an answer.

[EddieZ]

This istuation is a little different from the last 2 years though, we have a really troublesome firmware and I think we need an update on how things are going on the fix. No harm in asking. If you don't want to know then that's ok.

No, no harm in asking. But davevt31 is just managing your expectations. The situation is not really different from 2 years ago. Like davevt31 days: there are some people with issues, not the whole population.

[tentimes]

Judging by the sizeable amount of complaints both on this websites and across the internet I am minded to think a very significant amount of the userbase has problems with this latest firmware. It's a scandal frankly, and should have been addressed much more effectively. There should be regular feedback from the company on their progress on this - I would advocate weekly feedback given the scale of the issues faced.

Certainly if I am coding something for a company and there are bugs I would expect to have to give answers. They haven't even asked for peoples config files yet and it's been months now. That would have been the first thing I did if I couldn't recreate it in the lab. Unfortunately this is what you get with a global disconnect (thousands of miles) between CS/Sales and the company that engineers the firmware.

To be fair though the mods/devs on this forum don't duck the issue like many other companies would, so I have to give them their dues for that - they are always as helpful as they can be. I think this is a bad communication problem between Taiwan and the rest of the company. Just MHO.

[worldgeek]

I've been programming computers for the last 30 years.  We're all human.  Computer bugs are to be expected.  But the deadliest sin Dlink programmers had committed is: not allowing rollback to previous versions!  That's the dumbest to the nth degree!  You don't burn the bridge after you'd crossed. 

In software, nothing can't be reverted.  It's just will and skill.

Excuse my outburst.  I just hate to see a great router become an unreliable piece of hardware.

[EddieZ]

I've been programming computers for the last 30 years.  We're all human.  Computer bugs are to be expected.  But the deadliest sin Dlink programmers had committed is: not allowing rollback to previous versions!  That's the dumbest to the nth degree!  You don't burn the bridge after you'd crossed. 

In software, nothing can't be reverted.  It's just will and skill.

Excuse my outburst.  I just hate to see a great router become an unreliable piece of hardware.

Try to grasp the kernel situation in hardware/firmware and you will soon understand why a rollback is not possible/that simple.

[EddieZ]

Judging by the sizeable amount of complaints both on this websites and across the internet I am minded to think a very significant amount of the userbase has problems with this latest firmware. It's a scandal frankly, and should have been addressed much more effectively. There should be regular feedback from the company on their progress on this - I would advocate weekly feedback given the scale of the issues faced.

Certainly if I am coding something for a company and there are bugs I would expect to have to give answers. They haven't even asked for peoples config files yet and it's been months now. That would have been the first thing I did if I couldn't recreate it in the lab. Unfortunately this is what you get with a global disconnect (thousands of miles) between CS/Sales and the company that engineers the firmware.

To be fair though the mods/devs on this forum don't duck the issue like many other companies would, so I have to give them their dues for that - they are always as helpful as they can be. I think this is a bad communication problem between Taiwan and the rest of the company. Just MHO.

Getting the only configs will not do it. I can tell you they (Dlink) have tried recreating the issues on RMA-ed devices. Unfortunately they were not able to do that. This woulfd indicate that there might be a connection with other hardware devices used, either network periphirals or PC clients.

[worldgeek]

Try to grasp the kernel situation in hardware/firmware and you will soon understand why a rollback is not possible/that simple.

That simple?  Then there is a design flaw at the very beginning!  What is so restricted that you can't prepare a contingency "escape" route?  Engineers never expect the best to happen, but always prepare for the worst.  Didn't they teach that in engineering school anymore?

[gusjohnson]

Try to grasp the kernel situation in hardware/firmware and you will soon understand why a rollback is not possible/that simple.

So they say.  A straight rollback may be problematic but I've got to believe there is a way to create an upgrade that returns the 655 to stable 1.21 functionality.  Creating that upgrade might disrupt their development pipeline but it would appear to be a faster solution than whatever they've been doing for the past several weeks in trying to salvage 1.32a.   It seems to me that DLink simply isn't treating the situation as a crisis as there probably aren't enough of us out there to justify (in their opinion) changing course. I assume that new purchasers are getting the old firmware - they should offer trade-ins to those of us stuck in this situation but I'm not holding my breath.   

Unfortunately, I'm afraid that I've gotten to the point where I need to treat it as a crisis for myself.  Particularly because DLink won't even estimate when this problem might be fixed.  This means ditching the 655 and going with something else.  I won't consider DLink on principal.  I'm thinking Apple but would be curious to hear any alternative recommendations. 

- Gus

[EddieZ]

I guess in order to facilitate a rollback to the older kernel the upgrade/downgrade mechanism needs to be changed since kernel updates are locked.  Perhaps they can do a new firmware with better downgrade abilities, I don't know. But as I remember well, the 1.2x firmware was even worse when i comes to router performance and Shareport performance. So I really would stay away from that series. 1.11 seems to be stable, but you'll be lacking a lot of features. The A4 revisions are the ones that  also need the new kernel to function properly and will not be able to downgrade to 1.11 anyway since the hardware inside is not supported by 1.11.

For me the 1.32 works like a charm (router & Shareport). So no need here to downgrade all the way back.