• June 01, 2025, 08:12:24 PM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Pages: 1 ... 3 4 [5] 6 7 ... 9

Author Topic: 1.31 Offical Release  (Read 94549 times)

Lycan

  • Administrator
  • Level 15 Member
  • *
  • Posts: 5335
Re: 1.31 Offical Release
« Reply #60 on: May 01, 2009, 04:16:48 PM »

Again,
IF this was a problem with code we'd see more complaints. 655 is the highest selling router D-Link makes. I'm sure we'd see more then 1-10 people complaining about this.

Now, I'm not devalidating your issue. There are 100 different things that could have failed that are causing this issue. For instance, a bad burn to the EPRom, adusting the radio after the firmware upgrade(e.g. now it's more sensitive then it was before and is picking up interference that is causing poor behavior), or the unit is just plain broken.

What can be done? Simple. Contact technical support (i know i know), go through the steps, and if they can't help get your RMA.

Now, there is one thing that you might mention, that you never had this problem before upgrading the firmware, and since you can't downgrade you believe that the code is responsible.

Also I might suggest locating the 1.30Beta code and load that. See if the problem persists.
Logged

Lycan

  • Administrator
  • Level 15 Member
  • *
  • Posts: 5335
Re: 1.31 Offical Release
« Reply #61 on: May 01, 2009, 04:18:02 PM »

I'm having almost the exact same issue as unicks is experiencing. This is not an isolated or unique issue.

Understand that D-Link has sold 100000's of this router. It's not a problem with the code. It may hawever still be a problem with the code, your router and your environment.
Logged

desides

  • Level 1 Member
  • *
  • Posts: 9
Re: 1.31 Offical Release
« Reply #62 on: May 01, 2009, 04:34:28 PM »

Understand that D-Link has sold 100000's of this router. It's not a problem with the code. It may hawever still be a problem with the code, your router and your environment.

Since 1.31 is the only change made to my home network, it stands to reason that 1.31 would be the cause. 1.21 was fine for me, very solid. 1.31 is just unusable.

I'm waiting for an email reply from tech support.
Logged

ledan

  • Level 1 Member
  • *
  • Posts: 6
Re: 1.31 Offical Release
« Reply #63 on: May 01, 2009, 05:11:04 PM »

Updated from the package in the FTP site, reset to its factory defaults and configured from the scratch, by hand. A2 hardware. It's showing 1.31NA (never showed this "NA" before. anyway...) and seems to be working fine so far, except for a noticeable rate and signal loss on wireless, which is weird because nothing has been changed (positions, antennas, even channels). inSSIDer is still showing the same signal strenght as before. I've tried disabling b signal but it kept the same behavior.

Has anyone noticed the same? I've just realized that the router has never showed the full speeds it's showed with the original firmware (1.10 ou 1.11, I guess).

Had a similar problem with 1.22beta. Thanks for this information. I'll stay with 1.11
http://forums.dlink.com/index.php?topic=4971.0
Logged

EddieZ

  • Level 10 Member
  • *****
  • Posts: 2494
Re: 1.31 Offical Release
« Reply #64 on: May 01, 2009, 06:05:25 PM »

Since 1.31 is the only change made to my home network, it stands to reason that 1.31 would be the cause. 1.21 was fine for me, very solid. 1.31 is just unusable.

I'm waiting for an email reply from tech support.

That's cutting corners and a very simplistic ('easy') reasoning.
Question: did you restore your 1.2x config in the new 1.3x or did you reset to factory default and rebuild the configuration?

I second the opinion that three complaints do not make a faulty firmware. My 1.3x works great but in your line of reasoning I should have the problem too?
Again people seem to think that 1.11 is the holy grail of firmwares. Why? Because they think that the measurements/gauges in 1.11 were more accurate than the those in the newer firmware, thus showing better connection rates. It's the other way around: the 1.11 is more inaccurate (too optimistic). There has been no change in radio strength. The question has been put over and over again at Dlink tech: they made no firmware changes concerning radio strength...
Logged
DIR-655 H/W: A2 FW: 1.33

