D-Link VWR Known Issues - YIKES

Posts: 39 · Vonage Forum Junior Joined: Jul 24, 2005 Posts: 39

In case you wondered what the current know issues are with a D-Link VWR, here they are. THIS IS the worse piece of junk I have ever owned. What ever happened to releasing devices that actually had the features it claimed work? I have added about 3 more issues they need to add to their list.... but here is theirs. What ever you do, do not buy or let them send you this until there is a firmware update from both D-Link and Vonage, they are both on the list for actions to take for these devices. Stick with a Linksys PAP2 ver.2, best device i have used yet (used Linksys WRTP54G, D-LINK VWR, and Linksys PAP2 ver.2) The VWR know issue list is almost as long as their "features"....

In regards to your email, as requested, here is the current known issue list with the
Dlink VWR device.

Device does not have ability to backup and restore router settings.

Symptom: Backup and Restore functionality is not available.
Solution: Currently being worked by vendor.

Changing WAN configuration resets remote web-login and SSH settings to default.

Symptom: Remote web-login and SSH settings will revert to defaults if WAN
configuration is changed.
Solution: Currently being worked by vendor.
Back to top
Phone port LEDs are not functioning correctly.

Symptom: LED for an unprovisioned port may turn on after bootup or if phone is taken
off-hook.
Solution: Currently being worked by vendor.

User agent field displays incorrect information.

Symptom: User Agent field displays incorrect information when viewing syslog or
console messages.
Solution: Currently being worked by vendor.

DHCP Relay not working properly.

Symptom: DHCP Relay is not functional.
Solution: Currently being worked by vendor.

No option to release/renew IP from ISP (DHCP WAN).

Symptom: Users cannot release/renew their WAN IP address via Web GUI.
Solution: In order for the VWR to get a new IP address, device providing the WAN IP
address for the VWR has to be rebooted.

When Web and SSH settings are saved, user is prompted to setup DDNS Client.

Symptom: When Web and SSH settings are saved, user is prompted to setup DDNS Client.
Solution: Bypass these pop-ups by clicking OK and device should save remote access
settings.

No QoS functionality for VWR.

Symptom: Qos functionality is not present.
Solution: Currently being worked by vendor.

MAC Filtering option is not available.

Symptom: Device has no option for MAC filtering.
Solution: Currently being worked by vendor.

Cannot save DMZ setting.

Symptom: User will be able to disable/enable DMZ but would not be able to save the
setting. C"b,KApplyC"b,b" button does not take effect.
Solution: Currently being worked by vendor

LED for Wireless does not turn off when it is disabled.

Symptom: LED for wireless (AP) will not turn off if wireless AP is disabled
Solution: Wireless LED will get turned off when device is rebooted.

Remote Web-login and SSH do not work if subnet mask is set to 255.255.255.255

Symptom: Remote Web-login and SSH do not work if subnet mask is set to 255.255.255.255
Solution: Change subnet mask to 0.0.0.0

Device generates a fast busy tone when handset is left off-hook.

Symptom: When receiver is let off-hook, device generates a fast-busy tone instead of
an off-hook tone.
Solution: Currently being worked by vendor.

DTMF Generated Power Levels are too low with default gain settings for Port 1 and Port
2.

Symptom: DTMF tones may not be recognized intermittently on the receiver end. This
will not affect DTMF tones sent from the device
Solution: Currently being worked by vendor.

Tip and Ring Single ended voltages are not correct.

Symptom: Users who have their phones connected to a PBX system may see issues where
the device does not terminate an active call correctly
Solution: Currently being worked by vendor.

FTP upload and download speeds are poor.

Symptom: Wireless clients using Intel Centrino chip sets are reporting throughput
issues. FTP (File Transfer Protocols) uploads/downloads can be performed but the
transmitting speeds are poor
Solution: Currently being worked by vendor.

Entering ASCII key in WEP Encryption generates an incorrect HEX value.

Symptom: Entering ASCII key in WEP Encryption generates an incorrect HEX value
Solution: Do not use ASCII keys in WEP Encryption. Being worked on by the vendor.

Inbound rings are short.

Symptom: When the customer receives an inbound call, the ring is short.
Solution: Currently being worked on by the vendor.

No inbound caller ID on some UK telephones.

Symptom: Caller ID does not display for an incoming call on some UK telephones.
Solution: Currently being worked by vendor. Affects only UK devices!

Device has no IP address and is stuck on 2 Blinks.

Symptom: : Installation fails if device is connected to Modem/Router/Gateway that has
a LAN IP of 192.168.2.1. Vonage device will not get an IP address on the WAN Interface.
Solution: Log in to Customers Modem/Router/Gateway that the Vonage device is connected
to and change the LAN IP address from 192.168.2.1 to 192.168.2.254 or 192.168.3.1.

Dynamic DNS Client feature does not work.

Symptom: : Attempt to activate the Dynamic DNS client feature fails.
Solution: Currently being worked by vendor.

Posts: 6 · New Forum Member Joined: Aug 27, 2006 Posts: 6

