Update:
I bought a dir-655 last night (as a temporary replacement until I get new 4500).
What a nightmare !!
I cannot wait to return it to the store (but have to wait for my replacement 4500 first).
The dir-655 is buggy and slooooow !!!
(No wireless restarts, though from what I can tell from their cryptic logs !).
The web interface on the 655 is at least 5 times slower (no joke) compared to the 4500.
Almost every change/update you save on the 655 requires a restart - typically 30 seconds or so (wasted).
At first, this 655 was not "seeing" any hard wired or wireless clients. I had no idea why - it almost seemed that it was not aggressive enough at giving out dhcp ip addresses.
EVENTUALLY, it populated itself with clients, so then I decided to reserve ips for these devices.
I almost ripped this router off the desk and threw it into the garbage it was soooo frustrating to set up.
The router got confused about ip addresses and what was dhcp vs reserved so many times that even after "saving" the changes, things did not set up correctly.
I actually had to reset to factory settings and reboot this thing about 3 times - just to try and get it configured properly.
Even now, with all clients connected, when I go to the status screen and click on wireless - it takes (forever) to populate the screen and is hit and miss whether it actually decides to display the wireless connected clients or not. Unbelievable !
Regarding QoS, I have set up different priorities for traffic and when I check the internet sessions, it does display the streams, however it does not display the priority - so i have NO way to verify if my QoS is working or not.
Regarding the logs - for some reason they LOOK very different than what I am used to on the 4500. For one, they are broken into MANY pages, rather than allowing them all to be viewed on one page, which makes navigating the info a pain. Plus, many of the messages it displays are strange:
For example, what is all this garbage ?
Priority Time Message
info Dec 14 21:05:12 [ 5641.620000] m_table count= 1 Del 01005e00 00fc000b
info Dec 14 21:04:14 [ 5583.620000] m_table count= 2 Del 01005e7f fffa000b
info Dec 14 20:54:28 UDHCPD Inform: add_lease 192.168.0.67
info Dec 14 20:54:24 UDHCPD Inform: add_lease 192.168.0.67
info Dec 14 20:48:56 [ 4665.780000] m_table count= 2 Add 01005e7f fffa000a
info Dec 14 20:48:45 UDHCPD sending OFFER of 192.168.0.55
info Dec 14 20:48:18 [ 4627.470000] m_table count= 1 Add 01005e00 00fc000a
info Dec 14 20:48:00 UDHCPD sending OFFER of 192.168.0.97
info Dec 14 20:47:57 [ 4606.000000] module arch cleanup nf_ubicom_streamengine_default_classifier: OCM instruction memory free of 0 @00000000
info Dec 14 20:47:55 [ 4604.940000] module arch cleanup sch_ubicom_streamengine: OCM instruction memory free of 0 @00000000
What a collossal nightmare. I cannot imagine how Dlink can get away with selling such a shoddy product.
Perhaps the processor on the 655 is junk, I don't know, but I have a theory.
The HARDWARE revision of the unit is B1.
It would almost seem that Dlink does a good job on their routers with the FIRST/original Hardware revision.
When they make a newer version, the problems seem to start.
Even Furry noted that his 4500's are on A1 (which work fine), and most problems are on devices with A2 (which mine is).
This dir-655 is on version B1 - so who knows "what" they've done to the hardware to make it this excrutiatingly frustrating to work with.
In the store, they only had 655s with h/w rev B1, so no luck there.
I only hope that I get my replacement 4500 soon, so I can take this white albatross back to the store for a refund - as its buggy behavior is making my blood boil !