If you care to give us more details here regarding your problem then we can better help you in troubleshooting. Not everyone has the same setup, networking and external environmental conditions.
Help us help you.
My details haven't changed except that I upgraded to the 1.01 firmware. No one setting--except disabling .11n--allows wireless to function on an uninterrupted basis, nor does any combination of setting produce any sort of different result. And frankly, I'm only documenting my findings here as a possible assistance to others as I expect that my own training and experience is further along than most people here. This isn't just flailing about for me. I have processes that I follow, too, but they're based on working in an enterprise environment more complex than most and they include a fair-sized WLAN covering a few hundred thousand square feet over three buildings in two locations. I
do have an idea of what I'm talking about.
True claims of interference apply only in limited circumstances related to the public spectrum such as ill-fitting microwave doors or older 2.4GHz cordless phones and baby monitors, but you can't find those without special gear. The level of activity required for routers to interfere with each other in such a way as to completely prevent all activity is so incredibly high that it is unlikely to happen outside of a constructed environment and would show up immediately in a traffic capture. The people that write the standards factor in dense environments. Degraded performance due to congestion, yes, that can happen more easily, especially in the 2.4GHz range, but there will be patterns to it correlating with local network activity and thus varying over time (unless you have an active attacker). Those are more easily addressed by channel changes or perhaps settings adjustments.
But the problem that's been most often described in this thread is a cessation of all activity. I've been capturing all of the traffic for the past 27 hours and counting, about 6.5GB in total so far. I started it when my router stopped responding. I could see only beacon frames at the time save for my various devices--my Roku, my TouchPad, and two cell phones--trying to authenticate. They sent out probes and access requests, but never received a single frame in way of reply. I rebooted the router, still capturing traffic, and watched as my devices connected. It's happily chugging away now with three cell phones, the TouchPad, the Roku, and a notebook other than the one capturing traffic. Could it be one of them sending a mangled frame? Perhaps. But if that's the case, then it's the router's fault for not properly handling it, something it should be able to do because collisions, reflections, refractions, and sometimes plain old broken software produce mangled frames all the time.
Sure, I could call it in, maybe get an RMA. But what happens if it happens again? I'm in the same boat. I'd rather try to find something specific in the traffic and provide that to DLink in hopes of getting it fixed for everyone else with the problem than flail about trying random things. I realize that the path I'm taking isn't something that everyone can do, but that's why I'm doing it. Should this fall short, I've another path that I can take, but it's time consuming and kind of a pain to set up as I have to dig out some gear and set up a bunch of virtual cards. But I will do it when I have an idea of the parameters involved, and I'll share what I find should no matter the path or outcome.
Author
Topic: Wireless dropping Issues (Read 62471 times)