Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[FurryNutz]

Get it here:
http://forums.dlink.com/index.php?topic=60679.0

Let us know how it works for you...

[jclarkw]

Get it here:
http://forums.dlink.com/index.php?topic=60679.0

Let us know how it works for you...

Interesting.  When I go to http://support.dlink.com/ProductInfo.aspx?m=DIR-645 they show it only as a Beta version.

I don't suppose you have tested it for our old favorite bug regarding password change before configuration save? -- jclarkw

[FurryNutz]

I have loaded it and router was online for a while. I didn't test the PW issue out as I presume that once fixes are in place in prior version, they will populate to new version as they are graduated.

[jclarkw]

I have loaded it and router was online for a while. I didn't test the PW issue out as I presume that once fixes are in place in prior version, they will populate to new version as they are graduated.

To my knowledge, this bug was never fixed.  Certainly it's still present in my current FW1.04B11.  See also http://forums.dlink.com/index.php?topic=46358.15  Am I missing something? -- jclarkw

[FurryNutz]

So not sure if this is a bug perse or be design. I was able to input a PW using only the upper case characters on the numeric numbers and saved settings, rebooted and had to use the new PW. I did a save router config to file after that, Factory reset. Reloaded the saved file and rebooted. PW was blank again. V1.04 B12.

This maybe by design instead of a bug. If you think about it, If a user happens to input a PW and later on forgets it after reloading the saved file. It give them a chance to get into the router while still having all the other saved settings in place. The only thing users have to do is to test and re-input a new PW for the Admin log in. I personally don't mind the PW being blank after a restore. You just have to keep the config files in a safe place is all.

As for the other issue found, its been 2 year since he posted that and never responded back. I don't know if how his test and configuration methods are correct nor his network needs that he's testing for maybe supported officially by this model router on that level of testing. Generally, these are home routers and doing a lot of back end testing and network diagnostic just may not be supported on this layer. Ya maybe older routers may have however going forward, not a lot of call for that level of diagnostic support at home with the avg home user. Those things are kept to the Business and enterprise class HW.

Over all, this model router has done well for itself and is stable. Unfortunately, I don't think D-link will be doing much, if any, FW updates from here on out from what I was told. Unless there is some major security issue found.

[jclarkw]

So not sure if this is a bug perse or be design. I was able to input a PW using only the upper case characters on the numeric numbers and saved settings, rebooted and had to use the new PW. I did a save router config to file after that, Factory reset. Reloaded the saved file and rebooted. PW was blank again. V1.04 B12.

Furry -- I think you've got it backwards.  I agree that the situation you describe (password blank after configuration reload) could well be by design for the reason you state.

But in my experience a change of password **after** a configuration **save** (no configuration **reload** involved) results in a blank password after reboot or power cycle.  (See problem description at http://forums.dlink.com/index.php?topic=46358.msg204574#msg204574 and in another of our old threads.)  I believe this unexpected behavior could trick users into thinking their router is password protected when in fact it is not.  At least that was what happened to me.

I know I checked this after updating to Build 11 and it was still happening.  I'm still not sure exactly how long after the configuration save a newly set password is vulnerable to loss.  Also not sure how best to work around this problem, but it appears that resetting the password after it is lost (without any more configuration saves) results in a permanently stored password.  I haven't tried Build 12 yet... -- jclarkw

[FurryNutz]

I just checked with B12 with a Mac loaded with OSX 10.9.5 and Safari 7.1. The 645 didn't have any PW so I used 123456789, Save and used the power button in front of the router and exited the browser. Turned back on and after it came to ready. I just hit Enter and got log in fail. I typed in 123456789 and logged in successfully. I rebooted the router using the UI this time and exited the browser. After ready, typed in 123456789 and log in successfully. I removed the PW, saved and used the UI to reboot the router and this time left the browser going. After it was ready I typed in 123456789 and got a log in failure. Selected Enter and logged into the router correctly.

[jclarkw]

I just checked with B12 with a Mac loaded with OSX 10.9.5 and Safari 7.1. The 645 didn't have any PW so I used 123456789, Save and used the power button in front of the router and exited the browser. Turned back on and after it came to ready. I just hit Enter and got log in fail. I typed in 123456789 and logged in successfully. I rebooted the router using the UI this time and exited the browser. After ready, typed in 123456789 and log in successfully. I removed the PW, saved and used the UI to reboot the router and this time left the browser going. After it was ready I typed in 123456789 and got a log in failure. Selected Enter and logged into the router correctly.

Sorry if I'm being dense, but I don't understand your test.  Did you:
A) do a configuration save,
B) then change the password,
C) then reboot or power cycle,
D) then test the new password?
That's the condition in which my password disappears.

I just did the following test sequence on FW1.04B11 from Win7 SP1 with current FireFox (running inside Sandboxie, not that it matters).  I did not close and re-open the browser between steps:

1) Logged in to router using existing complex password.
2) **Did a configuration save**
3) Was automatically logged out by timeout.
4) Successfully logged back in using same complex password.
5) **Changed password to 123456789**
6) Was automatically logged out by timeout.
7) Successfully logged back in with 123456789.
  **Did a GUI router reboot**
9) **Attempted to log in with 123456789.  Failed.  Successfully logged in with blank password**
10) Changed password to back to original complex password.
11) Was automatically logged out by timeout.
12) Successfully logged back in using same complex password.
13) Did a GUI router reboot.
14) Successfully logged back in using same complex password.
 -- jclarkw

P.S. -- How do I suppress emoticons?  My "number-eight close-peren" above just got changed to a " ".

[FurryNutz]

Ok, sorry if I didn't read all of what we had gone over.
So,
A. do a configuration save,
B. then change the password,
C. then reboot or power cycle,
D. then test the new password? Yes, after a config to file is done, then changing the PW fails to apply the newly changed PW and entrance to the router is blank. However application again of a new PW, save settings and reboot sets the PW and the PW is correct for logging into the router. Only seems that if a user folliws this, will it fail at step D.

I'll have a talk with D-Link about this and see if this can be fixed. At least after the failure, a user just needs to re-apply a PW and it will be secure again. If a user does a save to config to file and just reboots with out changing the PW, the PW is saved and is required at log in from my tests.


p.s. Don't use the ) symbol when typing your information. Use . , : etc...

[jclarkw]

I'll have a talk with D-Link about this and see if this can be fixed. At least after the failure, a user just needs to re-apply a PW and it will be secure again. If a user does a save to config to file and just reboots with out changing the PW, the PW is saved and is required at log in from my tests.

p.s. Don't use the ) symbol when typing your information. Use . , : etc...

Thanks again!  This bug has been present at least since FW1.03 -- that's four FW revisions (major, minor, and beta) by my count since it was first reported.  I wonder if similar routers suffer from the same bug, or is it unique to the DIR-645 NA A1 HW version?  Best Regards. -- jclarkw

[FurryNutz]

I'll test on some of my other routers. I doubt anything will be done on the 645 as there is a work around. I'll keep you posted...