Print

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

[FurryNutz]

This thread is in regards to what users of the DIR-645 would like to request DLink to review and consider adding features to the routers FW and operation. Also this thread includes any reports of bugs that arere-producible, that should be reviewed by DLink seen my us users. Please be professional, detailed, concise and tactful when posting the requests and bug details.

Do not arbitrarily post defects or bugs here. Before reporting concerns about defects or bugs, please ensure that troubleshooting of the problem has been thoroughly completed before posting a problem about defects. Not all issues are a defect or bug related. Let other users help you troubleshoot the problem first before posting here.

Ranting or Demanding anything will not get us anything. There are no guarantees.

Please keep other subjects, topics and questions to other threads and posts. This thread is just a central list of Features and Bugs for review by DLink.

Example:
FEATURE REQUESTS:
Firmware update file process performs a Automatic Factory Reset after the firmware data has been applied. Would be nice to have the update automatically do a factory reset after the data has been applied to the unit. Some end users are not aware of doing a factory reset after the FW update has been applied and they presume that the unit has been wiped and back to factory settings. It would probably be beneficial if this additional reset was handled by the FW update process automatically.

DEFECTS:
Seems that upon entering the routers password for logging into the web page, then hitting ENTER on the key board, the router does not accept the entered PW and gives a incorrect password message when using Safari and other browsers on Mac OS. Possible Windows OS's as well. Seem that after several tries, the routers web page will accept this operation eventually. Entering the password and then clicking on the login button with the mouse seems to resolve this. The ENTER key on the keyboard should be a valid command and the web page should accept this operation. It was mentioned that Safari was not supported by the router and to use IE or Firefox. Mac OS comes native with Safari and as a end user, Safari should be supported fully by the router. MS does not make a recent version of IE and no longer develops IE for Mac.

[FurryNutz]

QoS is being reported as disabled on ISP Uplink Speeds over 2Mb. Dlink, Please review and consider QoS and the impact of uplink speeds over 2Mb and the interaction between the two to allow higher ISP up links speeds to work with QoS on router products.

Please review the following DIR-827 for additional information:
http://forums.dlink.com/index.php?topic=46674.0

[dalgibbard]

I appear to have stumbled across a fairly substantial bug, although i'm not 100% sure on the steps to reproduce.

Symptom:
* Local LAN Host fails to be able to ping or ARP router on wired or wireless connection, when that system's IP is set as one of the Internet DNS Servers in "Internet Settings". This also means no outgoing traffic from that host will work, BUT internal LAN traffic TO that host, will still function (SSH etc)

Steps to reproduce:
* Reserve an IP for a system on your LAN (eg. 192.168.0.30 -- referred to as SYSTEM1 from here on out)
** NOTE: Definitely does NOT matter if the IP is inside or outside of the DHCP range.
* Renew IP on SYSTEM1 for changes to take effect where necessary.
* Ping router from SYSTEM1- all should be fine.
* Go to Setup> Internet> Manual Internet Connection Setup
* Set the "Primary DNS Server" field to the internal IP of SYSTEM1 (ie. 192.168.0.30)
* Save changes
* Ping router from SYSTEM1 - fail.
* on SYSTEM1 "arp 192.168.0.1" returns "-- no entry"

Points which may affect outcome and are untested:
* SPI enabled in my case, disabled with no effect
* Spoofing check enabled, disabled with no effect
* Arp command above was on a Linux host, but problem affects Windows and Unix alike.
* DNS relay is set to off in my example, but also doesn't work when set to on.

Theory:
Routing is automatically setup by the internet connection settings page to route the DNS traffic via WAN regardless of IP range. Therefore, ARP requests reach the router (unproven... and unprovable) and replies are sent out of the WAN interface. Therefore, no ARP, no MAC reference, no ping-ability or another other connectivity outbound. Inbound traffic to that host still functions.

Technical backing:
I'm a Linux Systems admin by day

I would greatly appreciate if anyone could give this an attempt, and report back with their findings?
I've raised a support reference with D-Link already, and will keep you posted with progress (Fault ref: 724915 in case anyone needs it!)

---
See also: http://forums.dlink.com/index.php?topic=46615.0

[dalgibbard]

Is DNS relay enabled?
Not sure if inputting a LAN IP address on the DNS Setting is a valid option for these routers since it's tied and dependent on the WAN port I think. 

Have you talking to someone directly at DLink about this and if this option is supported?

I thought about that myself just after posting actually, was going to update tomorrow, but hey.
DNS relay is off (the way I want it! Primarily due to ipv6 tunnelling DNS requirements- long story...).
This is the exact setup I was using on my DIR-825 two days ago, for the past two years, without issue...
I'm awaiting response from a d-link support representative. Will let you know.

[FurryNutz]

Ok, sent this to my contact as well. Be aware that some routers behave differently from others, like loopback and pinging and such are not supported FYI. Not sure about this one however. I can give this set up a go on my 857 tonite and see.

[Lycan]

If I understand your issue correctly. your setting the WAN DNS server to be an IP address that is within the LAN segments subnet, and the router is performing irregularly?

[dalgibbard]

If I understand your issue correctly. your setting the WAN DNS server to be an IP address that is within the LAN segments subnet, and the router is performing irregularly?

In other words, yes. On setting it that way, the internal DNS server in question can no longer contact (more correctly- ARP) the router.

[bernied]

Hi

I have reported issues with the DLNA feature of the router.
See   " problems with dlna support within firmware. " thread.


Is this  something that will be updated in a new firmware.   tks

[go6henk]

A working IPv6 firewall on 6rd with some example settings in the help.

[FurryNutz]