Thanks for the list. I hope they know about my uPnP issues. I have been waiting for many months for the promised vapor-firmware.

Posts: 39 · Vonage Forum Junior Joined: Jul 24, 2005 Posts: 39

Well then, more issues? Lets use this list for them to keep track of issues they need to fix. I could understand if they just had a few minor issues not working, but when you have major ones like WEP keys, MAC addresses, and DDNS not working, you need to hold off until you have a least a model that the features at least function as expected. I have a feeling that Linksys and Vonage had a fallout, so they scumbled and D-Link put together this on the fly. I have been seeing more and more Linksys/Earthlink Voice on the shelves in the store and I bet they went with them. Anyways... here is a few i am adding to their list of things that need to be fixed....

1) When you are hosting a web server, and try to get to that server by the external dns name, you get the VWR device home page. Example. My website. www.techtronic.us . If I try to get to that host name internally, I get the VWR admin page, not my webpage. I can still access the site fine when on another network, but not internally. I can get to my web server by its internal IP, but that doesn't help me with links that are hard coded with their external DNS name... (www.techtronic.us/login.php...)
FIX either let us change the device home page port from port 80 tcp, or get your port forwarding right...

2) You never know if the DDNS service is working on the VWR. The status page says jack about the status. It doesn't even give you any info
FIX VWR needs to show you status of the domain info, if the IP was success in updating DDNS, what time it was last updated, and if it is considered abusive.

Posts: 39 · Vonage Forum Junior Joined: Jul 24, 2005 Posts: 39

Just for notes, here is the factory firmware revision. It is the only one available at this time too.

Product Information
Model Number VWR
Software Versions
Gateway VWR-11.4.0-r060331-1.00.03-r060627.img
Boot Loader 1.3.8.1602

Posts: 23 · Vonage Forum Associate Joined: Nov 07, 2006 Posts: 23

I posted a few issues here which aren't in the list they sent you:

http://www.vonage-forum.com/sutra98492.html

For example, the device puts out significant interference and blocks certain network printing functionality (though I don't know to what extent).

This device, at least with the current firmware, is utter garbage and should not be sold to the general public. I've worked with better quality beta products.

Posts: 39 · Vonage Forum Junior Joined: Jul 24, 2005 Posts: 39

Found another one. After you disable to the wireless AP. When you go into connection status and click on the wireless radial button, the VWR hangs until you close your browser and reopen it and go back to the web console. I did this just to make sure when I disabled the wireless that the status would reflect that without having to get my laptop and test it. (not to mention i am 500 miles from home and have no way of testing it)
FIX Have the connection status for the wireless either reflect the last usage information before it was disabled or have it say "disabled" when trying to view it's status.

Posts: 10 · Vonage Forum Associate Joined: Nov 28, 2006 Posts: 10

You can add mine from the following thread:
http://www.vonage-forum.com/modules.php?name=Forums&file=viewtopic&p=100139#100139

In summary:

1) When using a static IP address configuration which differs from the "factory default out of the box" configuration (which uses DHCP, has Wireless enabled, etc.) the router locks up after 8-12 hours. The LAN port of the router stops replying to ping requests which verifies the device is locked up or no longer on the network. In addition, phone and internet service is gone at that point. Picking up the phone, there will be a dial tone, however when dialing a phone number outbound, nothing happens. The only resolution is to reboot the router by pulling the power cable. Service will then be good for another 8-12 hours until which time it locks up again.

2) After the above happens and the router is rebooted, Virtual Server settings (used for port forwarding) are not retained and must be re-entered for all port based services such as WWW, FTP, POP3, SMTP, etc. After a few days, the router eventually "remembers" its Virtual Server settings and no longer do these settings need to be entered after a router lockup. However, if the router is factory reset and then re-configured with a static configuration, the above symptoms can and will be reproduced until a few days have gone by.

3) Tech support's response to this: Use only the default factory reset configuration. A lot of good that does me with a home network which has static IP addresses. Unacceptable cop-out defense to an obviously pi**-poor product that is nowhere close to being ready for production use.

4)
Default username: user
Default password: user
Questionable security measures there out of the box. At a very minimum, the username and password should not match. Let's not make hacking any easier than absolute necessary.

Posts: 10 · Vonage Forum Associate Joined: Nov 28, 2006 Posts: 10

BTW.. cancelling Vonage this month now that the busy holiday stuff has passed by...

Posts: 1 · New Forum Member Joined: Jan 04, 2007 Posts: 1

I received my new D-link wireless router yesterday but can not add new management rule. Not sure if this is a defected router or I am doing something wrong. I am trying to port forwarding and when I try to add new rule it goes to a blank page. Can anyone help?

Posts: 39 · Vonage Forum Junior Joined: Jul 24, 2005 Posts: 39

Just to comment on their "poor ftp transfers" Poor is an understatement. More like poop. 35MB upload to ftp site behind VWR 3 hours 52 minutes and climbing. Evil or Very Mad

Used my WRT54G, 5 mintues.