desides

  • Level 1 Member
  • *
  • Posts: 9
Re: 1.31 Offical Release
« Reply #65 on: May 01, 2009, 06:33:29 PM »

That's cutting corners and a very simplistic ('easy') reasoning.
Question: did you restore your 1.2x config in the new 1.3x or did you reset to factory default and rebuild the configuration?

It is not "simplistic" or "easy" reasoning, it is a logical diagnosis of the problem. When previously-working equipment ceases to function as expected, the first task is to figure out what changes occurred to bring about the faulty behavior. In this instance, it's the firmware upgrade of my DIR-655. Everything else on my home network is unchanged in all respects: configuration, physical routing, devices attached to the network, firmware and software versions on each of those devices, etc. The only change is 1.31. And I remind you that 1.21 worked perfectly on my network.

To answer your question, I did not restore settings: I used the 30/30/30 method to clear out all prior settings, updated the router to 1.31, then performed the 30/30/30 method again, and finally reconfigured my settings manually.
Logged

EddieZ

  • Level 10 Member
  • *****
  • Posts: 2494
Re: 1.31 Offical Release
« Reply #66 on: May 01, 2009, 06:39:41 PM »

It is not "simplistic" or "easy" reasoning, it is a logical diagnosis of the problem. When previously-working equipment ceases to function as expected, the first task is to figure out what changes occurred to bring about the faulty behavior. In this instance, it's the firmware upgrade of my DIR-655. Everything else on my home network is unchanged in all respects: configuration, physical routing, devices attached to the network, firmware and software versions on each of those devices, etc. The only change is 1.31. And I remind you that 1.21 worked perfectly on my network.

To answer your question, I did not restore settings: I used the 30/30/30 method to clear out all prior settings, updated the router to 1.31, then performed the 30/30/30 method again, and finally reconfigured my settings manually.

If it is the firmware just explain this to me: why don't I suffer from this issue?
Logged
DIR-655 H/W: A2 FW: 1.33

kentuck1163

  • Level 1 Member
  • *
  • Posts: 4
Re: 1.31 Offical Release
« Reply #67 on: May 01, 2009, 06:45:03 PM »

For the record, I've been running 1.31 for a couple days now with no issues at all.  So far its been great!  I was having a problem with 1.30 with severely degraded wireless speeds (to the point where my DSL speed tests were reporting about 600-1000Kbps when I should have 6000Kbps service.  Anyway, I reset the router to factory defaults and started making changes one by one and then retesting connection speeds after every change.  However, I never was able to get it to start messing up again.


Logged

desides

  • Level 1 Member
  • *
  • Posts: 9
Re: 1.31 Offical Release
« Reply #68 on: May 01, 2009, 07:25:21 PM »

If it is the firmware just explain this to me: why don't I suffer from this issue?
Finding out why this is happening is sort of the purpose of my posting in this thread.
Logged

TommyLee

  • Level 1 Member
  • *
  • Posts: 8
Re: 1.31 Offical Release
« Reply #69 on: May 02, 2009, 01:50:43 AM »

Hello Everyone,

These last few forum posts are exactly the point I was attempting to make in my earlier post:

"If you are not currently experiencing a problem, or the new firmware does not provide a requested upgrade feature, then there is truly no need to update your firmware version. Having the latest and the greatest firmware is only okay for those that do not rely on it for there sole internet connection. All the threads in this post are a perfect example of that."

The last truly stable version for the 655 is v1.21.

As for everyone who has unfortunately upgraded to v1.31 only to be plagued with problems, either hope for one of these three options soon:
1.) D-Link is finally able to duplicate and rectify the firmware in there in-house testing, and provide a stable update.
~or~
2.) D-Link puts out an update that un-locks downgrading to restore at the very least v1.21.
~or~
2.) Hope that DD-WRT comes out with the option to support the 655? Doubtful though, since they haven't been able to support anything in the 6xx series.  ;)

