D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: Tsumeone on May 02, 2009, 02:44:32 AM
-
Bug that was introduced in 1.22 is STILL here.
Namely, I cannot set pool.ntp.org as my time server any more. I could do this up thru 1.21 but 1.22 and newer have a bug with this where as soon as I hit "Save" on the page with pool.ntp.org as the time server, the router starts reboot looping until I use the physical reset button to restore the factory defaults.
Trivial bug, but it needs to work as designed or not allow you to type your own NTP server.
-
I got my own NTP server inserted: no problem. You are aware that you need to set the servers like this: 0.pool.ntp.org or 1.pool.ntp.org or 2.pool.ntp.org and you cannot insert pool.ntp.org (see the pool.ntp.org manual) ? I tried all three and router did not crash.
-
I just installed 1.31 on my router, and honestly, it's HORRIBLE!
I was using 1.21 before, with little to no issues, once I updated, I too am having this issue.
I WAS VERY SUCCESSFULLY using: north-america.pool.ntp.org
Since the instructions were to SAVE a copy of the Router configuration file, then flash with 1.31, THEN reset to DEFAULTS, THEN restore using saved configuration file -- I did just that.
HOWEVER, because I was using north-america.pool.ntp.org very happily before, no issues, and that was part of my saved configuration file, now because of this BUG, I have to go back and manually setup all of my fields, otherwise endless router reboots.
-
Sorry to here gericb, ...but do you have any friends with this router? Spread the word about the forum. It appears D-Link is using this forum to gauge whether or not v1.31 is actually a solid firmware update. It would also appear based on replies in this forum that D-Link believes far too many routers are on the market with not enough problem posts here in the forum to warrant researching and or resolving this v1.31 firmware debacle.
So, the more people that post about this problem, the more likely the chance for an update that will either resolve it, or an update that will unlock the downgrade option so you can get back on v1.21.
Respectfully,
Tommy Lee
-
Sorry to here gericb, ...but do you have any friends with this router? Spread the word about the forum. It appears D-Link is using this forum to gauge whether or not v1.31 is actually a solid firmware update. It would also appear based on replies in this forum that D-Link believes far too many routers are on the market with not enough problem posts here in the forum to warrant researching and or resolving this v1.31 firmware debacle.
So, the more people that post about this problem, the more likely the chance for an update that will either resolve it, or an update that will unlock the downgrade option so you can get back on v1.21.
Respectfully,
Tommy Lee
His issue is with the restoration of the saved config file. I do not agree to the 'easy' qualification that the firmware is no good. It's works perfectly fine over here, even the ntp issue is not an issue in my router and therefore cannot be called an issue, let alone a generic issue. It takes more than 10 peeps complaining about something that could just as well have an external cause. It's too easy to point immediately at the firmware. Too many so called 'firmware issues' have passed around here that were caused by external factors.
-
I got my own NTP server inserted: no problem. You are aware that you need to set the servers like this: 0.pool.ntp.org or 1.pool.ntp.org or 2.pool.ntp.org and you cannot insert pool.ntp.org (see the pool.ntp.org manual) ? I tried all three and router did not crash.
http://www.pool.ntp.org/en/use.html
Looks like I can use pool.ntp.org - and I've been using it in all my PCs as their time server without issue. The x.pool.ntp.org is optional.
I would like you to try putting pool.ntp.org in and see what happens. I'm not saying that I won't use the 0.pool.ntp.org now that I know that works, but I am saying D-Link needs to fix the problem that causes the router to boot-loop with a time server it doesn't like.
NOTHING should cause the router to infinite reboot.
-
Sorry to here gericb, ...but do you have any friends with this router? Spread the word about the forum. It appears D-Link is using this forum to gauge whether or not v1.31 is actually a solid firmware update. It would also appear based on replies in this forum that D-Link believes far too many routers are on the market with not enough problem posts here in the forum to warrant researching and or resolving this v1.31 firmware debacle.
So, the more people that post about this problem, the more likely the chance for an update that will either resolve it, or an update that will unlock the downgrade option so you can get back on v1.21.
Respectfully,
Tommy Lee
Well, I have started to post and hopefully many others do the same. I am getting disappointed with the dir-655, as it seems Dlink is more interested in adding non router features to it then improving the routing features.
For example, Securespot is a feature that does not belong in a router. Parental controls do not belong in a router either.
What does need improvement does not seem to get improved. A good example of an improvement would be to lower the amount of reboots required when making setup changes. Is it really required to perform a full router reboot when changing the MAC address? Is it really required to perform a full router reboot when adding a rule to the forward rules?
I know routers from other companies do not require reboots under those 2 circumstances...
-
For example, Securespot is a feature that does not belong in a router. Parental controls do not belong in a router either.
Well, it seems 'the market' thinks differently. Remember these are consumer routers and 90% of current PC users really don't have a clue what 'security' is for their network.
What does need improvement does not seem to get improved. A good example of an improvement would be to lower the amount of reboots required when making setup changes. Is it really required to perform a full router reboot when changing the MAC address? Is it really required to perform a full router reboot when adding a rule to the forward rules?
Reboots have been added to ensure that setup changes will be saved and executed correctly. You can delay a reboot until you have implemeted all changes and only have one reboot...So the number of required reboots is actually just....1!
-
It's a pest. A bit of topic, but these days it becomes increasingly harder to find what you need without all the extra fluff. It's so hard to just find a virus scanner these days...
-
Incorporating the feature into a router makes some sense: No software buying, installing or mind boggling configuration which forces you to educate otherwise your internet access will be blocked by the program or the AV doesn't block anything... And I don't blame them. As experts we tend to expect that everybody grasps the details of this technological machine and willingly dive into the "How Things Work" stuff. They don't , just like I do not have a clue how to fix a color TV. I just want to watch movies on that screen... :P
Taking that away from the 90% that just want to use a computer program is a blessing for internet security. Using routers (the gateway to the bad world) and subscriptions is easy for consumers, good for manufacturers and safe for the internet community.
-
BTW, I just ran into this. Very Annoying!
For the record, I used 0.north-america.pool.ntp.org and my router started to get in a rebooting loop...
-
Just enter another ntp server...they all give the same time you know...this is a problem that is not really a problem
-
Except that I had just set up QoS, WISH, DHCP Reservations, etc for 6 people, the only thing I do to get it stop rebooting was reset it.
And you said to use another ntp server... which I did, instead of using pool.ntp.org I used 0.north-america.pool.ntp.org... Should I try another one only to have it happen again?
Talk about regression testing... Do you do any dlink?
-
Except that I had just set up QoS, WISH, DHCP Reservations, etc for 6 people, the only thing I do to get it stop rebooting was reset it.
And you said to use another ntp server... which I did, instead of using pool.ntp.org I used 0.north-america.pool.ntp.org... Should I try another one only to have it happen again?
Talk about regression testing... Do you do any dlink?
The list of NTP servers is endless...whether you get one from Asia, Europe or the Northpole...they all give the same time. Even the default Dlink ones :D
By the way, I tried your NTP in my router: no issue whatsoever...
-
The list of NTP servers is endless...whether you get one from Asia, Europe or the Northpole...they all give the same time. Even the default Dlink ones :D
By the way, I tried your NTP in my router: no issue whatsoever...
There must be some set of options that when configured cause this problem. I tried that address twice with the same results and all the other settings the same.
-
There must be some set of options that when configured cause this problem. I tried that address twice with the same results and all the other settings the same.
I guess so. But I think entering an NTP that causes no problems is easier (unless you got too much 'time' on your hands and persist in keeping the problem).
-
Right, but I think the problem is that if there is some element to reproducing this besides just entering a time server, how does one know what a "time server that works" is? It seems like its going to be more trial and error. At this point I am just not going to enter one.
-
Hey EddieZ --
Yesterday I made the 1.31 jump and for sh*ts and giggles I added pool.ntp.org as my time server. I've never seen my 655 reboot so frequently and with so much passion!
Fortunately, turning the cable modem off will stop the problem from recurring long enough to change NTP to time.nist.gov. Its been working ever since.
Very strange indeed.
-
Right, but I think the problem is that if there is some element to reproducing this besides just entering a time server, how does one know what a "time server that works" is? It seems like its going to be more trial and error. At this point I am just not going to enter one.
You can use the ones defaulted in the router. Unless you don't trust Dlink to give the exact time ;) The majority of NTP will work (looking at the choice you have besides the 'pool' ntp's). Just an opinion, but I think you're making an elephant out of a mouse... :)
It's only there to set the time on the router, and unless you're in a transaction critical environment with timestamping there is any importance to it. But in that case you probably should also not be using a 'soho' DIR655 on the network...
-
You can use the ones defaulted in the router. Unless you don't trust Dlink to give the exact time ;) The majority of NTP will work (looking at the choice you have besides the 'pool' ntp's). Just an opinion, but I think you're making an elephant out of a mouse... :)
It's only there to set the time on the router, and unless you're in a transaction critical environment with timestamping there is any importance to it. But in that case you probably should also not be using a 'soho' DIR655 on the network...
If you look at my first post, I just said it was annoying... Not making a elephant out of anything.
Its just annoying.
-
ok
-
EddieZ - I take it you are part of D-LINK Technical or Firmware support? It seems your roll here is poo-poo anyone's topic, comments of issues they have seen.
Of course you seem to never have the problems yourself, we are all just lame nobs here, and you are the GOD of perfection right? :)
A problem is a problem, no matter the degree of the problem, and no matter if you agree it is or not from your perspective, it is to others. Your down playing of the "issues" as we see it doesn't negate our belief it is a problem, or in fact it's being taken as such. If more than one person see's the problem, can reproduce it, it's a problem.
Part of the reason anyone buys a product it on the belief there will be reliable, logical, continued support of same. Given for example that the NTP option in the DIR-655 ALLOWS you to put in ANY OTHER NTP's, is reason we SHOULD expect it to work.
It's not me saying that I don't trust the D-Link ones, but I sure as hell do not trust the M$ ones, and long ago stopped using those. So if I WANT to use this, I should be able to and not expect to see my router reboot senselessly over and over again...when it is stable before I decide to a server of my choice.
I might be new to this forum, but have 15+ of IT background, both technical and Mgmt, and the things going on with this particular 1.31NA version of the firmware are just buggy, flat out.
Every installation is going to be different, every need and expectation is going to be, and thankfully we do not need to get any approval from you for our varying environments, needs and expectations as you obviously have none yourself.
I have always personally steered IT/consumer purchases away from D-Link products for this very reason, weird, unreliable firmware updates and issues that rarely seem to get resolve. To that point, they as a company knew the impressions of their hardware and mgmt and have attempted many revamps of products lines, techical staff (having friends on the inside), and winning back customers.
Given the age of this company and presumed experienced product designers, I have FAR LESS issues with Linksys products. My exposure is 100% post purchase, otherwise there would never be these issues going on and me inquiring is anyone else is experiencing the same things, because I would not be buying them.
So give it a break, be part of the real soultion, problem determination, because your wonderful rosey world of no problems doesn't exsist for many others, and they are as equally important in their needs to be resolved to their satisfaction.
Thanks! ;D
-
No, EddieZ is NOT part of ANY D-Link staff. However blunt he may be, his point is valid. Now, I understand that more and more people are suffering from problems with the 1.31 firmware as well as it's cousin code on the other models.
We are looking in to the situation with renewed vigor and will do everything within our ability to isolate and correct the issue asap.
I understand that it seems like Eddie and the D-Link mods may not care, this couldn't be farther from the truth. We are constantly monitoring the forums and noting issues that are repeatedly appearing with our customers.
I'm going to lock this thread as it's reached the end of it's usefulness.
-Lycan.