D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: ceed on June 17, 2009, 10:11:15 AM
-
Hi,
Since I upgraded to 1.3x firmware I have not been able to store port forwarding and application rules. Some, or all of them simply aren't there after the reboot. One port forwarding rule is saved, but that one can't be removed or changed. I have tried to reset to factory settings, but no go. I really wish I could go back to 1.2x firmware.
D-Link, please fix this asap!
-
Hi,
Since I upgraded to 1.3x firmware I have not been able to store port forwarding and application rules. Some, or all of them simply aren't there after the reboot. One port forwarding rule is saved, but that one can't be removed or changed. I have tried to reset to factory settings, but no go. I really wish I could go back to 1.2x firmware.
D-Link, please fix this asap!
http://forums.dlink.com/index.php?topic=5338.0
Same problems there and something to do with securespot..
-
http://forums.dlink.com/index.php?topic=5338.0
Same problems there and something to do with securespot..
Thanks. That thread seems to be dealing with two problems. The one I have are mentioned in the thread, but I can't see a solution other than disable upnp-rebboot-enable upnp-reboot the router. There's something wrong with the 1.3x firmware with regards to both forwarding and applications rules since they can't seem to be saved. I have another DIR-655 at my office with 1.2x firmware. No such problems there.
-
Hi,
Since I upgraded to 1.3x firmware I have not been able to store port forwarding and application rules. Some, or all of them simply aren't there after the reboot. One port forwarding rule is saved, but that one can't be removed or changed. I have tried to reset to factory settings, but no go. I really wish I could go back to 1.2x firmware.
D-Link, please fix this asap!
Sorry...but LOL...they (DLINK) have a few issues with fw1.31. :-\
They what your Dir 655 to be a NAS device, print server, basically an all-in-one but not the Router you bought. SO if you made mistake of updating like myself & others your up the creek without a paddle. ETA on a fix, next product cycle. ::)
-
Sorry...but LOL...they (DLINK) have a few issues with fw1.31. :-\
They what your Dir 655 to be a NAS device, print server, basically an all-in-one but not the Router you bought. SO if you made mistake of updating like myself & others your up the creek without a paddle. ETA on a fix, next product cycle. ::)
Ummm....are you saying I will not be able to set port forwarding and application rules anymore? That would suck big time. I will keep updating hoping D-Link reads these forums. Poke, poke D-Link! :)
-
What Internet browser are you guys using? If you aren't using IE7 or 8, it's probably because you can't stand IE. If you ARE using IE then I'm done. I have read in other threads that some browsers don't play nice with the router interface. If I am way off on that - SMITE ME! (see the little button in the upper left?)
hehe
-
What Internet browser are you guys using? If you aren't using IE7 or 8, it's probably because you can't stand IE. If you ARE using IE then I'm done. I have read in other threads that some browsers don't play nice with the router interface. If I am way off on that - SMITE ME! (see the little button in the upper left?)
hehe
I could be wrong on that subject also but if I remember right someone was using Firefox beta 3.5. Clancy no "smite" needed. ;D
-
What Internet browser are you guys using? If you aren't using IE7 or 8, it's probably because you can't stand IE. If you ARE using IE then I'm done. I have read in other threads that some browsers don't play nice with the router interface. If I am way off on that - SMITE ME! (see the little button in the upper left?)
hehe
I've used Firefox, Opera (I work for them) and IE 7/8. That was my first theory: "The browser did it!" I'm sorry to have to say it ain't so.
-
Some security settings of browsers also can mess up stuff. Also, some Javascript can be addressed differently by different browsers.
-
I've used Firefox, Opera (I work for them) and IE 7/8. That was my first theory: "The browser did it!" I'm sorry to have to say it ain't so.
Well if you do a little research which @ this point is a lot from the number of posts you"ll find the issuse started when Dlink decided to emplement "shareport" around firmware 1.21-22. It's crazy the number of posts and subject matter people are blamming this or that is the problem. The bottem line is the firmware dose not work!
Also if you notice the fw1.31na "NA" is North America only. Have you ever went to dinner @ your mother in laws house and had a dish she swore was good and you choked it down to be nice, same thing here. We are as it seems the test bed as I wonder how 1.31NA ever made it out of beta!
Visit other Dlink sites like "EU", they stopped @ fw 1.21.
-
Well if you do a little research which @ this point is a lot from the number of posts you"ll find the issuse started when Dlink decided to emplement "shareport" around firmware 1.21-22. It's crazy the number of posts and subject matter people are blamming this or that is the problem. The bottem line is the firmware dose not work!
Also if you notice the fw1.31na "NA" is North America only. Have you ever went to dinner @ your mother in laws house and had a dish she swore was good and you choked it down to be nice, same thing here. We are as it seems the test bed as I wonder how 1.31NA ever made it out of beta!
Visit other Dlink sites like "EU", they stopped @ fw 1.21.
I cannot get Shareport to work reliably. That is my one and only issue. When I first came to this forum I was running under 1.21. Since then, I have flashed every new release the day of, or the day after release. No matter how much I try, no matter how often I change settings just to "see what this does", I have been unable to break the DIR-655. What is even stranger and bizarre is that I recently switched my settings from mixed Wireless N and G, to Wireless G and B. I fully expected a decrease in Upload/Download speed. When I ran a speedtest, to my utter astonishment and disbelief I discovered that I now had a speed increase in both Down and Uploads. It was slight, but it was there never the less. I ran this test dozens of times to make sure I was not hallucinating. When something like this happens, one of you out there can probably tell me that there is a logical explanation because if there is, I truly would like to hear it. Maybe it's because I don't know what I'm doing. Maybe it's the "Triumph of the uncluttered mind". But when my router throws surprises like this at me after all of the settings I've checked and unchecked, firmware flashes, and everything in between, you'll have to excuse me if I don't fall in line with you.
-
I cannot get Shareport to work reliably. That is my one and only issue. When I first came to this forum I was running under 1.21. Since then, I have flashed every new release the day of, or the day after release. No matter how much I try, no matter how often I change settings just to "see what this does", I have been unable to break the DIR-655. What is even stranger and bizarre is that I recently switched my settings from mixed Wireless N and G, to Wireless G and B. I fully expected a decrease in Upload/Download speed. When I ran a speedtest, to my utter astonishment and disbelief I discovered that I now had a speed increase in both Down and Uploads. It was slight, but it was there never the less. I ran this test dozens of times to make sure I was not hallucinating. When something like this happens, one of you out there can probably tell me that there is a logical explanation because if there is, I truly would like to hear it. Maybe it's because I don't know what I'm doing. Maybe it's the "Triumph of the uncluttered mind". But when my router throws surprises like this at me after all of the settings I've checked and unchecked, firmware flashes, and everything in between, you'll have to excuse me if I don't fall in line with you.
So you saying fw 1.31na-1.32na beta works? But your shareport dose not? I'm confused.
-
The 'problem' is not that simple. There are multiple situations where everything works fine. But there are also some situations in which one thing causes an issue, the other works, there are situations that have it vice versa and situations that have both issues. Still following me? ;)
So...it's very hard to distinguish here where one can speak of a hardware error or firmware issue or where there is some local config issue that has nothing to do with either hardware or firmware. That's the beauty of these forum :)
-
Thanks. That thread seems to be dealing with two problems. The one I have are mentioned in the thread, but I can't see a solution other than disable upnp-rebboot-enable upnp-reboot the router. There's something wrong with the 1.3x firmware with regards to both forwarding and applications rules since they can't seem to be saved. I have another DIR-655 at my office with 1.2x firmware. No such problems there.
Actually i did get rid off this issues when i did some SECURESPOT enabling/disabling/making rules/rebooting stuff... It has something to do with securespot when this port forwarding settings are not saved like they should.
-
The 'problem' is not that simple. There are multiple situations where everything works fine. But there are also some situations in which one thing causes an issue, the other works, there are situations that have it vice versa and situations that have both issues. Still following me? ;)
So...it's very hard to distinguish here where one can speak of a hardware error or firmware issue or where there is some local config issue that has nothing to do with either hardware or firmware. That's the beauty of these forum :)
I have two DIR-655s. One with firmware 1.2x, the other updated to 1.3x. The one with 1.2x works perfectly, the one with 1.3x can't store port forwarding and application rules. This tells me the firmware is messed up. I can't find any other explanation. Port forwarding and triggering are pretty basic functions of a router and should work. I have a pretty simple set-up without anything fancy enabled. The settings are similar on both my DIR-655s. I've spent hours on this and think D-Link at least should work on a downgrade option so that people can get back to something that works. I'm sure that's possible somehow.
-
I run 1.31 and port forwarding saves OK....honestly, I'm not joking here. You did do a reboot after filling in the data?
PS: using FF3.6 Preview, in case you were wondering...
-
So you saying fw 1.31na-1.32na beta works? But your shareport dose not? I'm confused.
LOL! Nothing like making yourself look stupid (and I'm referring to Moi). I was taking into consideration all of the other complaints I've been hearing after upgrading to the latest Betas. Shareport's reliability issues have become something that is now only in the back of my mind. I'm just watching and waiting and spending way too much time in these dang threads. I didn't buy my DIR-655 to host a NAS. If they ever get it to work, (for me, that is, because there are users that have NO problems with it) then I will consider it icing on the cake. D-Link does have a problem in that I think they put the cart well before the horse. This feature is advertised big time. Unfortunately, if every customer out there (besides us that frequent these boards) who bought it for this purpose and has NO problems with it, we will never know. Why would they ever visit here? So, Shareport to many people could be an unqualified success and we who visit these boards are but the inmates of the assylum who think the rest of the world is just as crazy as us.
After backtracking and reading YOUR posts, I see that you have only dealt with Shareport issues alone. So, I hope that I have un-confused you. If only someone would do the same for me.
-
I run 1.31 and port forwarding saves OK....honestly, I'm not joking here. You did do a reboot after filling in the data?
PS: using FF3.6 Preview, in case you were wondering...
I have rebooted several times. Entered the settings manually instead of restoring a back-up. I've disabled and enabled stuff I do not use to see if something else affects port forwarding, and I've done both a sw and hw restet to factory defaults. I've bascally done what I would expect D-Link to do before they ship a fw update: Check that everything works! :)
I've compared two identical routers since I have two of them. The 1.2x one works flawlessly, the 1.3x one doesn't. I do not use Shareport or Secure Spot or anything fancy, just basic router functionality, so I can't tell if these new features work or not. I simply want 1.3x to work like 1.2x for basic router operation.
-
The 'problem' is not that simple. There are multiple situations where everything works fine. But there are also some situations in which one thing causes an issue, the other works, there are situations that have it vice versa and situations that have both issues. Still following me? ;)
So...it's very hard to distinguish here where one can speak of a hardware error or firmware issue or where there is some local config issue that has nothing to do with either hardware or firmware. That's the beauty of these forum :)
Demonized it is that simple and I do follow you! Either it works or it dose not period.
So it's acceptable to have a flaky Router or Firmware which ever you choose to blame @ the time to work hafe the time?
-
I run 1.31 and port forwarding saves OK....honestly, I'm not joking here. You did do a reboot after filling in the data?
PS: using FF3.6 Preview, in case you were wondering...
Just a clarification: You say that port forwarding is working. Yes it is working. The problem is not that it isn't working but rather than the settings aren't stored so the router "forgets" it's port forwarding rules after a reboot.
-
LOL! Nothing like making yourself look stupid (and I'm referring to Moi). I was taking into consideration all of the other complaints I've been hearing after upgrading to the latest Betas. Shareport's reliability issues have become something that is now only in the back of my mind. I'm just watching and waiting and spending way too much time in these dang threads. I didn't buy my DIR-655 to host a NAS. If they ever get it to work, (for me, that is, because there are users that have NO problems with it) then I will consider it icing on the cake. D-Link does have a problem in that I think they put the cart well before the horse. This feature is advertised big time. Unfortunately, if every customer out there (besides us that frequent these boards) who bought it for this purpose and has NO problems with it, we will never know. Why would they ever visit here? So, Shareport to many people could be an unqualified success and we who visit these boards are but the inmates of the assylum who think the rest of the world is just as crazy as us.
After backtracking and reading YOUR posts, I see that you have only dealt with Shareport issues alone. So, I hope that I have un-confused you. If only someone would do the same for me.
lol...some of these threads and posts are weeks deep and old, they are all overlapping.
It's like that movie "Ground Hog Day".
-
Port forwarding is working for me on A2 FW 1.32NA, it wouldn't save if I used firefox to configure it tried it in IE and it saved went back to firefox and settings were saved go figure..
-
Demonized it is that simple and I do follow you! Either it works or it dose not period.
So it's acceptable to have a flaky Router or Firmware which ever you choose to blame @ the time to work hafe the time?
Don't understand what you're trying to say here...
-
Demonized it is that simple and I do follow you! Either it works or it dose not period.
If the chipset of the router was designed to only do certain things and accept configurations that made sense in the programming of the firmware there would not be an issue no matter how complex the config was.
@ issue: Shareport, DNS Relay, portforwarding
-
My best guess it is in the hardware (=>kernel SDK). Running A2 here and all three work like they should here (and i don't run a minimalist config).
-
My best guess it is in the hardware (=>kernel SDK). Running A2 here and all three work like they should here (and i don't run a minimalist config).
I'm not sure I understand. Are you saying that some hw worked with hw 1.2x, but not with 1.3x, while some hw works with both 1.2x and 1.3x? If so, is there a way to see what hw version I have?
-
That's what it looks like, yes.
The hardware version is displayed in the router setup GUI. Top right. And on the bottom of the router itself.
There are different components used in A1/A2 <=> A3 (switch) and A1/A2/A3 <=> wireless radio
The kernel for each version is the same and needs to work with all hardware. That can cause issues for one revision while not causing the issue on the other revision. And D-Link has a third party doing the coding (from Ubicom source to Dlink use), and if they do a c****y job....