The only reason D-Link locked this update, is most likely to get everyone on the same firmware to alleviate support issues. The more firmware revisions out there in the field, the more difficult the support. I only wish they would have taken the time to more thoroughly test a version in various field scenarios before locking it down like they have.

Spread the word about the forum. If enough people post with similar issues, maybe everyone could petition for D-Link to put out an updated firmware to at least un-lock downgrading back to v1.21  :-\

Respectfully,

Tommy Lee
Logged

EddieZ

  • Level 10 Member
  • *****
  • Posts: 2494
Re: 1.31 Offical Release
« Reply #70 on: May 02, 2009, 02:40:26 AM »

Finding out why this is happening is sort of the purpose of my posting in this thread.

Finding out is something different than just crying out  "blame the firmware". When the discussion already concludes that it's the firmware that's to blame, one is loosing sight of all kinds of possible causes for this behaviour. During the last year I am active on the board it has showed that in many, many cases it was not the firmware...
Logged
DIR-655 H/W: A2 FW: 1.33

Msradell

  • Level 1 Member
  • *
  • Posts: 20
Re: 1.31 Offical Release
« Reply #71 on: May 02, 2009, 05:10:02 AM »

Hello Everyone,

These last few forum posts are exactly the point I was attempting to make in my earlier post:

"If you are not currently experiencing a problem, or the new firmware does not provide a requested upgrade feature, then there is truly no need to update your firmware version. Having the latest and the greatest firmware is only okay for those that do not rely on it for there sole internet connection. All the threads in this post are a perfect example of that."

The last truly stable version for the 655 is v1.21.

As for everyone who has unfortunately upgraded to v1.31 only to be plagued with problems, either hope for one of these three options soon:
1.) D-Link is finally able to duplicate and rectify the firmware in there in-house testing, and provide a stable update.
~or~
2.) D-Link puts out an update that un-locks downgrading to restore at the very least v1.21.
~or~
2.) Hope that DD-WRT comes out with the option to support the 655? Doubtful though, since they haven't been able to support anything in the 6xx series.  ;)

The only reason D-Link locked this update, is most likely to get everyone on the same firmware to alleviate support issues. The more firmware revisions out there in the field, the more difficult the support. I only wish they would have taken the time to more thoroughly test a version in various field scenarios before locking it down like they have.

Spread the word about the forum. If enough people post with similar issues, maybe everyone could petition for D-Link to put out an updated firmware to at least un-lock downgrading back to v1.21  :-\

Respectfully,

Tommy Lee

To start with many people believe 1.22B05 is as stable as and works better than 1.21 so based on that I question your line of thinking but going onward....

I'm sure D-Link does much testing however it's impossible to replicate every real world condition out there.  This is especially true for people who make their own "enhancements".

WW-DRT can never provide software to work for the 6xx series of routers because they are based on a very different operating system (additional information posted elsewhere).  Parts of it operating system are proprietary and not publicly available.

I do agree however that it would be nice if we could downgrade from 1.3x versions of the firmware to lower version.  I'm still not really sure why this can't be done, all the explanations I've seen so far just sound like excuses!

I really wonder how many end users ever upgrade the firmware on their routers.  My bet would be that most users never do in their router is still running whatever firmware version it came with.  Thus those of us who were constantly changing our firmware are in the minority and not truly D-Link's bread and butter.
Logged

EddieZ

  • Level 10 Member
  • *****
  • Posts: 2494
Re: 1.31 Offical Release
« Reply #72 on: May 02, 2009, 05:12:44 AM »

There have been a lot of threads already about DD WRT NOT working EVER on the DIR. DD WRT is for Linux routers which the DIR 6xx is certainly not... The 655 Ubicom platform is propriety , so you will never see OpenSource/GPL code to fiddle with.
Logged
DIR-655 H/W: A2 FW: 1.33

