D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: Lycan on April 28, 2009, 04:54:11 PM
-
For your routing pleasure. 1.31 in all it's glory.
NOTE: It's still a locked upgrade, you can not downgrade past 1.30 once a 1.30+ code is applied.
http://support.dlink.com/products/view.asp?productid=DIR-655
-
just going to say thanks Lycan.
You guys don't see that enough for all the S### you put up with.
-
So I assume this version has 802.11b support?
-
Just installed it and Yes, 802.11b is back in there. So far, so good. I will test out the VPN from the office tomorrow.
-
So far working great. B is back, but of course I have already disabled it. :)
Thanx Lycan!
-
So far version 1.31 is working great for me. Thanks for your hard work!
I found a javascript error in the 1.31 firmware. It's not serious, but I thought I'd let you know.
In Tools/Firmware.shtml
There's a javascript error looking for the ID main_content and it doesn't exist. This prevents the "Restart Later" button from working on the firmware page.
Sorry, it seems I am mistaken. I must have had the previous firmware's javascript cached or something. I cannot reproduce the problem now.
-
Download links for the firmwares are not active. Is this because of the reported problems thus far?
-
Links worked just fine for me.
-
Thanks Lycan for the all the work you do for us it is greatly appreciated!
-
Thank you for your work.
What can you tell about 3G modem support? Is it removed?
-
Anything is better than 1.30NA I can't use the wireless N.. I'll see how it goes with 1.31...
-
Thank you for your work.
What can you tell about 3G modem support? Is it removed?
You could take a look at the releaselog inside the download.
Or do you need a translation: "7. Remove the 3G from GUI"?
-
You could take a look at the releaselog inside the download.
Or do you need a translation: "7. Remove the 3G from GUI"?
Yeah, I really need translation. Removed from GUI ( Graphic User Interface ), doesnt always meen that something is not going to work. Also it can mean, it is hided somehow. Thats why i asked, is the support for 3G completely removed?
If yes.. It is bad thing, because it is the most important option for me, because in Finland we have 3G working everywhere and its very popular here.
P.S
"5. Modify the turn from "Network USB" to "SharePort" in the option of "My USB Type is:"
Please tell me what that exactly mean?
-
Well, if you can't turn it on (mode select) it doesn't work anymore. So removing it from GUI disables it. If you find a way to make it reappear...
-
Any reason why I should update from 1.30.
I don't need 802.11b. So basically is this just 1.30 with B put back into place.
-
AFAIK that is correct.
-
Will this also be released in a europeon version? If so is there any timescale on this?
thanks
TLE.
-
AFAIK the firmware will be Global, however I'll ask about the 3G for you guys on the other side of the pond. They may have plans to release a EU version with 3G, but don't quote me if they don't. Or get mad. Or swear at me. ;D
-
Awesome!!! New FW works great and now I can use my remote play function again!! Thanks guys for fixing this.... Until the next gen of handhelds have wireless g or n you'll alienate millions of of PSP and DS owners without 802.11 b. Glad you guys put it back.
-
Just one question: if I upgrade to 1.31 and 1.31 EU version comes out, will I be able to upgrade to it?
-
No problem. Same 'core'.
You can downgrade to 1.30, upgrade to any 1.31 (+) firmware. 1.30 and upwards have the same updated SDK/kernel. That is the reason you cannot downgrade below 1.30. Onze the cire has been updated, it's locked and other firmwares just would fail to work if downgrading was allowed. :)
-
Can anyone confirm that this has the securespot option please? :)
-
yes, it has secure spot
-
Toilet-duck : Yes it does.
-
Great, thanks updating now ;D
-
AFAIK the firmware will be Global, however I'll ask about the 3G for you guys on the other side of the pond. They may have plans to release a EU version with 3G, but don't quote me if they don't. Or get mad. Or swear at me. ;D
not just EU version... supposedly in Canada the Rogers Rocketstick worked great (yes on this router), it turned into an awesome option.
Seeing it gone removes a great option.
-
I'm sure a EU version would work for you guys as well.
-
not just EU version... supposedly in Canada the Rogers Rocketstick worked great (yes on this router), it turned into an awesome option.
Seeing it gone removes a great option.
Also, 3G network is available in Asia. Those products sold in Asia are labeled with "EU" serials at the back.
-
And what about 1.31 and Mac OS support? Is it working fine or disconnecting every 10 seconds just like the 1.30?
-
Will there be a version of 1.31 that does not have Secure Spot?
-
Will there be a version of 1.31 that does not have Secure Spot?
Ive never known why there are 2 versions of securespot and no securespot.
Doesnt disabling securespot in the router options, the same as having no securespot at all? Except that there is an option to enable it?
-
That's possible - I've been using the "No Securespot" FW previously, so thought I'd ask.
Ive never known why there are 2 versions of securespot and no securespot.
Doesnt disabling securespot in the router options, the same as having no securespot at all? Except that there is an option to enable it?
-
Upgraded... so far so good... but when I login to device, close that tab, open new and try to login, it fails. I close browser window, start browser again and it works until I again close tab... is this expected behavior?
-
Officially updated to 1.31. Shareport works, all nice and smooth.
-
Also, when I disabled graphical authentication, I was unable to login to router, it says that password is incorrect. I done hard reset of the router, same behavior. Graphical authentication in now on, but previously stated problem is still there.
edit: problem "solved", when enter password and hit [Enter], it doesn't work, I must click on Log In to successfully login to router.
PS Thanks Lycan for his fast response :)
-
Has anyone tried out the Wake on Lan port forwarding?
-
Its not going to work. The wol is on the broadcast adress and uses a simple ping to wake the computer.
-
I upgraded my firmware to 1.31 and it displays as 1.31NA - pretty sure it is NorthAmerican - if I not wrong. Well so far working great. Awesome..!!!
-
Shareport not working on Mac OS with 1.31, on 1.30 it worked with a lot of bugs and forcing me to force shutdown my mac.
-
Are the screens the same as previous versions? Would be nice to see some..
-
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).
-
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).
Yes but when copying files from LAN to Wireless the speed is the same as before.
I get up to 8,5 MB/s to a Thinkpad laptop with internal Atheros AGN PCIe card.
Also the DIR is showing 81 to 165 Mbit connection and only sometimes up to 240 Mbit.
-
I'm having a couple of problems with firmware 1.31:
1: Prior to the upgrade my wireless bridge (DD-WRT) and my Internet Alarm Clock connected fine using AUTO WPA and (TKIP and AES) settings on the DIR-655 (FW1.21 A2). Now the clock can't get an IP address and doesn't work if I assign one manually. I had to create a guest zone and set it to 128bit WEP to get it to work.
The clock is a Aluratek AIRMM01F Internet Radio Alarm Clock with Built-in WiFi.
http://aluratek.com/product_info.php?products_id=54&display=All (http://aluratek.com/product_info.php?products_id=54&display=All)
2: With both devices now connected wirelessly, under status --> wireless, the device on the WPA SSID is connected and works, but doesn't show an IP address. It shows 0.0.0.0. The device connected on the guest zone shows the IP address as expected.
These are the only problems I've experienced so far. I followed the recommendations on upgrading, resetting to factory defaults and restoring the previous config. I also tried resetting to factory defaults and manually reconfiguring with the same results.
-
I am a novice user just looking for consistency. I have noticed since upgrading to 1.31NA my connection drops often. I checked with my Internet provider and they are not showing my modem dropping off. When it does it is for a few seconds and comes back quickly. It is most noticeable on my VoIP which is wired. It is constantly breaking up and has become unusable. My desktop is wired and drops out as well. This is noticeable while streaming Sirius.
Are there settings I need to adjust? Keep in my I am very inexperienced with this. Unless I can get help I will be forced to get a new router. That would be frustrating considering problems were brought on by a firmware upgrade. If I understand correctly, I cannot go back to an earlier firmware version?
-
I have noticed since upgrading to 1.31NA my connection drops often
You're sure the router drops connection ? Did you look into the LOG ? What are the messages when connection drops ?
What kind of connection is in use ? Cable or DSL ?
Which Modem do you use ?
You reset the device to factory defaults after upgrade and configured it manually ?
Did you already try to set the WAN-Port speed to 100Mbps - not Auto ?
-
Enable QoS. Reserve the up adress of the voip box. Enter static entry in QoS, voice high.
If you run torrents you may want to give those boxes lower priority than 128, which is the default. I would be more discriptive but I hate replying on my blackberry. I'm afraid I may walk into on coming traffic, or most embarrasing into a pole.
-
You're sure the router drops connection ? Did you look into the LOG ? What are the messages when connection drops ?
What kind of connection is in use ? Cable or DSL ?
Which Modem do you use ?
You reset the device to factory defaults after upgrade and configured it manually ?
Did you already try to set the WAN-Port speed to 100Mbps - not Auto ?
-
Lizzie555, thank you for your help. I checked the log. The last entry is from Feb 28th and it is an IP being assigned. Am I sure it is the router? No. This problem just began shortly after the firmware upgrade to 1.31NA. I did check with my internet provider and they do show my modem dropping off. My next door neighbor with the same service is not having similar problems.
To answer your questions, my service is cable. I have a Motorola S85101 cable modem. No I did not, but will, reset the device to factory defaults after upgrade and configured it manually. I will set the WAN-Port speed to 100Mbps - not Auto.
As a side note, in the few minutes I typed this, the connection has dropped six times…
Not sure if this helps but here are my Statistics. They are current. I reset them two days ago.
Sent :155278
TX Packets Dropped :1
Collisions :0 Received :174339
RX Packets Dropped :0
Errors :0
WAN Statistics
Sent :167097
TX Packets Dropped :0
Collisions :0 Received :252426
RX Packets Dropped :0
Errors :0
Wireless Statistics
Sent :81454
TX Packets Dropped :1362 Received :29918
RX Packets Dropped :62
Errors :445
-
Wow...I was ready to make the leap from 1.21 (which has worked well) to 1.31...until I saw DavH's problems. Not being able to roll back if there are problems is really a killer. Will wait until more feedback comes in on the 1.31.
-
your statistics looks OK there are no errors.
With a cable modem try to connect directly after the reset with manufacturer settings.. It should work.
If your modem still drops connection try the settings I mentioned above.
Perhaps coincidentally the modem broke at the same time you updated the router ;)
-
The bottom line is simply that more than enough erroneous error's exist with customers regarding this firmware update to prevent the rest of us from upgrading to v1.31.
I was excited to find out about the update, especially with a version of the SharePort software for the Mac platform. However, after reading all of the existing threads for this post, I have no interest in upgrading/breaking my currently working Non-SecureSpot v1.21 firmware.
In my humble opinion, my recommendation having 20+ years in IT, and holding nearly two dozen industry certifications would be to allow qualified testers who do not need their router for a primary internet connection to more thoroughly test the firmware and provide ample feedback before the rest of you upgrade.
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.
And in closing, we all appreciate the engineers hard work, but bugs in the code are inevitable. Hence, ...allow for appropriate testing and feedback before upgrading. And what I mean by that, is feedback here in the forums. Don't rely solely on D-Link's QA department to find all the bugs. They only look for major failures, as there is no way to duplicate every persons use and or setup outside of D-Link.
Respectfully,
Tommy Lee...
-
Ok Lizzie555. I did a reset to manufacturer settings then manually configured wireless security. Although it has only been 10 minutes or so, all is well.
I am going to be positive and say this did the trick! If not, I will be sure to post. Thanks again for you help.
Are there any settings you guys suggest a nontechnical person like myself (but not afraid to learn and try) do to enhance this router's performance and capabilities?
-
I applied 1.31 to my DIR-655 A3, upgrading from firmware 1.21 in the process, and now my router reboots every single time it establishes a connection to my ISP. My DIR-655 goes through a 2wire 2701HG-B DSL modem which is set in bridge mode. I've had to remove my DIR-655 from the network entirely, and I'm using the DSL modem's wireless feature in the interim.
Did 1.31 screw my DIR-655?
-
I am a novice user just looking for consistency. I have noticed since upgrading to 1.31NA my connection drops often. I checked with my Internet provider and they are not showing my modem dropping off. When it does it is for a few seconds and comes back quickly. It is most noticeable on my VoIP which is wired. It is constantly breaking up and has become unusable. My desktop is wired and drops out as well. This is noticeable while streaming Sirius.
Are there settings I need to adjust? Keep in my I am very inexperienced with this. Unless I can get help I will be forced to get a new router. That would be frustrating considering problems were brought on by a firmware upgrade. If I understand correctly, I cannot go back to an earlier firmware version?
WARNING TO THE DEAR READER: OK, long post here so I can include some background details for you. I'm hoping this helps point out there are some issues in this firmware and compatibility with speed negotiation.
I understand exactly what DaveH has mentioned here. The same thing happened to me with the upgrade. I was actually a couple revisions behind on my 655 router (1.20) when I noticed my logs indicated DLink had firmware upgrades. For now, I'm wired directly and have the wireless disabled. I was very concerned about making the jump to 1.31 when it said "not reversible" (How dumb on my part for moving forward. How REALLY dumb of Dlink for putting such a mess out there - debate this later).
Something kept me from being able to hit the Net yesterday, so I had to reboot everything (modem, router, voip, computer) and started combing the logs of my router when it came back. I found nothing indicating the trouble and attributed it to a lost modem carrier link from upstream. (We had strong winds the previous evening, so maybe something happened to the lines along the way.) I could see a message indicating there were firmware upgrades waiting from Dlink. I was finally able to get thru to the Net and DLed both 1.21 (dir655_firmware_121_no_securespot.bin) and 1.31 (dir655_firmware_131.bin).
I applied 1.21 first and no issues showed up, so I moved on. My problem started immediately after the upgrade to 1.31. My browser (firefox) kept dropping back to a page telling me the router was testing the speed and that I should wait to avoid impacting the test. Well, there was nothing I could do to it anyway and was forced to wait. The login screen appeared for getting back into the router and I had a really hard time getting the correct letters/numbers on the new GUI addition before the "testing" page would come back up. Each time the testing began, I would actually see the router reboot/reset itself (all the lights on the front panel would blink off and come back like a reboot). I had my setting saved on my computer for the router, so I thought I needed to hit the "reset" button and get a clean start. It didn't make a difference. I finally had to disconnect the router from the modem to stop the testing so that I had a chance to get into the router interface.
I looked for all the spots I could find to disable automatic speed testing. I disabled the new security GUI feature first. I ended up turning off the traffic shaping and automatic upllink speed testing and set a LOW manual uplink speed. I'm using Road Runners Turbo package that is supposed to be 15M down/ 1-2 up, but I set the speed to really low (384Kbps). I searched for other things I could turn off and think I even tried turning off the QOS engine completely. This seemed to stop the problem, for now, and I could get back online. It was important to get connection as my only phone right now is VOIP. :-)
Finally got thru the extremely annoying front line RR support and got a 3rd leve guy to the phone. We verified that my cable modem was the one model they had in the field that did NOT support turbo speeds (nice!! - never told me this 6 months ago when I upgraded to turbo) and I should return it for an upgrade. Everything else tested fine along the line and they did not have any reported outages or issues for my area. Hmmm. Well, SOMETHING happened somewhere as I was dead Thursday. Moving on, I was able to use the Net and VOIP for the rest of the evening and switched the modem out today.
Intially I left the setting alone on the router and just tried to hit the Net. Connections to a few sites worked ok. Then I went back to using the traffic shaping and automatic uplink speed testing and I had my connections between the router and modem start acting up again. The router wasn't restarting this time but I could see my network icon in the tray indicating I lost network connectivty to the modem. Nothing would resolve in DNS for the websites (page not found) until I changed these settings and rebooted the router. I am running now with the QOS engine back on, traffic shaping allowed, but have manually set my uplink speed.
I know this was a long post, but I wanted to get this information out there so others can possibly explore the same thing. Better yet, I hope Dlink admits they still have issues out there and need to address immediately.
Good luck, gang.
-
Unicks,
You must understand that the problem that you're seeing is unique to you or even a small number of people and not likely a problem with the firmware.
If it was a problem with the firmware everyone that was using it, with RR-Turbo would see this issue, right?
As for your problem, I suggest resetting the unit to factory adn configuring it from scratch. If that doen't help contact technical support.
-
just installed on my A3, and works fine.
But i have 2 questions:
- Does anyone know if the 3g suport will be 'recovered' (maybe on a EU version of this firmware, i'm in Portugal, and 3G Internet, is very used around here. I think is a bad decision to remove the support, at least on Europe)
- 1.1x firmware is related to A3 revision. 1.2x is related to A4 revision. With 1.3x are we expecting a A5 revision?
-
Im hoping the 3g option will be added back later too with the next firmware update, I sometimes take my router with me when I go away and use the t-mobile usb dongle to connect.
But this latest firmware for this is really stable havent had 1 crash and reboot since I updated it, use to keep needing a reboot every few days after I used it for a week but this latest firmware seems to fix it :)
-
^LOL! I guess you should have gone with 'USB Doohickey'. ;)
-
Unicks,
You must understand that the problem that you're seeing is unique to you or even a small number of people and not likely a problem with the firmware.
If it was a problem with the firmware everyone that was using it, with RR-Turbo would see this issue, right?
As for your problem, I suggest resetting the unit to factory adn configuring it from scratch. If that doen't help contact technical support.
I guess u missed my point, Lycan, that was written above (even if it was lllllloooooonnnnnggggg):
I DID RESET and also reloaded my settings. It had NO impact. I had NO problem until I went to 1.31. This did not surface in the other versions. Repeat: I never saw anything like this until I uploaded 1.31. Is it a settings issue? Great, then school everyone on where we have it wrong. No shame there. It is not the fault of the modem as it was replaced (different model even) and the problem stayed. I got the problem to repeat with settings that were just fine before. ???
I know this isn't just my issue as I see others here have described the SAME behavior. Technical support has no interest in my case as I have no warranty / contract with them. (Their position on the probelm, not mine).
This isn't the case of a "lost" user and single case just because not everyone hasn't see it (yet). There are others who are reporting the problem and I know we are not all using the identical ISP and hardware. :o Break, coffee, discuss amongst yourselves.
-
I'm having almost the exact same issue as unicks is experiencing. This is not an isolated or unique issue.
-
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.
-
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.
-
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.
-
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
-
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...
-
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.
-
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?
-
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.
-
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.
-
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
-
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...
-
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.
-
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.
-
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.
-
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
-
You seem to flaunt with your certifications and experience. Well, that does not make you a 'good' IT guy...
But anyway, comparing with a Cisco PIX is like comparing a Ford sedan (consumer) with a Mack (PRO).
Your claim as to the stabilty of 1.21...I do not know where you did your testing, but it is regarded by the majority as the worst firmware after 1.11... So hearing your qualification of 1.21 is surprising to say the least.
The issues reported are incidents. As an experienced IT guy (just following your logic about certifications for a moment) you would know that 5 complaints do not make a priority issue. Certainly not when you have no insight in the local configs. A malfunctioning restoration of saved config is quite common (see BIOS update manuals) and it is a preferred method to config from scratch (factory default). Solving issues is not about the odds. Refusing to look in different directions because of the odds does not suit an IT pro. Because the best thing in IT is simplicity: Either the firmware causes issues which are generic (all equal devices) and should be reproduceable or there are other factors causing the issue, not being the firmware.
Example: NTP server issue. I cannot reproduce it at home. The given NTP server just works fine. No reboots, no loops. Howcome? If it's the firmware I should be able to reproduce.
Example 2:
The only issue I could reproduce was reboot loops after restoring a saved config.
So thanks for your elaboration on...well, mainly yourself.
Let's try to fix this guys issue.
Generic steps would be:
1. reflash 1.3x
2. Reconfigure manually after setting tho factory defaults.
3. reset your internet gateway device
-
Your claim as to the stabilty of 1.21...I do not know where you did your testing, but it is regarded by the majority as the worst firmware after 1.11... So hearing your qualification of 1.21 is surprising to say the least.
The issues reported are incidents. As an experienced IT guy (just following your logic about certifications for a moment) you would know that 5 complaints do not make a priority issue.
We upgraded to 1.21 and we run a macbook pro, a PC with XP SP3, Canon MP wireless printer and Ipod Touch all problem-free since the upgrade. Before we had 3-4 dropouts a day. My only need to upgrade is for a version that supports shareport and macbook pro. See the Mac thread for problems there.
We recently swapped companies from a 6 Mbs ADSL service to a 20 Mbs Cable , so this firmware has been running on different services with different modems, speeds etc.
Lastly, if I check on D-Link Germany, 1.21 is the most up to date official firmware. Not 1.22b, not 1.30 or 1.31. The official seal of approval by D-Link Germany is for 1.21, so if it is so bad as you say, why has it not been returned to beta, as 1.30 was so quickly, If the "majority" have so many problems with it?
-
You seem to flaunt with your certifications and experience. Well, that does not make you a 'good' IT guy...
But anyway, comparing with a Cisco PIX is like comparing a Ford sedan (consumer) with a Mack (PRO).
Your claim as to the stabilty of 1.21...I do not know where you did your testing, but it is regarded by the majority as the worst firmware after 1.11... So hearing your qualification of 1.21 is surprising to say the least.
The issues reported are incidents. As an experienced IT guy (just following your logic about certifications for a moment) you would know that 5 complaints do not make a priority issue. Certainly not when you have no insight in the local configs. A malfunctioning restoration of saved config is quite common (see BIOS update manuals) and it is a preferred method to config from scratch (factory default). Solving issues is not about the odds. Refusing to look in different directions because of the odds does not suit an IT pro. Because the best thing in IT is simplicity: Either the firmware causes issues which are generic (all equal devices) and should be reproduceable or there are other factors causing the issue, not being the firmware.
Example: NTP server issue. I cannot reproduce it at home. The given NTP server just works fine. No reboots, no loops. Howcome? If it's the firmware I should be able to reproduce.
Example 2:
The only issue I could reproduce was reboot loops after restoring a saved config.
So thanks for your elaboration on...well, mainly yourself.
Let's try to fix this guys issue.
Generic steps would be:
1. reflash 1.3x
2. Reconfigure manually after setting tho factory defaults.
3. reset your internet gateway device
EddieZ, ...where to begin,
No one is flaunting here. D-Link needs to know there are users out here that are actually IT professionals in the industry. Not just hobbyists at home tweaking things in there spare time, whose day job may not even be IT. And in knowing so, realize that we (the IT professionals), will not be lulled over by simple statements like thousands of 655's have been sold, and there are only 10-problems out there (supposedly), so it must be the user and not the firmware. Even if the only problem that existed was the reboot issue you spoke of, and it could be completely cleared by starting from scratch as you say, a problem still exists that should be rectified.
Additionally and based on your response, it would seem that everyone else in the forum is inept at successfully configuring a working DIR-655, all because your router works with no problems according to you. Where is the logic in that? Better yet, where is your so called IT professionalism in that?
The bottom line is, v1.31 does have problems. Be thankful you got the luck of the draw with a combination hardware revision/firmware installation that luckily enough didn't happen to cause you any issues. However again, just because your router works according to you, it in no way means that firmware v1.31 is utterly and totally without issue. I have never worked for D-Link personally, but I have worked in QA throughout my career, and I am well aware of how things are pushed through to make deadlines. If known dev issues are considered to not be fatal, or show stoppers so to speak, then the company pushes forward with the changes hoping for the best, or at the very least, to deal with them another day. The only problem is far too often, those non-fatal issues are never revisited and or resolved, leaving the customer to simply deal with them.
I also agree that we should try to help people in this forum, like "desides" for example. However advising them to perform the same repetitive steps over and over, I guess until they eventually work? ...does not constitute helping anyone in my opinion. Especially when the only true help is going to be a rectified revision of the firmware, or at least an unlock revision to allow down grading back to v1.21.
Respectfully,
Tommy Lee
-
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...
I used measurements on my laptop in the same room and there was a real difference in downloading speed while navigating between 1.11 and 1.22 on A2 hardware.
-
I used measurements on my laptop in the same room and there was a real difference in downloading speed while navigating between 1.11 and 1.22 on A2 hardware.
I measured and tested too. 1.22 gave exactly the same throughput as 1.11, but had to reconfigure the antenna setting somewhat. The radio seems a bit more sensitive after 1.11 which changed the optimal position. 1.31 is the best so far with actual throughtput and transfer speed.
-
I measured and tested too. 1.22 gave exactly the same throughput as 1.11, but had to reconfigure the antenna setting somewhat. The radio seems a bit more sensitive after 1.11 which changed the optimal position. 1.31 is the best so far with actual throughtput and transfer speed.
Thanks for the information. May be I'll try 1.22 again to test antenna position before moving to 1.31
-
Could anyone that was having issues with 1.22 dropping during bittorrent downloads post if 1.31 fixed the issue?
-
Here is my take; an average PC user. I had issues when I initially upgraded to 1.31NA. Thanks to this forum I learned the correct way to install and make it work, so I thought. No longer do I have consistent connection drops on either wired or wireless devices. However, my VoIP that worked flawless prior to upgrading to 1.31NA does not work. It cuts in and out and is now unusable.
As a test, I wired my VoIP directly from my cable modem (not even involving the DIR655 in the equation) and it worked perfect. I made a 30 plus minute call. Absolutely no quality issues on my end or the receivers.
I have been reading the comments form IT professionals and D-Link moderators going back and forth. It has been entertaining to say the least. Bottom line is since I upgraded to 1.31NA, my set up (cable modem to DIR655 then one hard wired PC and one hard wired VoIP) that worked prior is no longer working correctly. I have always done firmware upgrades. How silly of me upgrading to a firmware that was issued by the manufacturer to presumably improve and enhance their product. All while assuming it was issued so an average, non-IT pro could install and enjoy the benefits without spending hours on a forum to get it to work!
Ok, so I am having problems. I can understand stuff happens. I am sure D-Link will address these issues and make corrections eventually. But why the hell do they no allow the user the option to fall back to a prior proven firmware that worked in their specific case?!! They have eliminated an escape route. This is just plain ignorance. That is what frustrates me most. Yes they had a disclaimer written in red you cannot go back. But again, I trusted it would work. Lesson learned. I will now let others try it and what for feedback.
I am not here to get into a pissing match. I just want my internet and VoIP to work properly! Does anyone have suggestions on how to make this happen? Can I go cable modem to VoIP then to DIR655? If so, are there any drawbacks. Guess I could go try that. Or maybe I'll go purchase a new non D-Link product. That would be a shame up considering I loved the way it worked prior to this mess.
-
Can you provide an overview on your QoS (and WiSh) settings?
-
Whatever the default setting are, those are my settings. I have not played around with those settings in the six months I have had the router. If you still need specifics, I can will get that for you.
-
I didn't read every detail of all the posts, but for those having issues... have you attempted a re-download of the firmware and then another "30/30/30, flash, 30/30/30, manual setup"?? I'd suggest at least doing that again if you're having issues to maybe remove any corrupted data in the download or a possible "bad flash".
Also, as a general comment... not all hardware is equal and while I would think most people are doing just fine with 1.31 I would also think that some people would have issues with 1.31 as well. Since I didn't write the firmware I can't say for sure, but maybe this firmware is stressing certain parts of the hardware differently over 1.21, 1.22b05, etc.
Computer hardware is an interesting thing. While the same people who had issues with 1.21 are now singing the praises of 1.31... others that had no issues with 1.21 are now denouncing 1.31 for giving them huge headaches.
So (for the ones having problems and if you haven't already tried it) if it was me I'd try to re-flash my router again with 1.31... I'd also try 1.30 just as a test to see if the same issues were there.
**On a side note (I know we've been told the "reasons", but)... I'd like to know why exactly we can’t downgrade to an earlier firmware. I of course don’t know what all the properties of the chips inside the router are, but if we’re talking any type of flash ROM that was obviously able to be changed to “lock out” a downgrade… then why can’t that same chip be changed again to allow a downgrade?? Is this a “write once” type of memory that was changed with 1.30/1.31 and now we’re locked to that code no matter what???
Please explain in detail exactly why we can’t downgrade… because from everything I know about hardware there should be no limitations so it VERY much appears to be an artificial software limit imposed by D-Link even though the hardware could still be “re-flashed” with the old code.
-
Whatever the default setting are, those are my settings. I have not played around with those settings in the six months I have had the router. If you still need specifics, I can will get that for you.
Default is "no settings".
And for teknomedic: the 1.3x firmware has a new SDK or Kernel update. Once installed, it locks the new codebase (kernel) in the device. Since the older firmware requires a different kernel (the old kernel) it is not downgradeable. Can't go into more details.
Ofcourse one can say "there is always a way..." but believe me, you don't want to go that road.
-
And for teknomedic: the 1.3x firmware has a new SDK or Kernel update. Once installed, it locks the new codebase (kernel) in the device. Since the older firmware requires a different kernel (the old kernel) it is not downgradeable.
I understand that part... what I'm trying to figure out is just why the hardware can't be reflashed with the "old kernel". Is it because it's a write once type of memory (which I wouldn't think as it would mean only one update like this could ever happen)??... or is it because the older firmware files don't include the full kernel update code (in which case a v1.21 with full kernel update could be released).
Simply saying that it's a new kernel doesn't fly with me (and others from what I've read) unless there's some physical reason the hardware can't be changed.
Let me put it this way... even though I'm running Vista and can't run anything from Win98... I could still reformat my hard drive and put Win98 onto my computer (a vastly older kernel). So please tell me why we still can't reformat our "hard drives/routers" and put the v1.21 kernel back on???????
-
I guess what I'm trying to get at is this:
IF D-Link simply wanted to lock us out from using anything older once we upgraded then fine... but then it's ONLY a software lock as I would assume all the chips in the router would be of the "rewrite or CD/DVD RW" type and not the "write once or CD/DVD R" type. In this case I would much prefer D-Link to simply say... "because we didn't want you to use anything older so we locked you out".
BUT...
IF it's an actual physical limitation of the hardware (or earlier firmwares), then I'd like to hear the WHY and WHAT of the physical limitations. (ie, write once flash, v1.21 or earlier don't contain the kernel update codes, etc).
....I've seen them do similar things with motherboard BIOS chips, where it won't let you downgrade, but it's just a software lock imposed and not an actual physical one as (I've done it in the past) I can simply remove the chip from my motherboard.... place it into my EEPROM programmer and re-flash an older BIOS and it works just fine. So obviously there's not a physical limit, but a software limit imposed by the maker.
-
I guess with this new version they performed a full flash instead of a code flash, and flashed the bootstrap with a new version.
More then likely the old firmware flashers don't recognize the new bootstrap and refuse to flash it, or the old code does not work with the new strap.
-
@teknomedic; Go and write a nice friendly email to Dlink tech department if they want to share these tech details with you (to which you're not entitled by default, just in case this argument might come up). If you want to have a "but what if you ... (go and change the old firmware with the new bootstrap etc)..." discussion with them be my guest.
Ubicom has released a new kernel (improvements???) which has been implemented by Dlink. It's just the way it is.
@ominator: you're close...
-
EddieZ... from what you've posted you seem to be claiming to know the "true" reason so why not share it with us, or have you signed some form of NDA recently?
-
I guess with this new version they performed a full flash instead of a code flash, and flashed the bootstrap with a new version.
More then likely the old firmware flashers don't recognize the new bootstrap and refuse to flash it, or the old code does not work with the new strap.
That's the point I'm trying to make. If that's the case then I (as well as others it would seem) would much prefer D-Link to simply say that instead of some PR "bull".
-
EddieZ... from what you've posted you seem to be claiming to know the "true" reason so why not share it with us, or have you signed some form of NDA recently?
The things I've shared is all I know, I'm really not that into coding and stuff so I do not know the tech details of that kernel upgrade. But as far as I can trust my sources this is the actual reason for the downgrade limitation. This is what happens when the marketing dpt has control :o
-
Fair enough... I'm not that into coding either, but from what I've learned by programming/flashing many chips and hardware from my little EEPROM programmer as well as what I know about hardware in general it seems that D-Link was simply spouting some "PR fluff".
-
Fair enough... I'm not that into coding either, but from what I've learned by programming/flashing many chips and hardware from my little EEPROM programmer as well as what I know about hardware in general it seems that D-Link was simply spouting some "PR fluff".
Indeed a bad call.
-
Is it just me or why can't I find the 1.31 Firmware on DLink Website anymore?
-
Is it just me or why can't I find the 1.31 Firmware on DLink Website anymore?
Yeah, I don't see it. Has it gotten take down again? Seriously dlink?
[Edit]
NVM,
If you got to this address it doesn't show it.
http://www.dlink.com/products/support.asp?pid=530&sec=0#firmware
However, this one does:
http://support.dlink.com/products/view.asp?productid=DIR-655
-
The unit comes with 2 types of on board storage. 16MB Flash RAM for system settings and configs as well as the statetable, and an EPRom of unspecified size. Obviously the EPRom is where the code known as the OS for the unit (IPoS to be exact), is kept.
When the kernel to the OS is updated a section of the EProm is changed. This is WRITE memory that is non-volatile. My guess is UBicom felt there was a significant enough change in the SDK that allowing downgrades from this new SDK could possibly damage or destabilize the unit. Normal firmware upgrade allows for the "addition" or DELTA of the firmwares to be applied. The CODEBASE is not re-written. When the SDK goes through a upgrade, the entire EPRom is re-written.
This isn't the first time we've done this, I believe this is the 3rd for this router. The 4500 also saw an upgrade like this (although that was a tragedy).
Moving on......if you believe that the firmware is causing your unit to fail, contact technical support, request that they assist you with your issue, and if not resolved request a replacement unit. You can even go as far as to request a unit with 1.21 if you like.
I'll close in saying this. There is nothing currently wrong with the 1.31 firmware from a preformance standpoint. There as some small java problems with the code that effect the UI, mostly involving some quirks with captcha.
I do not doubt for a second that upgrading the firmware on your router may ave caused it to malfunction or operate poorly, however please understand that it is not the code's fault. It IS however a combination of that code, your router and your environment. The unfortunate side is because the codebase is locked, you're extremely limited on what you can try as far as troubleshooting.
I appologize to all the 655 owners that are suffering with a unit that is not performing up to par.
-
Thank you Lycan - personally I really appreciate, not only the information, but also the honesty in your reply.
-
As do I Lycan.
-
Yeah, I don't see it. Has it gotten take down again? Seriously dlink?
[Edit]
NVM,
If you got to this address it doesn't show it.
http://www.dlink.com/products/support.asp?pid=530&sec=0#firmware
However, this one does:
http://support.dlink.com/products/view.asp?productid=DIR-655
Yea, I went to follow the links on www.dlink.com. Haha, still not sure if I should make a move to the new one or not yet lol. ;)
-
Firmwares are downloaded from support.dlink.com
I'll check in to the links provided at dlink.com.
-
speaking of firmware download and stuff alike, the A2 here in canada, has never ever reported new firmware version since 1.10. Don't know what that is all about but I guess it doesn't work in Canada? Never reported it before, well once actually, only because it's not a big deal. :P Since I havn't made a post in a little while I thought to write this. anywayyys. tootaloo.
-
NA = North America, I'm guessing according to D-Link's view Canada is part of NA. ANNEX TIME! lol j/k.
-
how is the 1.31? is it faster than older firmwares?
someone do a benchmark!
-
NO real speed difference noticeable. There have been no new changes to the radio part and the transmit power was already maxed (100 mw for legal reasons). But it seems to be quit stable.
-
speaking of firmware download and stuff alike, the A2 here in canada, has never ever reported new firmware version since 1.10. Don't know what that is all about but I guess it doesn't work in Canada? Never reported it before, well once actually, only because it's not a big deal. :P Since I havn't made a post in a little while I thought to write this. anywayyys. tootaloo.
Well, I'm a follow Canadian and installed the 1.31 without any issues on my A2. If you take a look on the Dlink.ca site, you'll see the 1.31 is there, same as the US site. HTH.
-
Has anyone had experience with 1.31 firmware on an A4 unit? If so, can you compare now against any prior 1.2x firmware with the unit?
-
On my A4 was using the original 1.20 until a couple days ago. Noticed an improvement in wireless performance, much less Errors and Dropped Packets, otherwise, same...
-
Hi,
Some interesting thread here.... I like many other users of this forum have been looking to make a decision to upgrade my firmwware (or not) in hopes to improve stability or performance (hopefully both), and am not flummoxed by the debate, in case I am also one of those people whose router and environment might evoke the problems that others are seeing;m rather than a nice simple update that the other others have seen....
As to the wireless signal drops and such that have been reported from the update to the 1.31 firmware, I would likely concur with what others have said about the new firmware perhaps stressing the hardware in some slightly different way that is pushing individual units into some type of instability scenario(s). I saw this PLENTY with my old Netgear (WGT-624) unit from some sort of overheating of the wireless chipset, and I assure you Their user forum was littered with complaints form folks who were having the same types of issues, not just 5 or 10....so much so that netgear eventually took down their forum "for upgrades" and seemingly months and months of forum threads "went away"....
To that end, i chose the Dlink unit because they had a better "rep" than what I saw with netgear. I used what I learned in working with my Dlink.... Use a vertical orientation, in that it aids with internal heat flows / transfer... I always run my router off a battery-backed up powerline (implying a certain amount of voltage stabilization).... and I run my VoIP box in between my cable modem and my 655, rather than stringing it off the 655, then I set up a DMZ inside the VoIP box for the router's IP.
Just my .02
Dave
-
Hello everybody!
I had mistakenly updated my 1.21EU firmware to 1.31NA. And my biggest problem is, that the EU version hasn't released yet. So far, I am experiencing problems with 1.31 :S Okay, I know, stupid me...
So here is my problem: After I updated my firmware, sometimes I cannot access the internet, and my router's config page too. After that happens I press on the router the Refresh button, I disconnect, then reconnect, and it's working again.. But it happens hourly sometimes, or often than that.
I have a notebook with wi-fi, with cables the problem doesn't occur, but I am living with flatmates, so it would be very difficult to use cables.
I did a 30-30-30, and reinstalled the 1.31 firmware, but it didn't solve the problem.
What should I do? Is there a non-Europe 1.31 firmware, that is compatible with my device? Oh yes, I forgot to mention, that I have the A4 version of the router.
Thanks for your reply in advance!
(And sorry for my bad English...)
-
EU and US (NA) version do not differ (apart fro extra languages).
-
But the product's support page says:
This firmware is engineered for North American products only.
Using this firmware on a device outside of North America will void your warranty and may render the device unusable.
-
Try the new 1.32NA beta version.
It is working fine here in EU with Cable Internet and a "normal" ADSL modem too.
In the moment there is no other firmware you can use as you can't downgrade to a 1.2x version.
-
Is there a new version? Where can I download it?
I can't find here (http://"http://support.dlink.com/products/view.asp?productid=DIR%2D655").
Thx for your quick replies :)
-
http://forums.dlink.com/index.php?topic=5841.0
-
Is there a new version? Where can I download it?
I can't find it here (http://support.dlink.com/products/view.asp?productid=DIR%2D655).
1.32NA is still beta firmware at the moment which is why you won't find it listed on the main support page.
-irrational john
-
Thanks :) I hope this solves the problem..
-
When can we expect a 1.3x version for Europe?
-
Unless you really need the extra languages the only possible extra item could be 3G support on the EU version. So if your English is OK and you do not need 3G you can use the NA version .
-
Unless you really need the extra languages the only possible extra item could be 3G support on the EU version. So if your English is OK and you do not need 3G you can use the NA version .
OTOH, if he installs it and finds out it does not work for him because of something he overlooked, then he's pretty much stuck with a pet rock instead of a router, no?
Ah, the joys of non-reversible firmware installation ...
If it were me, I'd wait. And ***** ... err, complain? (who knew that a common name for a female dog would be on the banned list?).
-irrational john
-
I'm in Europe and have never loaded any other firmware than NA versions. There is only one global hardware device (with revisions). Don't let them scare you.
Only precaution (not EU/NA version related): downgrading is not possible when you upgrade to firmware version 1.3x. So beware...
-
Moving on......if you believe that the firmware is causing your unit to fail, contact technical support, request that they assist you with your issue, and if not resolved request a replacement unit. You can even go as far as to request a unit with 1.21 if you like.
I'm glad I came to the forum and found this, I have been running great since last october and the last I had before 1.31 was 1.21 and I was getting 16mb down wireless and wired, went to 1.31 and could not get above 4mb wireless, signal fluctuating bad. Tried all kinda of settings, nothing. I went to 1.32 beta and even worse. I had to pull the router. I have been a member of dslreports since 01, went there first and found a bunch of people that had to pull theirs after upgrading. If dlink wants to deny there's a problem, fine just give me a replacement with 1.21 and I'll be happy fixing the "non" problem.
-
It seems that there was a lot of info put out since the 1.31 with the 2 betas that followed; however, now it seems as though we have been forgotten after spending $100-$130 for this router. What are we to do? Will there ever be a firmware update released to fix this issue? Very many folks are upset about this and yes, the easy answer is to just buy another router. Why should we have to? What about exchanges or refunds for those of us (many) that are affected?
-
Try these settings for the beacon period, rts threshold and fragmentation threshold, the rest are what I use and have always used. I'm not getting 300, but 130, where I got 300 before, but my speed has camu up some and the signal more stable. I still wish I could go back to 1.21, it was much better.
Transmit Power - High
Beacon Period - 80
RTS Threshold - 2100
Fragmentation Threshold - 2100
Dtim Interval - 1
802.11 mode - n only
Channel - 11 (or other)
Transmission Rate - Best (Automatic)
Channel Width _ Auto 20/40
Security Mode - WPA-Personal
WPA Mode - WPA2 Only