Print

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

[Rimtech]

Of course, now that I have the wireless restart issue fixed, I am starting to notice another issue...

When I download using the very popular p2p program bittorrent, say a linux DVD image ISO, over my wireless connection... my LAN ports are somehow completely neglected by the router.

Figure this... 270mbps wireless connection, no errors or dropped packets.... constantly pinging 192.168.0.15  (a wired client)... normal ping responses are 1ms, 2ms occasionally...

However, with bittorrent active after 10 minutes, with lots of active IP connections, the ping responses to that wired interface goes up to 2000ms and higher, even getting "request timed out".

When this happens, I can still ping the other wireless clients perfectly, with normal 1ms response times, but for some reason when i ping the wired clients, the requests time out.

My VOIP line goes dead, or gets severely choppy, and my wired xp mce box cannot communicate with anything internal or external.

So based on my observations what happens is this... a moderate amount of ip connections occur, 150 or more, which seems to tax the router or QOS so much, that the router is unable to process LAN traffic, and can only deal with WLAN traffic.

The DWA-552 generates far too many DPC latency issues for my liking, not only every 60 seconds but it doubles the normal dpc latency of the machine on a constant basis.

Too many issues for me. Now you might say that it's just "user error", but I'd like to think that with over 5 years in software development, aswell as possessing both CCNP and Network+ certifications, I'm smart enough to get a simple wireless network going.

Maybe I just have bad luck and got 2 defective components at the same time, I don't know. But the fact that I call D-Link tech support and speak with 3 or more levels of support based out of the phillipines that can barely speak english and have no idea what TCP/IP even is happens to be, and they dont even offer my an RMA, but just keep trying random things with me that they hope will solve the problem, it's quite disappointing.

I expect more from a company like D-Link, especially from their "premium" Xtreme-N product line.

Both of these products have been on the market for so long now, there is really no excuse for the unreliability and stability issues of both the DIR-655 and DWA-552. And it's not just me. I've read these forums and many others and I know other people are having these same problems and more.

I must commend D-Link on their clever marketing of the DIR-655, and the amazing features that they have incorporated into it. Aside from the stability/reliability issue, it seemed to perform very fast and the QoS did seem to work well, the interface was well designed with excellent documentation.
In short, the DIR-655 is nothing short of remarkable on paper, but in practice it's absolutely horrible.

I am very fortunate that the vendor from which I purchased these products from has graciously decided to permit me to return them for a full refund. At this point in time I will be forced to discontinue my customer relationship with D-Link and move onward to an alternate networking solution. D-link's brand and product positioning has taken a definate hit from this customer's perspective. As an opinion leader in my IT support group, I will no longer be able to recommend D-Link's products or services to my peers and colleagues.

Thank you all who have tried to help me. It's certainly been a learning experience. Best of luck in all your endeavors, but it wont surprise me if this post gets deleted.

[EddieZ]

Nice long story but a well configured BT client has no impact on the LAN whatsoever. Neither does it flood the router. Believe me when I say that with a few settings in my BT program I can kill every router. In your "150 or more" connections you're leaving out the incoming connections and the numerous connection attempts that don't persist.

So either you have a defective router or your BT setup just [exploitive deleted].

Edit: And if we're 'taking measurements' here, what's 5 years against about 24 over on this side...
At least show us some logs and packet captures to teach us why your P2P kills your router and my P2P does not kill my (identical) router. I must be doing something wrong when all works fine.

[funchords]

However, with bittorrent active after 10 minutes, with lots of active IP connections, the ping responses to that wired interface goes up to 2000ms and higher, even getting "request timed out".

Very interesting. Is WISH enabled?  If you turn it off, does this behavior change?