Shareport v4 for Mac fails to connect to a USB drive using OSX 10.6.8 and 10.8.2:
http://forums.dlink.com/index.php?topic=44116.msg189865#msg189865

Same Mac and USB drive and Shareport version work with a DIR-857 and 657. 

[jclarkw]

DEFECT:  New Password is Lost After Configuration Save

Environment:
DIR-645, H/W A1, F/W 1.03 (flashed from original 1.01), S/N PVU41C2002342
Windows XP SP3, IE 8 or Firefox 20.0.1.

Reference Thread:  http://forums.dlink.com/index.php?topic=53305.0

Conclusions:
A) Any change in password following a configuration save does not survive UI reset (and almost certainly not a power cycle).  Result is a blank password.
B) Without a configuration save, or with the configuration save **after** the password change, any change in password survives either UI reset or power cycle.
C) Device accepts passwords up to 15-characters containing a mix of upper and lower case letters, numbers, and special characters.

Steps to Reproduce Password Loss:
1) Open router Web-admin page, paste in current complex password, log-in OK.
2) Save configuration file.
   Optional steps inserted here do not change result:
   2A) Log off of Web-admin pages (close browser).
   2B) Log on again with same complex password, log-in successful.
3) Enter simple 3-digit password in both new-password fields and save settings.
   Optional steps inserted here do not change result:
   3A) Log off of Web-admin pages (close browser).
   3B) Log on again with same simple 3-digit password, log-in successful.
4) Re-boot router from UI.
5) Attempt log-in with same simple 3-digit password, log-in failed.
6) Attempt log-in with blank password, OK, password fields are blank.

Because of the possibility of inserting an unknown number of steps either before or after (3) above, this unfortunate effect of a configuration save can lead to fairly unpredictable loss of password and resulting security vulnerability.

Furry, I've added a few more elaborations here.  I hope this is what you have in mind for this thread. -- jclarkw

[FurryNutz]

This is fixed in v1.04. 

DEFECT:  New Password is Lost After Configuration Save

Environment:
DIR-645, H/W A1, F/W 1.03 (flashed from original 1.01), S/N PVU41C2002342
Windows XP SP3, IE 8 or Firefox 20.0.1.

Reference Thread:  http://forums.dlink.com/index.php?topic=53305.0

Conclusions:
A) Any change in password following a configuration save does not survive UI reset (and almost certainly not a power cycle).  Result is a blank password.
B) Without a configuration save, or with the configuration save **after** the password change, any change in password survives either UI reset or power cycle.
C) Device accepts passwords up to 15-characters containing a mix of upper and lower case letters, numbers, and special characters.

Steps to Reproduce Password Loss:
1) Open router Web-admin page, paste in current complex password, log-in OK.
2) Save configuration file.
   Optional steps inserted here do not change result:
   2A) Log off of Web-admin pages (close browser).
   2B) Log on again with same complex password, log-in successful.
3) Enter simple 3-digit password in both new-password fields and save settings.
   Optional steps inserted here do not change result:
   3A) Log off of Web-admin pages (close browser).
   3B) Log on again with same simple 3-digit password, log-in successful.
4) Re-boot router from UI.
5) Attempt log-in with same simple 3-digit password, log-in failed.
6) Attempt log-in with blank password, OK, password fields are blank.

Because of the possibility of inserting an unknown number of steps either before or after (3) above, this unfortunate effect of a configuration save can lead to fairly unpredictable loss of password and resulting security vulnerability.

Furry, I've added a few more elaborations here.  I hope this is what you have in mind for this thread. -- jclarkw

[jclarkw]

This is fixed in v1.04. 

Furry -- I regret to report that this bug does not seem to have been fixed in FW 1.04 Build 10.  Here is an edited version of my  Reply #11 on: April 21, 2013, 05:13:27 PM showing exactly what I did this time:

DEFECT:  New Password is Lost After Configuration Save

Somewhat Changed Environment:
DIR-645, H/W A1 NA region S/N PVU41C2002342 (as before)
F/W 1.04 Build 10 (indicated date under Tools/Firmware is  "05/23/2013 09:45:00"?!), flashed today
Windows XP SP3, Firefox 25.0 (new version of FireFox_

Steps to Reproduce Password Loss:
1) At log-in page, enter current complex password, log-in OK.
2) Save configuration file.
3) Enter new password "123" in both new-password fields and save settings.
4) Re-boot router from UI.
5) Attempt log-in with same simple 3-digit password, log-in failed.
6) Attempt log-in with blank password, log-in OK, password fields are blank.

-- jclarkw

[FurryNutz]

Ok so I can reproduce this as well.

I also can't reproduce if I save config to file then reboot with out changing the PW.
I also can't reproduce if I change the PW and just reboot the router with out saving config to file.
I also can't reproduce this using your steps on a DIR-865L.

I attempted one more save config to file, changed the PW, saved settings and rebooted from the UI and PW was correct and and logged in correctly. However on a 2nd try again with saving the config to file and changing the PW and rebooting, the PW failed and was blank..

I input a new PW and rebooted with out saving to file and the new PW worked.

I also notice that when changing the PW and saving settings, some routers will log out and have you log back in. Not sure if the 645 should do this as well or not.


I'll forward this to D-Link for review. I thought this was fixed.  

[jclarkw]

Ok so I can reproduce this as well.

I also can't reproduce if I save config to file then reboot with out changing the PW.
I also can't reproduce if I change the PW and just reboot the router with out saving config to file

Furry -- Those are my observations as well.  The problem appears the same as with FW 1.03.  Glad I'm not completely crazy.  I think it can still be avoided by resetting the password **before** any configuration save... -- jclarkw