D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: Peter_G on January 21, 2009, 03:36:13 PM
-
The Dlink Dir-655 update site has posted Firmware 1.22 today but if I use the search for function in the firmware page it is not found and 1.21 is recognized as the most up to date firmware release.
It lists only a few fixes. Is there any documentation about this?
I've downloaded the file which is approx. 1.4 meg but I will not get a chance to try this upgrade until later when I don't have so many computers online.
If anyone has tried this, please post some results
-
Upgraded and setting were retained so no reloading configuration.
DNS relay seems to be working OK so far.
Comes with Securespot and was enabled by default so I disabled.
That is about it for now.
Edit: After further testing I have found I need to once again disable DNS relay.
-
Any chance that 1.22 fixed the Wake on Lan (WOL) issues?
-
Down grade back to 1.11.
We've got another 1.22 coming, we're told they believe they've pin pointed the DNS relay issue.
-
Using 1.22 on A2 hardware- no issues at all. Did have to restore the configuration file after the flash.
-
Down grade back to 1.11.
We've got another 1.22 coming, we're told they believe they've pin pointed the DNS relay issue.
Just what does this mean exactly? Why downgrade so drastically to 1.11? How soon/how long until we can expect this new ''1.22 coming''?
-
Now... See www.dlink.com
Misread, sorry
-
Down grade back to 1.11.
We've got another 1.22 coming, we're told they believe they've pin pointed the DNS relay issue.
So there is another one coming out?
-
I just noticed the v1.22 firmware files on the FTP have changed. The release notes file is different, and also the firmware's MD5 has changed.
-
Why not simply bump it up to 1.23 or 1.221 to reduce confusion?
-
Why not simply bump it up to 1.23 or 1.221 to reduce confusion?
Yeah, that and the funny fact that the previously posted version was actually the newer version than the latest posted. The ''new'' one is dated January 5th while the previous one was much later--unfortunately don't remember exactly when because I ''upgraded'' to the ''new'' version.
Now I'm confused...
-
Why not simply bump it up to 1.23 or 1.221 to reduce confusion?
That would be too logical to do. ;)
-
Seems to be working fine so far. I'm not sure which "1.22" I have. The release notes have 1/22/09 but the version tag on the admin screen is 1/5/09.
I was experiencing wireless connection drops across different G clients (laptop, Wii, Roku, etc.) with the 1.21 and 1.20 rev which have been eliminated with this version so far (only 4 hours of testing of course). I was going to back down to 1.1x today after troubleshooting several hours last night...good timing.
UPDATE: Still having occassional wireless drops on 1.22. Annoying but I can deal with it untill 1.22 is released again for me to test. Seems this is a common issue with dozens of possible causes and solutions based on other posts.
-
Here's a little insight.
Version numbers are for TRACKING of versions. That being said if we come out with a firmware version 1.22b01 and a 1.22b02 and the b02 gets posted, but is found to have a flaw we'll post the working b01 until we can either fix the flaw (1.22b03) or get a new firmware 1.23.
Please do not ask me what constitutes a new firmware or a build change, they NEVER tell me.
(I'm guessing it has to do with how far in to the code they have to go to effect the fix/change.)
We can NOT just change the numbers as that would skew our tracking process and also disrupt error reporting to our software people.
Hope this shed's some light on the situation for you guys and helps you to be less confused.
-
I understand that, Lycan.
A quick suggestion, though: I think the router's check for new firmware function should be able to detect a newer build of the firmware version installed, and offer to update.
-
That can't happen.
Because the update functionality is based on a .xml we control. It's not automatic. we handle it.
-
I installed 1.22 today and it's working much better for me than 1.21 did (1.21 was bad enough for connecting to my company's VPN that I had to revert back to 1.20).
So far so good (note: I do have DNS relay disabled). Haven't tested out everything yet... but first impressions are good. :)
-
Here's a little insight.
Version numbers are for TRACKING of versions. That being said if we come out with a firmware version 1.22b01 and a 1.22b02 and the b02 gets posted, but is found to have a flaw we'll post the working b01 until we can either fix the flaw (1.22b03) or get a new firmware 1.23.
Please do not ask me what constitutes a new firmware or a build change, they NEVER tell me.
(I'm guessing it has to do with how far in to the code they have to go to effect the fix/change.)
We can NOT just change the numbers as that would skew our tracking process and also disrupt error reporting to our software people.
Hope this shed's some light on the situation for you guys and helps you to be less confused.
I was right with you up until the part where you started talking. ;)
-
Would still like to request the ability to have client "ALIAS" in the wirless client information page.
As well, that feature for detecting new firmware has NEVER worked on my 655 here in canada.
-
I tried to update my DIR655 A2 (1.21) with the 2 1.22 firmwares versions out this week but each time, the updating is ok but my router write it's the 1.21 firmware again I can't change the date inside.
???
-
Just leave 1.22 alone for now.
D-link has put it on the site too early, which I can understand because there has been a lot of impatience, and retracted it.
-
Here's a little insight.
Version numbers are for TRACKING of versions. That being said if we come out with a firmware version 1.22b01 and a 1.22b02 and the b02 gets posted, but is found to have a flaw we'll post the working b01 until we can either fix the flaw (1.22b03) or get a new firmware 1.23.
Please do not ask me what constitutes a new firmware or a build change, they NEVER tell me.
(I'm guessing it has to do with how far in to the code they have to go to effect the fix/change.)
We can NOT just change the numbers as that would skew our tracking process and also disrupt error reporting to our software people.
Hope this shed's some light on the situation for you guys and helps you to be less confused.
That might be a fair statement for internal operations but when I visit the support site to download the latest firmware I would suspect the binary to work without the need to pull it!
It just so happens that I downloaded the 1.22 [1/13/2009] version the other day and was going to install this weekend, its only because I had missplaced my download did I come back to the support site to download again only to find that the latest 1.22 is missing.
I do not believe I've seen firmwares treated this way by other vendors, please take note.
-
That might be a fair statement for internal operations but when I visit the support site to download the latest firmware I would suspect the binary to work without the need to pull it!
It just so happens that I downloaded the 1.22 [1/13/2009] version the other day and was going to install this weekend, its only because I had missplaced my download did I come back to the support site to download again only to find that the latest 1.22 is missing.
I do not believe I've seen firmwares treated this way by other vendors, please take note.
Lycan,
From I professional point of view I do not have great admiration for your Tech dpt.'s versioning process or release management. Please get them to read a book on it or something because their practices look kind of amateuristic. I would gladly help you guys out (free of charge).
-
Hey Eddie have you any idea when version 1.22 will be re-released again?
-
Nope, no idea. Shouldn't take too long, but the 1.21 is quite workable when tuned correctly.
Would like to do some testing for them before they put it out there. Haven't been able to convince them yet I guess :)
Your alias could need a nice avatar: (http://www.sevensheaven.nl/images/producten/cartoon-spotprent_wc-eend-duck.jpg)
-
Aww I cant see the image lol ;)
-
Aww I cant see the image lol ;)
http://www.sevensheaven.nl/images/producten/cartoon-spotprent_wc-eend-duck.jpg
-
Not to add to any discord over the ongoing fiasco over the 1.22 release, but from someone who actively sought out the DIR-655 from ''rave reviews'' by several sources as the best all around router for the money, and as someone who returned a freshly purchased and overpriced Apple Airport Extreme base station in exchange for it because the Apple unit was more expensive and was unreliable, I am a bit disillusioned that things have been so ''clunky'' thus far with my DIR-655.
The rather clumsy way that the 1.21 and 1.22 releases have gone remind me a bit of the MobileMe fiasco at Apple. There seems to be a relaxation in quality control, and when someone tries to point it out on the forums here, instead of understanding, they get the defensive attitude.
As for myself, after a heck of a lot of research and tinkering on my part post-1.21 firmware update, I managed to get it to work at least 90% of spec on a mixed Apple-Windows network--however--one should not have to ''hamstring'' something to get it to perform properly using less than optimal settings.
When the latest firmware update to 1.22 (the first posting) was reported I updated. There was no overt difference with when my 1.21 settings were kept. Then I was advised by a tech that there was an ''updated update'' of 1.22, so I then re-updated. Again, generally with my ''tinkered settings'' from 1.21, things seemed to be status-quo.
Thinking that 1.22 was a success, I decided to return the ''tinkered settings'' to what should be ''normal'' and optimal settings. Like many have noticed, not a good idea. I immediately re-imported my backed up 1.21 ''tinkered settings'' and to make this long story short -- 1.22 is a vapor update. Nothing better and nothing worse as far as I can see so far.
To use an analogy, if this was an automobile, yeah, sure it could drive, but it definitely would not pass state inspection.
Please guys in development, I know this is a down economy and perhaps your staff has been cut--and if this is the case, you have understanding and compassion--however, this might also be an opportunity for the ''proud few'' to shine and surprise us with a stellar firmware update that fixes everything and shows a ''can-do'' attitude.
A friendly nudge of encouragement.
-
http://www.sevensheaven.nl/images/producten/cartoon-spotprent_wc-eend-duck.jpg
They seem to be strict on cross linking. Therefore the solution: (http://www.citadel.nu/cartoon.jpg)
-
Ohh Love it lol!
Everyone look at my new avatar! :P
-
I hope this will sooth the firmware pains ;D
-
Would still like to request the ability to have client "ALIAS" in the wirless client information page.
As well, that feature for detecting new firmware has NEVER worked on my 655 here in canada.
I'm not sure how that would work, seeing as the .xml pushes to a specific code version and that product is international but has very different codes for different areas.
-
Lycan,
From I professional point of view I do not have great admiration for your Tech dpt.'s versioning process or release management. Please get them to read a book on it or something because their practices look kind of amateuristic. I would gladly help you guys out (free of charge).
I warned them of this. They felt that their actions were just. It turns out we didn't even find a problem with the code, our Taiwanese testing department found a potential flaw the day we posted it. Because we're trying to make every effort to avoid things like the 4500-esk issues from happening again our PM team agreed to pull the code.
We're supposed to have new code today, if i don't get something I'll repost the 1.22B01 as beta on the forums. ;)
-
It's a good thing the retraction action was taken if that one was (potentially) flawed. It does suprise me though the testing still took place when the decision to post the version was already taken. Seems there is not a "sure" sign-off procedure. One day extra does not make a big difference I would say.
PS: we got the 825 issue figured out. Like I suggested on the board, the modem was to blame, not the router :)
-
I'm guessing the flaw was caught before we posted it but because of the distance and time variance between here and taiwan, they probably just had a hard time getting the information to us in time.
-
I'm guessing the flaw was caught before we posted it but because of the distance and time variance between here and taiwan, they probably just had a hard time getting the information to us in time.
Time difference perhaps. Although a sign off on testing is a formal procedure. Non sign off, no release. Simple as that. You could initiate some groundbreaking work here on release management. Good career move ;)
-
So theres now been a firmware called:
121b11_beta02
Thats been released on the D-Link FTP, whats this firmware? Is it the beta of 1.22?
Im totally confused now! ???
-
I posted a 1.22b11 code. It's supposed to have the DNS Relay fix.
Try it out.
No Securespot.
http://forums.dlink.com/index.php?topic=3969.msg22296#msg22296
-
Just a typo, no worries
-
Will the 1.22 firmware fix issues with wireless restarts? I managed to get 1.11 to work without wireless restarts, but the thing reboots every 2 mins....will this firmware repair all of these issues? Would be nice. Thanks.
-
Here is what I don't get.
How long has D-link been around? At least a few years right? Really this question goes to any "strong" product manufacturer nowadays. It doesn't really matter who my query applies to, it's just that the way products are released today is completely baffling.
Why in the world would you release a product, onto a shelf, to an e-tailer, or any other way possibly conceivable, without it being READY FOR USE in ALL WAYS that APPLY to what that piece of equipment was designed to do?????
I can see a new firmware to add Securespot, and maybe even Shareport, although having the USB port already on the device without that functionality from the very first firmware is still ******ed if you ask me.
Can engineers not write machine language any better than that?? If they can, then how much do I have to pay in order to get a firmware that just FREAKING WORKS????
Or do I have to go to school and learn how to do it myself, I am more than capable, in order to get my Router to do EVERYTHING it was designed to do out of the box???
Even if the initial firmware is just to get the product on shelves, why release even ONE additional firmware release, IF IT ISN'T RIGHT?????
No offense to D-link specifically, it's just that most manufacturers are rushing products out that are nothing more than unfinished BETA products, and without any sort of break in price.
What gives?? Value is nowhere to be seen with the crapshoot of products available today, and it's clear that even paying more won't buy you a quality product.
If I hadn't been born into so many hurdles from the get-go, and had the means to be "handed" an education without having to fight and struggle for everything I have, BELEIVE me when I say that any company I owned or was head of engineering or technical support, would have your problems solved.
My team would do the job right, expeditiously, most importantly we would be able to sleep at night knowing that we did EVERYTHING we could do to help every last customer, from NOOB to L33T.
-
Before you go off yelling, I have a DIR-655 that has worked great from Day 1. I have had it well over a year. I have tried all the beta firmwares and never had an issue. I am also running the 1.22 that was pulled and I don't have any problems with that either. When you come to a forum it is usually for some kind of support and those are the issues you see, but I bet there are a whole lot more people out there that don't have problems becuase I think they have probably sold alot more units than just the people that come to the forum.
-
Is there today, or will there ever be a 1.2x that will work on all HW-versions.
I have today one A2 and one A3 version, and neither work with a 1.2x version. Different problems.
Maybe a question for Lycan to answer.
:-\
-
Before you go off yelling, I have a DIR-655 that has worked great from Day 1. I have had it well over a year. I have tried all the beta firmwares and never had an issue. I am also running the 1.22 that was pulled and I don't have any problems with that either. When you come to a forum it is usually for some kind of support and those are the issues you see, but I bet there are a whole lot more people out there that don't have problems becuase I think they have probably sold alot more units than just the people that come to the forum.
Same here. By now I've helped solving a crapload of user issues. 85% of those were NOT DIR655 related. Approx. only 1% of users come to the forum to seek help, not a platform to rave about 'how wonderful the machine is'. So considering this is aboutthe most popular routers around, the number of complaints and issues is really not that high.
-
Thanks Lycan for your unwavering commitment. I'm sure many of us here appreciate your efforts, though I can see how this can easily get lost amidst the complaints! ;)
While were at it....Thanks EddieZ. I still can't believe you don't work for D-Link! :D
-
Same here. By now I've helped solving a crapload of user issues. 85% of those were NOT DIR655 related. Approx. only 1% of users come to the forum to seek help, not a platform to rave about 'how wonderful the machine is'. So considering this is aboutthe most popular routers around, the number of complaints and issues is really not that high.
I would. Come here to rave about how wonderful the machine is. I rave all the time about how my Lanparty boards are ALWAYS tight from the get go. DFI doesn't release immediately, but they have a quality motherboard with top notch support over at the club.
So of course you won't here from too many people praising a product when the forum is filled with people booing and hissing in the first place, especially when the product being complained about was a rushed Beta with continual firmware issues that never really get ironed out for the majority. Stewpid issues that should have been fixed with the FIRST firmware released after what was shipped with the A1's.
Provide a firmware that actually seems to fix the issues for those who DO HAVE issues, and you won't hear from them anymore.
How is it going to help ANYONE by saying "well of course your gonna hear crybabies, that's what a support forum is for, crybabies for us to HAVE to listen to, nevermind their legitimate complaints/concerns"
If you provide support in a support forum, then DO THE DAMN JOB. Suck it up or find someone who can, or better yet if it isn't really your job, then stop doing it!
I was just making a generalized statement about what is to be found today, D-link's firmwares are VERY frustrating whether you want to admit that or not.
I am not currently having any issues with my A2, I pulled it out of the wastebasket, dusted it off, and gave it another shot. Seems to be working pretty good now, but by no means worth what I paid for it.
To be honest, if we didn't get the boy a PS3 for Xmas, and I had time to run copper to his room, then the A2 would still be in the pile waiting to be ran the F over with a John Deere 4WD. I also have a Creative X-FI, EVGA 790i Ultra, and an EVGA 780i in that pile. All gonna get ran over eventually.
I'll bet that if you went to EVGA's or Creative's support forums you would only find them full of people patting their respective support agents on the back all day long for how great those products turned out. ::)
Anyways.
When the 1.22 is released, would it be too much to ask for a descriptive explanation of what is actually being changed. Maybe some additional tuning tips, or what progress was made with the DNS Relay issues with percentages or test results??
I didn't think so. And that is why people will still *****.
-
In response to several recent posts:
This is a forum.
This is one of the typical places that those who purchased D-Link products come to canvas help and advice when they have some sort of problem they need to resolve.
That's thankfully what a forum like this provides for. It's a great self-help resource that hopefully helps cut down on traffic to the ''official'' technical support team.
Certainly some of the ''unfortunate few'' with problems perhaps go overboard and vent sometimes. They are frustrated. It happens. Be kind.
If you're not having problems, great, and I'm sure the ''unfortunate few'' wish we were you. They certainly want to be among you.
However, bashing those with problems is not helpful. It smacks of bitterness and gives me, at least, the impression of someone who has nothing better to do than to look for and to incite conflicts on a forum.
Is it appropriate to barge in on a group therapy session and yell at those with problems, ''What's wrong with you people?''
Is it too much effort to expect civility and understanding anymore?
-
I would. Come here to rave about how wonderful the machine is. I rave all the time about how my Lanparty boards are ALWAYS tight from the get go. DFI doesn't release immediately, but they have a quality motherboard with top notch support over at the club.
Good for you. Just a reminder: the DIR655 is a router (wireless, gigabit lan etc)
So of course you won't here from too many people praising a product when the forum is filled with people booing and hissing in the first place, especially when the product being complained about was a rushed Beta with continual firmware issues that never really get ironed out for the majority. Stewpid issues that should have been fixed with the FIRST firmware released after what was shipped with the A1's.
Provide a firmware that actually seems to fix the issues for those who DO HAVE issues, and you won't hear from them anymore.
You really have problems understanding my statement posted above apparently. And like you said: your router seems to do OK...
How is it going to help ANYONE by saying "well of course your gonna hear crybabies, that's what a support forum is for, crybabies for us to HAVE to listen to, nevermind their legitimate complaints/concerns"
If you provide support in a support forum, then DO THE DAMN JOB. Suck it up or find someone who can, or better yet if it isn't really your job, then stop doing it!
Have a look on the 655 forum and just count the number of successfully solved issues, and sort out the number of unique issues. You'll be surprised on how good a job all the folks on the forum are doing.
I was just making a generalized statement about what is to be found today, D-link's firmwares are VERY frustrating whether you want to admit that or not.
And you are ... The Only Truth?
I am not currently having any issues with my A2, I pulled it out of the wastebasket, dusted it off, and gave it another shot. Seems to be working pretty good now, but by no means worth what I paid for it.
Well, if it does all the things that are advertised quite well, you probably should have chosen a more feature-rich model
To be honest, if we didn't get the boy a PS3 for Xmas, and I had time to run copper to his room, then the A2 would still be in the pile waiting to be ran the F over with a John Deere 4WD. I also have a Creative X-FI, EVGA 790i Ultra, and an EVGA 780i in that pile. All gonna get ran over eventually.
I'll bet that if you went to EVGA's or Creative's support forums you would only find them full of people patting their respective support agents on the back all day long for how great those products turned out. ::)
So you're proposing that Dlink should be manufacturing motherboards and soundcards? Please compare apples with apples.
Anyways.
When the 1.22 is released, would it be too much to ask for a descriptive explanation of what is actually being changed. Maybe some additional tuning tips, or what progress was made with the DNS Relay issues with percentages or test results??
I didn't think so. And that is why people will still *****.
Have a look on the forum yourself, plenty of tips to work with. Or is that too much to ask? Anyway, the message of this thread was to report about the beta and the DNS relay issue. It seems to be resolved.
I can imagine that ranting on the board gives some air to frustration. Please do everybody a favor: write it down, post it and delete it again. This will give you the outlet you need and you don't bother other people with it. Shouting and ranting never impressed any manufacturer, and surely will not impress Dlink. All folks on the board try to be helpful and solve mutual issue. I, for one, do not have any appetite for personal frustration. Just leave 'm at home with the wife. ;D
-
Do to the FLAMISH nature of this topic I'm going to lock it.
Here's the end of this subject.
D-Link has designed, manufactured and marketed the BEST hardware you can purchase. End of story.
I've used them ALL. We have to. Pound for Pound the DIR-655 is the most stable platform we've ever had the pleasure of releasing. There are two caveat's to my statement.
1) This is a forum. Like any support forum you're getting the worst of the worst here.
If I showed the numbers of DIR-655's we sell every year versus the number of people that have actual problems with the unit (hardware failures or operator malfunction aside) it would be less the 5%.
So if we've sold 100,000 units thats 5,000 units with issues. Thats a guesstimation based on or replacement percentile.
2) This is also along with the understanding that everyone is complaining about a firmware that ADDS FEATURES. 1.11 is PERFECTION. If you want your router to work use that. If you want newer features, wait till we hammer the bugs out. Consumers act like because they've purchased a product, their entitled to free feature upgrades to that product years later. D-Link tries to accommodate to keep the product fresh and in the game, but we have other products that need to be developed and launched. If we're continuously adding features and expending resources to correct inherent issues with those features in an aging product we're not going to be in business long. That being said, please understand that I feel your frustration with the sequences of events that have occurred with the last several firmware launches.
We are a large organization and are slow to move because of the sheer size and people involved with any given product.
Please be patient and keep your eyes on the forums, I practaclly live here and I can get answers as quick as anyone.
I will be locking this thread. If someone feels I've wronged them in doing so feel free to PM me with a realistic reason of unlocking it and I will, however if I do this and you flame, I'll temporarily ban your account.
-Lycan.
-
I was just informed by my manager, that 5% is 4% too high. :) Apparently D-Link has a 1% failure rate and if it goes higher we take more imediate aggressive action.