You have to take every review with a grain of salt.
For some, what they are "used to" is garbage, so practically "anything better" will seem like the greatest thing on earth.
I have been spoiled by owning a DGL-4500, it would seem.
My critique of DLink is probably that their newer devices (with newer UserInterface updates) took a step back for me.
I am not certain with which model and on what date DLink changed their "standard" UI, but they made some changes that I cannot stomach.
Some of these changes are part of the reason why I have inevitably decided to keep my dgl-4500.
Here's my take - below:
DIR-857 - What I LIKE:- Power/range is the best I have seen so far for both 2.4Ghz and 5Ghz (comparing it to Cisco e4200v2)
- Dual radios
- Media Server and USB 3.0 capability
Just so you know, it is not "all" bad, but my issues are primarily with the UI, as I will explain:
DIR-857 - BEEFS:- As mentioned previously, the UI is a few steps "backward" from what the dgl-4500 has, in useability, presentation, and capability.
You do realize they are using the DIR UI vs DGL UI right? What browser are you using to display the UI?- Fonts - The font size/type now used is too large, taking up space where they could actually fit more information - compared to the dgl-4500, the 857 looks "antiquated"
Can you post a screen capture of the UI?- Internet Sessions: a visually ugly layout - in table format. BIGGEST beef here is that there is a lot of information, but they have OMITTED to display the "Priority". So if you have set up QoS, you'd never see which internet sessions are using that QoS scheme (properly). In other words, it is one thing to configure your device, but it is very satisfying to see that it is actually "working" in the manner that you set it up. The dgl-4500 DOES show you the priority, by comparison.
- Wireless clients: Very buggy. It sometimes displayed all clients, but not always (both N and G). It actually was quite unreliable - even though a wireless client was connected, it would not display it.
How many wireless clients do you have connected a the time you looked at the status window? Anything more than 2 or 3 or was it just 1?- Wireless clients: Some clients that were set up for n, would flip between a and n for no apparent reason - even when the wireless device was 5 feet from the router !
Was this on 2.4 or 5Ghz? or both? How many clients were connected when you saw this?- Wireless clients: Some clients would not display their reserved dhcp address - only 0.0.0.0 - even though, on the actual device, it HAD the correct IP, and the device actually worked on the network - yet the router could not display the correct IP - buggy as all hell.
Where was this not being displayed at? Network settings? Status? How many client devices were connected at the time? Does wired devices display or exhibit the same thing?- DHCP Reservation of IPs: As per above, there were issues in having the router "actually" give the address you specified to the actual device. Yes I saved, and Yes I rebooted - yet sometimes it just wouldn't "take" - very frustrating.
Wonder if someone should have a look via teamviewer at your router.- Reboot, Reboot, Reboot !!!: For almost every change, it wants you to reboot. Contrast this with the dgl-4500, which does not want you reboot for every mickey-mouse change you do. Do you see the REBOOT LATER option? The DGL did this as well. Both DGL and the 857 have the REBOOT LATER option.
- Reboot TIME: Holy @#$!. Not only do you have to reboot after every breath, when you DO reboot, it takes a lifetime - 60 SECONDS to reboot, and then another 30 SECONDS for it to fully come back up to being "useable". The dgl-4500 takes 15 seconds to reboot and another 10 seconds for it to be fully back up and running/useable. This reboot time is outrageous !
The DGL had a long reboot if changing some of the options as well. I would agree that reboot could be made a bit faster. However if your making changes and using the reboot later option, I'd rather have the router make the changes correctly in a timely manor than be rushed to set up something incorrectly.- UI speed: Logging in, changing pages, etc, etc was noticeably SLOWER on the 857 vs the 4500 - I would say easily twice as slow.
What browser are you using? Any 3rd party security SW enabled while doing this? Does this happen on different browsers? Try Opera, or FF?- DHCP reservations and device names: On the 4500, when I over-wrote a name for a device (for example if a printer had "UNKNOWN or something else that did not have much meaning" - I could over-write that with a name that was meaningful. The kicker here is that the 4500 would "keep" that new name and use it everywhere on all pages that would display that device. For some reason, on the 857, it only displays what "you" named it in the one dhcp reservations page - everywhere else it will only display what it saw via netbios, etc. A total consistency letdown.
I too have notice that after changing the name that its listed in the Reserved list however thru out the rest of the web page, its reported as unknown or blank. I would like to see this fixed if possible.- Logs are garbage: As stated before, DLink took a large step back here on their new UI (post the 4500 era). The type of info in the logs is not very helpful or user-friendly. To make it worse, on the 4500, the FONT was nice, plus it displayed ALL of the logs on ONE page. On the 857, it gives you about 5 lines or so, and then has you do "next page" to see the rest. Well as you know the logs fill up FAST in a router - so who on earth likes to have to click "next page" when there are 27 or more pages to view ? It is like tunnel-vision instead of peripheral vision.
LOGS on 857:Apr 12 21:34:52 DIR-857 daemon.info dnsmasq[1841]: read /var/tmp/hosts - 1 addresses
Apr 12 21:34:52 DIR-857 daemon.info dnsmasq[1841]: read /etc/hosts - 2 addresses
Apr 12 21:34:52 DIR-857 daemon.info dnsmasq[1841]: using nameserver 64.71.255.198#53
Apr 12 21:34:52 DIR-857 daemon.info dnsmasq[1841]: reading /etc/resolv.conf
Apr 12 21:34:52 DIR-857 daemon.info dnsmasq[1841]: compile time options: IPv6 GNU-getopt no-MMU ISC-leasefile no-DOCTOR no-NOWILD no-DBus no-I18N TFTP
Apr 12 21:34:52 DIR-857 daemon.info dnsmasq[1841]: started, version 2.45 cachesize 150
Apr 12 21:34:51 DIR-857 user.debug syslog: gpio create pidfile /var/run/gpio_power.pid
Apr 12 21:34:50 DIR-857 daemon.info avahi-daemon[1277]: avahi-daemon 0.6.30 exiting.
LOGS in 4500:[INFO] Thu Apr 12 23:28:33 2012 Sending log email before reboot
[INFO] Thu Apr 12 23:27:57 2012 Allowed configuration authentication by IP address 192.168.0.67
[INFO] Thu Apr 12 23:27:53 2012 iceman: Wireless system with MAC address 00215C2A480D disconnected for reason: Received Deauthentication
[INFO] Thu Apr 12 23:27:36 2012 Blocked incoming UDP packet from 96.30.153.114:39883 to 99.241.118.57:63764
[INFO] Thu Apr 12 23:25:38 2012 Blocked TCP packet from 89.89.170.227:59512 to 99.241.118.57:443 as control FIN:SYN in not valid
[INFO] Thu Apr 12 23:22:37 2012 iceman: Wireless system with MAC address 889FFA5E8CE7 secured and linked
[INFO] Thu Apr 12 23:22:37 2012 iceman: Wireless system with MAC address 889FFA5E8CE7 associated
[INFO] Thu Apr 12 23:22:37 2012 Above message repeated 1 times
Geez, now which one do "you" think is actually useful between the two ? Seriously DLink - what's up with your new way to display log information ? Useless.
To some point the details of the logs on the 857 are a bit out of average or home user understanding and do agree that Dlink could probable make the logs a bit more understanding in la-mans terms or at least segregate the detailed technical logs to the DEBUG section when used and then leave more of a summery logging when not using debug. I go agree that some of the information on the 857 logs is a bit beyond me. - Technical Terms: On the 2.4GHz wireless setup, there is a HT20/40 "coexistence" setting - that I have never seen before, and there is no explanation of what it is/how it is used.
I agree, there needs to be a help menu information regarding this. Even searching the web is kind of limited on information. 20/40 MHz Coexistence- QoS setup - Very messy on the screen. I like the way the 4500 has arranged the UI screen much much better.
Again, this is using the DIR QoS UI and do agree that DLink could clean it up a bit more and make each section a bit more distinguishable.Final thoughts:
If my 4500 were to bite the dust tomorrow, I would probably buy the latest Netgear and test it out before deciding whether or not I wanted to own the 857.
There is a ton of buggy behavior in the 857, and annoyances as I have pointed out above that would make me hesitant to own it.
If you can get past all of that, and once you set up your router, then "never look under the hood again", then you might be happy.
If you want a router that has a strong signal, then this is a good purchase for you.
In the end, for the money, I'll stick with my 4500 until something much better comes along - and it may not be a DLink product.
It would be nice if they actually took our feedback to heart and did some more development on their UI.
Yes, it seems you are quiet picky. 