D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: Rimtech on January 10, 2009, 02:43:29 PM
-
I do several large file transfers a day across my wireless network.
I am a software dev at a major canadian company and I have to transfer very large files across my home office network. To expedite this process, as the files are getting larger and larger (20GB, sometimes 30GB and growing), I have recently purchased a DIR-655 wireless router and a DWA-552 wireless nic, both of the Xtreme N variety.
Since I got it, I have noticed that several times throughout the day (4 or 5 times a day) I will get an interruption in my wireless service.
I check the logs on my DIR-655 and I notice "Wireless restart" events.
What does this mean, why is my DIR-655 doing this, and how do I stop it. I have tried multiple channels I know to be clean.
My previous G network had no issues whatsoever. This is completely new and isolated to the DIR-655 from what I can tell.
I called D-Link tech support before I say the "Wireless restart" events in the log, and the person on the other side of the phone seemed to have no idea what they were talking about, and instead told me to disable "UPnP" and "Multicast Streaming" in the router's UI. Needless to say, this hasn't fixed the problem.
Please help!
The place I bought the router from wont do an exchange unless I have a D-Link case number, and it seems like the router is defective based on these random "Wireless restart"s!
-
Are there any more devices connected to the router?
What is the firmware of the router?
Regardless of this required info, you might want to fiddle around with the transmission rate (http://192.168.0.1/Basic/Wireless.shtml). Default setting is Auto, but you might want to turn it down manually to where it is stable and gradually up the setting until it becomes an unstable connection. On auto the router tries to get the best speed possible, but as you may or may not know a radio signal will vary (there's interference all around us from walls, DECT phones, Microwaves etc, as well as other AP's from neighbours perhaps), causing the transmission speed to fall back (and sometimes even cause be the cause of disconnects).
You can also try to set the 'roaming' feature in your NIC driver settings to low, roaming can be useful but can also disconnects.
Let me know if it works.
-
There are other wireless devices connected to the router that are also affected when this "Wireless restart" happens which leads me to believe that this is an issue on the router, and not on any of my WiFi adapters.
Read... when a "Wireless restart" occurs in the logs, all of the wireless clients on my wireless network get disconnected at the same time for 3-5 seconds, effectively terminating any active file transfers.
If there is an issue with signal with a single client, then only that single client affected should get disconnected. So what you're saying doesn't help my situation.
The wireless on the router is going down and up periodically throughout the day, not my NICs.
According to the status>wireless page on the router, the speed that is auto-negotiated is usually 270mbps.
I have fiddled and fiddled. Believe me. Right now here are the settings I am using, as recommended on this forum by the stickied posts.
(http://hdguild.kicks-ass.net:8080/img/wireless.png)
-
Firmware version?
You'd be surprised what can trigger a wireless restart. Your call.
-
Hardware Version: A3
Firmware Version: 1.21
-
If it is modem or firmware related you can check by downgrading to the most stable version thusfar, 1.11.
You'll lose Shareport and Guest wireless (only available in V1.21), but it's worth a try.
ftp://ftp.dlink.com/Gateway/dir655/Firmware/dir655_firmware_111.bin
-
you're saying 1.21 isn't stable?
-
No, saying your having issues with your device and that changing the firmware may have a positive effect on your issue. Have you ever seen completely bugfree software? :)
-
Do you own this device?
-
The DIR 655? Yep.
Edit: And I don't have wireless restarts with the 6 wireless devices (and 3 wired).
-
What firmware version are you running?
Can you go into your logs for me and see if you too are recieving the "Wireless restart" events?
Thanks :)
It's possible that it's happening to you aswell, but you're just not noticing because you don't utilize the connection as much as myself.
-
No wireless restarts, I'm running 1.21. Sorry...
No, I don't push 30 Gb over the network daily. If that's your reference you wil not find many users with a comparable situation. I receive all my logs through email, so I would be very surprised I missed a line. And the wireless connection is used 4 hours a day for the home theatre/streaming movies. I would certainly notice a wireless restart I would say (yes, I know the player has a buffer...).
Practical solution is to install a FTP server on your laptop that supports resume.
-
This is the same problem I have been having with this router since I purchased it in November.
Wireless restarts. On my network I run 1 laptop, one wii, and a blackberry pearl. I'm here in canada, and am using shaw high speed.
I use ftp daily for probably around 1gb of transfer per day.
This past week my windows partition crashed, so I've been running in linux all week. The restarts are as present as ever.
I'm using an Atheros super G card.
So, if, theoretically, the source of our problem was the same. It might be some freak response to something Shaw is pumping down the line. (If you company is using shaw.) It could be a computer in your organization with an atheros super g card. Or a blackberry pearl connected to the router. Or the router hates ftp.
I've been dealing with this problem for two months now, I recommend trying a replacement, or a new router.
-
Well, I can rule FTP completely out of the equation for me.
I have no pearl, no wii. I'm also in canada, and my provider is awesome Vianet, they block nothing and allow everything.
My configuration is...
Motorola Cable Modem----->DIR-655
Wired Clients:
----->Linksys Sipura VOIP Gateway
----->Windows XP MCE SP3 box
Wireless Clients:
~~~~~> Windows XP Pro SP3 box A (D-Link DWA-552) (Atheros AR5008 based chipset
~~~~~> Windows XP Pro SP3 box B (Linksys WMP54G) (Ralink 2500/rt61 based chipset)
~~~~~> Windows XP Pro SP3 laptop C (Broadcom chipset based 802.11g card)
So I do have a fair mix of wireless vendors' chipsets connecting to this thing. Previously I was running DD-WRT (custom linux firmware) on a WRT54G v4 router.
From my observations I can tell you that it is not an issue with any of the wireless cards, as they have all demonstrated flawless communication with several other wireless AP's.
I talked to D-Link tech support tonight and they advised me to do the following:
>Make sure UPnP and Muticast streaming are disabled.
>Change wireless channel to 10
>Change beacon period to 80
>Change RTS threshold to 2100
>Change Fragmentation threshold to 2100
>Change DTIM interval to 5
I was advised that if this does not resolve the problem to call back and ask for a sr. level technician.
I'll keep you all updated as to whether or not this resolves my problem. I will stress test it for a day or two.
-
I vaguely remember that there used be another wireless restart issue somewhere on the board with a Linksys VOIP gateway. Could be mistaken though.
-
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.
-
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.
-
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?