D-Link DSR-250V2 Unified Services VPN Router, Multi-WAN Giga, Failover, Load Balance, IPSec/PPTP/L2TP/OpenVPN, Dynamic Web Content Filtering, Application Control, Captive Portal

Ce commentaire ne va pas vous permettre de juger la qualité du produit, mais plutôt de la version reconditionnée après plusieurs problèmes suite au firmware corrompus plusieurs appels et échanges par mail avec le Support de Link, il faut être avancé pour pouvoir régler ce problème. Outre ça une fois l’OS réparé dans les paramètres, le routeur avait été allumé pendant 7 ans ce qui pour un Routeur est déjà très bien. Soit c’est de la seconde main. Mais du à cette utilisation, plusieurs services essentiel et détection d’interface dans les ports n’était plus supporter ou dysfonctionnels engendrant ici une erreur hardware qui m’a découragé et m’a amené à renvoyer le produit.

Made in Taiwan. Get this one only , it works well.

The router works well. Configured it in just a couple of minutes. I was very happy with it until I connected a couple Yealink IP Phones to it. The Yealink phones would not obtain an IP address from the DHCP from the router. I verified VLAN settings, switch settings, I even went as far to try to do an IP reservation via MAC address. It was then that I found the problem. It's not my Yealink IP phones but rather the D-Link router would not recognize the Yealink MAC address as valid. I know Yealink is a relatively newer manufacturer, but not that new. If the D-Link router will not recognize the MAC address as valid, DHCP will not assign an IP address. In case you're wondering, yes I tried statically assigning IP address to one phone to see if would work. But after autoprovisioning it with our VoIP provider, it would lose it's IP address. Besides, who wants to statically assign IP address on a bunch of phones. So in summary, I either have a defective D-Link router or they need to update their firmware and OS to recognize Yealink IP phones. Are there other MAC addresses it doesn't recognize? That's not a bet I want to take so I returned it. The replacement TP-Link router assigned IP addresses to the Yealink phones with no issues.

The default configuration of this router is great. Plug-and-play. However: Trying to use the features this router purports to have, particularly bandwidth management and QoS prioritization, frequently results in the entire network losing connectivity -- even when settings are removed. The only fix thus far has been to reset the router to factory defaults. Memory utilization is consistently above 80%, even at factory defaults. That doesn't leave a lot of wiggle room to make changes that could require more memory. The most recent firmware as of this comment does not address the issue. The DSR-250N worked great compared to this. I regret getting rid of it, despite learning of it's security vulnerability. I regret purchasing this router.

First be sure to update firmware! mine came with an almost unusable version I am embarrassed to admit that I spent 2 evenings trying to set this up before checking and installing updates my thinking was to get the basics setup before allow connecting to the Outside world. I love the way the LAN clients DHCP settings all of the fields can be sorted this sort is missing for the Port forwarding settings. Current firmware version 1.02.B008 I cannot find anyway to change the default Management GUI IP address from the default of 192.168.10.1 If I change the LAN interface from the default IP you can no longer access the Management GUI from the LAN Limit of 15 port forwarding items and even the inactive ones count towards this total allows you to add just not save 16 and beyond. Can not enable NAT hairpin, loopback or reflection makes this router worthless for my use example I have a server that is a local computer inside the NAT firewall lets say it has a service listing on port 1234 I “port forward to the WAN port 4568 there is no problem accessing the service outside the network however I can not access it inside LAN on port 4568 using the WAN address. All other routers I have used have a feature that loopback the call as if it came from the WAN side if using the WAN address.