desides

  • Level 1 Member
  • *
  • Posts: 9
Re: 1.31 Offical Release
« Reply #73 on: May 02, 2009, 09:18:02 AM »

Finding out is something different than just crying out  "blame the firmware".

I would really prefer help fixing my problem and not denigration of that problem.
Logged

TommyLee

  • Level 1 Member
  • *
  • Posts: 8
Re: 1.31 Offical Release
« Reply #74 on: May 02, 2009, 09:51:51 AM »

To start with many people believe 1.22B05 is as stable as and works better than 1.21 so based on that I question your line of thinking but going onward....

I'm sure D-Link does much testing however it's impossible to replicate every real world condition out there.  This is especially true for people who make their own "enhancements".

WW-DRT can never provide software to work for the 6xx series of routers because they are based on a very different operating system (additional information posted elsewhere).  Parts of it operating system are proprietary and not publicly available.

I do agree however that it would be nice if we could downgrade from 1.3x versions of the firmware to lower version.  I'm still not really sure why this can't be done, all the explanations I've seen so far just sound like excuses!

I really wonder how many end users ever upgrade the firmware on their routers.  My bet would be that most users never do in their router is still running whatever firmware version it came with.  Thus those of us who were constantly changing our firmware are in the minority and not truly D-Link's bread and butter.

My line of thinking comes from more than two decades in IT, and holding nearly two dozen certifications in the industry from MSFT, AAPL, and CSCO.

My 655's are not my sole internet connection routers, hence, I can modify and play with them without regard to any resulting ramifications. I only ever test firmwares that promote higher stability, better security, and or the possibility of speed enhancements based on whats been updated with the firmware in the release notes. Sometimes this requires the ability to read between the lines.  Therefore, my statement concerning v1.21 being the last truly stable version comes from a culmination of substantial experience in the industry and actual hands on testing.

As for Lycans statement about the sales of the 655, well, the 655 is D-Link's highest selling router simply because of its initial magazine reviews. First impressions are everything, ...bottom line.

I'm not totally dogging D-Link so to speak. Cisco's sub brand Linksys, is far more unstable (unless you use DD-WRT). However, my Cisco PIX is about as solid as they come. And Apple's Airport Extreme is simply not secure enough.

Lycans observation of why aren't more people complaining if v1.31 is so unusable goes hand in hand with the last paragraph of your quoted statement above. Simply not enough people ever upgrade, which I completely agree with if there are no benefits to be gained or immediate problems to be solved. However, this in no way can be used as a valid measurement of v1.31's stability just as Lycan is claiming that people with issues in this forum can in no way be used as a valid measurement of v1.31's instability.

The bottom line is simple logic. If everything in the environment is stable and working, and the only change made to this environment is the firmware, then its the firmware. The odds of this are much higher than the odds of coincidentally having some other inadvertent hardware failure elsewhere at the exact same moment the firmware on the router just happens to be upgraded. That's just completely illogical.

And "decides", the best advice that could be given at this point would be to follow the step's "kentuck1163 used in this post:
For the record, I've been running 1.31 for a couple days now with no issues at all.  So far its been great!  I was having a problem with 1.30 with severely degraded wireless speeds (to the point where my DSL speed tests were reporting about 600-1000Kbps when I should have 6000Kbps service.  Anyway, I reset the router to factory defaults and started making changes one by one and then retesting connection speeds after every change.  However, I never was able to get it to start messing up again.

D-Link is unfortunately going to need detailed information about the failure, in addition to an open mind, in order to actually resolve the issue.

And Lycan, my last note would be if v1.31 was simply wonderful and without issue as you would appear to suggest, then there would not be a single post of failure in this forum about it.

Respectfully,

Tommy Lee


Logged
Pages: 1 ... 3 4 [5] 6 7 ... 9