D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-657 => Topic started by: TwinLinked on November 03, 2011, 06:56:50 AM
-
I have seen this post before and am having similar issues. The wireless portion keeps dropping every 30-60 minutes. The SSID still broadcasts you just cannot connect to it. If you change the channel or restart the router, you are able to connect again for 30-60 minutes.
I have tried all individual channels, reflashing the firmware, setting everything back to factory and still no luck. I took th router to my workplace and tried it there only to have the same problem. With little to no help from DLink support they eventually told me to take it back. Now I have a brand new one and the same problem!
At home I'm on Comcast with a Motorola Modem. I do have it set to mix B,G,N on WPA. QoS is off.
To make sure it wasn't interference or my modem I installed a Netgear D600 from work and had absolutely zero issues for the entire 2 days I had it running.
Any help would be appreciated. This seems to be more than an isolated issue.
-
Try single mode G or mixed G and N?
What security mode are you using? WEP, WPA or WPA2? Preferred is WPA-Personal. WPA2/Auto TPIK and AES.
What wireless devices do you have connected?
Any cordless house phones?
Any other WiFi routers in the area?
Some other things to try:
Ensure DNS IP addresses are being filled in under Setup/Internet/Manual? You can find these under Status/Device Info/Wan section.
Turn off ALL QoS (DIR only) GameFuel (DGL only and if ON.) options.
Turn off Advanced DNS Services if you have this option under Setup/Internet/Manual.
Turn on DNS Relay under Setup/Networking.
Setup DHCP reserved IP addresses for all devices on the router.
Ensure devices are set to auto obtain an IP address.
Set Firewall settings to Endpoint Independent for TCP and UDP.
-
Thank you, I will go through this check list when I get home tonight.
-
I solved the issue by turning off .11n. That is the culprit. There's something in the firmware that's not handling .11n properly. Even crowded wireless shouldn't cause problems like that.
-
Before you assume it's the FW, you should do some trouble shooting.
Do you have alot of wireless routers near by?
What wireless modes were you using? Did you try Mixed G and N or Just Mixed All?
I solved the issue by turning off .11n. That is the culprit. There's something in the firmware that's not handling .11n properly. Even crowded wireless shouldn't cause problems like that.
-
I do this stuff for a living. There are about a dozen nearby SSIDs. Any setting that involves .11n results in failure after 30m to two hours. The IEEE specs are quite clear that radios should work properly with interfering APs in the area. Something is off, though I've not had the time to dissect the wireless frames to figure out what it is.
-
if you have other WiFi routers near by then they could be a cause of your problems. Have you used InSSIDer application to see whats around?
What modes are you using? Mixed ALL? What happens with single mode G and single mode N. Notice any issues while using single modes? Try Mixed G and N?
My 657 works great on N mode however I only have about 3-4 routers near by me.
-
No, I've used Kismet under Linux with an Atheros card, much as I do at work when I do site surveys for wireless installations. As I said, there are about a dozen around me, several of which are running .11n. It's not interference--it can happen at early hours of the morning where the overall level of wireless traffic is almost nil. In any case, density like this shouldn't be a factor anyway.
If the router is having problems handling even the beacons from the surrounding routers, which is the source of the majority of wireless frames at those hours, something is definitely wrong internally.
-
I would presume that your issues lie with the routers that are near by you. There is a guy over on the 855 forum having the same issues, A LOT of routers near by and even though the router is trying to find a good channel, there just isn't enough open and interference from the other routers is effecting his signal internally to his area.
Have you tried to lower the power out put of the router to see if this might help?
One thing I would do is to move the router to a friends or family place. See if the problem is traveling. Need to isolate the router of your current environment.
-
The issue occurs when I connect devices to my network. I have, for example, seen network failures when I connect my phone while streaming on my Roku. Turn off the phone's WiFi and it resolves itself. Phone, right? Nope. Power up my TouchPad and it does the same thing. Sometimes, the Roku is off, and it happens when my girlfriend's notebook is connected and I connect my notebook.
Even if it were the presence of routers nearby, the 802.11 standard allows for that. It even allows for a lot of them nearby, and .11n was written specifically with coexistence in mind (hence why it detects the presence of 20MHz APs and doesn't use 40MHz features around them).
I still have not had time to pin down the issue. The fact that .11g works perfectly fine tells me that it's something in either the chip or the firmware covering .11n functionality, and it needs to get fixed.
-
Does this happen over single mode N, auto channel scan enabled and disable?
Is WMM enabled?
ny other WiFi routers in the area? Use InSSIDer (http://www.metageek.net/) to find out.
And yes other router near by can and will effect other WiFi routers near by depending on how many are hear, frequencies and channels used. We are noticing that as more and more people get WiFi routers, specially in metro cities and in apartment complexes that even running N modes is having a problem due to the congestion of wireless radios and there all trying to broadcast singles and trying to maintain channels that are being used up. Yes the wireless standard allows for presence of other routers however when channels and freqencies are all being used up, then you start to run into problems.
Example:
http://forums.dlink.com/index.php?topic=41071.0 (http://forums.dlink.com/index.php?topic=41071.0)
One thing you can try, take this router to a friends or family's place that had Internet. Hook it up and test with Single mode N.
Maybe someone can review your router settings with you using teamviewer. (http://www.teamviewer.com)
Not try to say your wrong here or that there isn't a problem with the router. Just looking to troubleshoot here as much as possible.
-
I'm voting firmware. I'm running inSSIDer now and there is one other wireless router in my neighborhood. We're locking up every 15-20 minutes. Following other poster's advice to disable .11N to see if it improves otherwise taking router back to the store.
-
Ok, I'm testing my unit out as well on single mode N and will post results here.
Keep us posted on what Single mode G does.
-
Been having dropping issues also been reading the threads on this forum trying the various recommendations given the problem i face is that i got a Wii that only got B/G and my netbook got N so ive tried running everything in G mode but that just increased the dropping also checked so i wasn't broadcasting on same channels as neighbours currently running without the QQS engine turned off since that damped the dropping
that's my experience so far didn't have that much problems with my old 655 router (except lighting kinda broke it :P)
-
Try mixed G and N?
What security mode are you using? Preferred security is WPA-Personal. Try WPA/TPIK only.
Any cordless house phones?
Might manually set Auto Channel scan to a manual channel. Make sure your not broadcasting on an used channel. Try 1, 6 or 11 first.
Turn off Short GI and Extra Wireless Protection if you have it. Under Advanced/Advanced Wireless.
My 657 is set for single mode N, WPA2 and AES only. I have a iPhone and a wireless xbox that connects to it. Been working great. Seems like something in interfering with your maybe.
-
ohh sry forgot to include current settings
802.11 Mode : 11gn
Channel Width : 20 MHz
Channel : 6
WISH : Inactive
Wi-Fi Protected Setup : Disabled
Any cordless house phones?
No
What security mode are you using?
AES Only, WPA2 Only (Wii Limitation cant handle TKIP)
So im already running as you suggest but still there is something and ive already scanned channel ranges using inSSIDer so i dont collide with others works fine if i only use one thing at a time but if i used Wii, netbook and if a buddy is visiting and hes laptop is hooked up then everything fails so i agree something is interfering but i havent found what so far just wanted to run the config by this forum too see if there is something ive missed.
-
What Hardware version is your router? Look at sticker under router.
What Firmware version is currently loaded? Found on routers web page under status.
What ISP Service do you have? Cable or DSL?
What ISP Modem do you have? Stand Alone or built in router?
What ISP Modem make and model do you have?
If this modem has a built in router, it's best to bridge the modem. Having 2 routers on the same line can cause connection problems.
If DSL and using PPPoE option on the router, ensure that the ALWAYS ON option is selected, and not the On Demand option.
Some things to try:
Ensure DNS IP addresses are being filled in under Setup/Internet/Manual? You can find these under Status/Device Info/Wan section.
Turn off ALL QoS (DIR only) GameFuel (DGL only and if ON.) options. Advanced/QoS or Gamefuel.
Turn off Advanced DNS Services if you have this option under Setup/Internet/Manual.
Turn on DNS Relay under Setup/Networking.
Setup DHCP reserved IP addresses for all devices on the router. Setup/Networking
Ensure devices are set to auto obtain an IP address.
Set Firewall settings to Endpoint Independent for TCP and UDP.
-
What Hardware version is your router? Look at sticker under router.
Hardware Version: A1
What Firmware version is currently loaded? Found on routers web page under status.
Firmware Version: 1.00
What ISP Service do you have? Cable or DSL?
DSL
What ISP Modem do you have? Stand Alone or built in router?
Brigded Modem (it just supplies wan interface)
What ISP Modem make and model do you have?
Thompson (gags, but again its bridged and all wifi features are turned off)
If this modem has a built in router, it's best to bridge the modem. Having 2 routers on the same line can cause connection problems.
Already done that first thing i did when i experience the problems
Some things to try:
Ensure DNS IP addresses are being filled in under Setup/Internet/Manual? You can find these under Status/Device Info/Wan section.
running google DNS 8.8.8.8 and 8.8.4.4
Turn off ALL QoS (DIR only) GameFuel (DGL only and if ON.) options. Advanced/QoS or Gamefuel.
Already turned off
Setup DHCP reserved IP addresses for all devices on the router. Setup/Networking
Ensure devices are set to auto obtain an IP address.
Always reserve ip for all my devices, former network techican so i love structure
-
I would try to Update to v1.01.
The only thing i saw with my v1.00 was that the web page ui would hang after doing some tweeking or setting up. v1.01 has cleared that up.
I love structure and management too. Easier that way.
-
on the .SE domain only 1.00 is available so i guess .com has the 1.01 ?
-
Where are you located? EU or NA?
-
Sweden, EU
-
Ya I see there isn't any 1.01 yet. I would hold off or contact DLink and ask. I presume there might be comming soon, however know that DLink has changes there priorities with FW since this WPS vulnerability has cropped up, there focus is fixing that and any other releases wont be done until thats complete.
-
Well i updated to 1.01 but that didn't seem to help since it drops not as bad as before but still..
-
How about the DWA ? Is that all up to date as well?
Did they post 1.01 for EU units?
-
Well its both my wii and my netbook that fails so the guilty party in all of this has to be the router
-
Did you follow FW update sticky?
How about a factory reset and set up the router from scratch.
Turn off ALL wifi devices accept for one and test with single mode G then mixed G and N.
Turn off Short GI and Extra Wireless Protection if you have it. Under Advanced/Advanced Wireless.
-
Short GI was still enabled gonna turn it off and see that makes any significant matter
-
Maybe someone can review your router settings with you using teamviewer. (http://www.teamviewer.com) If needed.
-
well i havent had this much problems with my 655 and the only reason i changed from that was that lightning broke that one and now its running on the same simular settings as 655 and the interface is pretty much the same, with the 655 i had no issues with wifi dropping nor bad speeds so might it be possible that i just got a router that doesn't work proper
-
Where did you get FW for this router? I see nothing has been released for the EU as of yet for v1.01.
-
So is this v1.01 working for your router? Where did you get it from?
-
its working to the extent that it drops a little less and i got it from mailing support at dlink but still the overall experience with this router hasn't been as good as with the DIR 655 where i had 0 issues except that it wasn't lightning proof :P
-
None I guess.
-
Well as it seems im not alone in this with wireless being messed up and since we covered the basics and tired most options there has to be something that makes wireless mess up
-
I had the same issues with wireless dropping in random intervalls. I tried all options listed above, and it seemed that nothing worked. But than I tried to disable the n-mode running b+g and the problem has totally dissappeared. I have the A1 hardware version and the v1.0 firewire. I am sure that there is a bug in the firewire as Martin Blank wrote above.
-
I would agree too that but i cant disable G since my Wii needs it so stuck with the "bugs" until a fix is available
-
How about running a separate AP or router for the Wii? That way you could run N mode and use the other AP for the Wii and G devices. ::)
-
URGH... rather see D-Link do actual test to determine if there is a bug present since so many have the same problem again i truly hope that D-link personal checks these forums
-
currently there priorities are working with the main developers of the WPS system as that has been compromised so ALL Mfrs are having to refocus on getting that fixed. I've been told that there won't be any new FW releases until that issue has been resolved. No time frame either when that will be.
-
ofc WPS should be first priority then i hope that they focus back on the firmware and take a look at these forums cause its not just me thats had this problem
-
Time will tell.
-
OK I am confused after reading all 3 pages here. Why not simply RMA the defective units for ones that work. Why are folks settling for disabling features that you paid for when you purchased the router rather then holding D-Link responsible to provide working units?
Jeff
-
Trying to troubleshoot to see if there are other causes to the issue before RMAg. Could be external interferences that can cause wireless to not work well. If we can trouble shoot some of the options then that helps narrow down if the unit should be RMAd or not.
-
Trying to troubleshoot to see if there are other causes to the issue before RMAg. Could be external interferences that can cause wireless to not work well. If we can trouble shoot some of the options then that helps narrow down if the unit should be RMAd or not.
Maybe it is just me but if your unit works in straight .11g but not in .11n then that says to me it is the unit. If you have to turn off QoS to get your router to work then you are not getting the use of features you paid for.
Personally after reading this thread, a couple of other threads, and my personal experience with D-Link I really wonder how they stay in business. It has taken me 9 months to finally get them to RMA my defective DGL-4500 then they send me not 1 but 2 defective replacement units. Then I am told that the DGL-4500 is EOL stage so I can pick a unit of the equivalent value. I pick the DIR-857 which is on the D-Link site I was sent to pick a new model from only to be told it is not being released till Q2. So I decide on the DIR-827 only to be told it is out of stock. Even though it is available via the D-Link Shop. I am told that the vendors get priority product shipment and units are not held back for potential RMA issues. So I settle for a DIR-657 which is being shipped out to me today. Now reading this forum I am just hoping that I am not going to have to RMA the DIR-657 when it gets here.
Jeff
-
Sorry you had some issues with your routers man. After all that, I might guess that you have some external interferences that might be causing your problems your seeing however with out knowing a bit more from you thats only a guess. I have had 3 4500s, sold one, have a DIR-825, DIR-657 and now working with a DIR-655 and ALL have performed very well for me.
There are some troubleshooting steps in finding some of the problems that arise to router conditions. We've notice over the past year or 2 that being in a hight populated area such as a apartment complex or city or neighborhoods that more and more people are getting more wifi routers, thus this is using up all the channels 1-11 on 2.4Ghz and being either close or not too far away is impacting how these routers work and all get along in the same area. I call it WiFi Congestion. I have only a couple near by me so channels are pretty open. Other considerations is ISP service, lines from the telephone pole or box to the house or building. What condition are they in? I have seen many that the ISP lines are not in good condition which leads to bad or low signals going to the ISP modem. From there, if cable ISP, tv line splitters can impact the signal as well and lower it going to the modem. It's always the standard thinking that it's the routers fault when something happens. After doing a bit more troubleshooting, other issues probably can be found and would help fix or resolve issues elsewhere that are not router related. Other issues can be ISP modems. Having built in routers in modems is having a configuration problem here and there. WE can get past most of them.
I'm not going to say that routers are not completely at fault and I presume that some are defective. However I've been told by DLink that most problems seen are 90-98% end user configuration or external environment related. Working with people here in the forums over the years seems to prove most of that. Seen a lot of issues get resolved with a bit of troubleshooting and help.
I would recommend that you let us help you out and see if your problems with these routers are in fact HW related or the problems lie elsewhere. If not then you'll need to find a different solution elsewhere.
-
I'm not going to say that routers are not completely at fault and I presume that some are defective. However I've been told by DLink that most problems seen are 90-98% end user configuration or external environment related.
From personal experience with D-Link I find that hard to believe.
In the case of my original DGL-4500 it is clearly a hardware issue. The router will randomly do a hard reboot or power cycles down if you prefer. It started doing it about 3 weeks after I purchased it. What bothers me most about this one is that it took 9 months to finally get a tech at D-Link willing to RMA it. Seems D-Link only allows so many RMAs a day as at one point I had a tech tell me point blank "the unit sounds defective but we can't RMA DGL-4500s today".
Then I finally got a RMA approved last month and they wanted to charge me $250 that would be refunded 7 to 10 days after they received the defective unit. I got a CS II manager to waive that fee. But then the replacement unit showed up absolutely filthy and would not broadcast the SSID so I got that one RMAed and it's replacement also would not broadcast.
I was on the phone with D-Link tech support for almost 2 hours troubleshooting the second unit before they agreed to RMA it. I do not believe that the problem with either of the replacement units was due to interference. I tested both units sitting right next to them with 3 different wireless devices. I also tried multiple configurations with both units including running through all the channels. No matter what I did non of the 3 wireless devices could find the SSID. But as soon as I hooked up my original DGL-4500 they picked up the SSID no problem.
Where the DGL-4500 is EOL the CS II manager agreed to switch it for another model. Van (the CS II manager) has really been doing all he can to make this right. But it still don't change the fact that I will most likely never purchase anther D-Link product again.
-
And thats your choice. Were here to help each other and help people with there problems and to gain a better experience for those who ask for help. Most people here get a the help they need and continue to enjoy there routers. Of course, some can't be helped.
Good luck in your endeavors.
-
Maybe it is just me but if your unit works in straight .11g but not in .11n then that says to me it is the unit. If you have to turn off QoS to get your router to work then you are not getting the use of features you paid for.
The feature I paid for was the IPv6 stack, the best available in the consumer market for those whose ISPs don't provide IPv6 connectivity themselves. The overwhelming majority of my network use is wired, so while I do need WiFi, high-speed wireless is merely a convenience.
I'm in the midst of some long-term troubleshooting, collecting captures of all wireless traffic to try to determine under what circumstances the router ceases responding to other devices. It may take a day, it may take a week, but in any case, it may provide useful data.
Incidentally, Furry, there are a total of eight other local WiFi networks within the same frequency band. That's not enough to provide congestion issues. The router works fine with them on .11g, not on .11n, even locked to 20MHz bandwidth. It's not interference.
-
I understand that having only 8 other WiFi routers around YOU, doesn't consitute congestion, however I could be for others. Distance can play a factor as well. Many factors play a role in how these WiFi routers work. I just offer up some ideas and suggestions to what might be happening and these are only to try to help trouble shoot the problem. If the troubleshooting process has been exhausted then I do recommend contacting D-Link for support and RMA options.
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.
-
Also curious about .Toast's problem, any status on this? ???
-
No change here still suffering from dropping issues havent had time to contact dlink about RMA since ive been working alot gonna do that when i get a chance cause lets face it a router should be able to handle more then 3 devices without issues
-
I agree. It's possible this router is faulty. I would contact D-Link and check on RMA options. Please keep us posted.
-
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.
-
Please do Martin keep us updated now its starting to get interesting rather then the quick answers thats been given in this thread so far, with the almost same conditions as i have you should face the same problems ive been dealing with, so whatever you find, post :)
-
Maybe someone can review your router settings with you using teamviewer. (http://www.teamviewer.com)
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.
-
No one is viewing my settings via Teamviewer. I'm not trying to be difficult, but you need to acknowledge that whatever is going on here is not just a simple setting issue. I dissect network traffic as part of my job, and that includes doing detailed analyses of WLAN traffic down to the wireless frame. I've got seven years in network security, double that in IT in general, and I teach a class that involves protocol analysis and understanding complex environments. I do protocol analysis from Layers 2 through 7 on a routine basis and have probably dealt with trickier situations than almost anyone here, so instead of offering to help me, let me try to help.
Now, with that out of the way...
It took 23.2GB of traffic captures to knowingly capture an issue, but I have. I don't know exactly what the cause is yet, but I'm seeing some very odd things that include:
- Silence on the part of the router followed by a flood of probe responses for probe requests that I can't find
- Authentication requests that were acknowledged by the router's radio hardware; I can identify it by the signal strength of -26dBm, consistent with the strength of the beacon frames from the router sitting about eight inches from the wireless NIC in monitor mode. But the router's software doesn't respond to them, at least not in any meaningful timeframe. (Wireless operates in the microsecond range, so not seeing responses at least in the next few seconds is bad.)
- Return to normal operations after a minute or so, which itself is unusual as the router usually needs to be rebooted to get normal ops back.
This looks to me like something in the router's software such as a driver or a service is either hanging or crashing. It may in some cases recover and in other cases not, which also means that those of us affected by this may be having problems that we don't recognize because we don't see it or because it resolves itself before we can declare it a router issue.
I went looking for logs since I now had an exact time of the problem. Unfortunately, since I rebooted the router, logs prior to reboot were no longer available. But there is a debug option in the log configuration (Stats | Logs | Log Options) which was unchecked. I checked that and rebooted and am now seeing some information (use of udhcpd, PID files stored in /var/run, etc.) suggesting that Linux is the underlying OS which puts me on even more familiar ground. I just wish there was a shell to which I could gain access. Well, that's what nmap is for...
-
We are here to help each other out. I and others are here on our own accord and motivated to offer help to those willing to take the time and allow us to try and help them. We do all we can to help everyone out. However, we do understand that we can lead you and not make you do anything. That said, you seem to be supposedly experienced enough to trouble shoot these issues that your seeing and should be able to figure out the problem. If you say that you do this kind of "analysis" then you would realize that there are other factors that effect how these home routers work. So some settings on these routers can call effect how they work. I have 2 of these model routers and tested them both. You do understand that these are low end class routers don't you. These are not higher end business class routers. These are ment for general purpose and home user use.
Not trying to be difficult either, however these forums are for people who are looking for help in solving there issues and willing to let others help them. What we are here for.
Yes there maybe FW or HW issues, however some of those can not be addressed here. They need to be addressed directly with D-Link themselves. You need to contact your local DLink support office and have them help you with your router and tell them of your concerns. DLink is aware of what goes on with there products.
Gook luck.
-
If I take them up solely with DLink and never post here, those who come here for help may not get any solutions or learn the possible problems.
I am aware that it's a home router and not the same as the $25,000 controllers I use at work. That doesn't excuse random functionality drops, and I'm loathe to simply RMA something without having an idea of the actual issue. Your testing of the two devices may not have shown anything, but you also might not have run enough traffic through them. I had to run mine for five days of reasonably high traffic to trigger a problem.
I'm continuing my analysis and will post in the next few days and also contact DLink about it, and will update with that information as well.
.Toast, if you enable debug-level logging and run into the problem, could you perhaps post the log or maybe send it to me via PM if you're not sure about public posting?
-
I do understand that posting information here is appreciated however and does benefit all, however keep in mind the level of information and level of some users here. Most of the information and help here is related to immediate problem solving if possible. Then it becomes historical knowledge from then on.
Regarding immediate problem solving, sometimes it does help out to let others help you out with router settings. Like a 2nd opinion. We've helped many out to resolve problems.
Again, not wishing to be "difficult" in any regards here. Like I said before, we're here to help each other out as much as possible and we do appreciate any good and quality information posted. We also appreciate it when users accept help and allow us to help them out. :D
Regards.
-
Martin, sure ill provide a log in pm after this weekend gonna pressure it so it gives an accurate picture of of the traffic when dropping issues occur so ill get back too you after the weekend :)
-
Well I got my DIR-657 loaner unit to replace the 3 deffective DGL-4500 they sent me. It has been running fine for about 5 days. Then today it started dropping just like what has been explained over and over again here. Sounds to me like there is a flaw in the router and D-Link is refusing to address it and just keeps shipping bad units out.
I am just hoping that the DIR-857 does not have the same issues when it finally hits the market. I wonder if this has something to do with it's release being continually pushed back.
Martin thank you for all you are doing. I just hope that when you find the cause D-Link stands up and recalls these bad routers and fixes the issue.
Jeff C
-
Having 3 4500s and now a 657 seemingly doing the same thing, might also indicate you have a external environmental condition effecting your area and these routers.
What wireless modes are you using now on the 657?
Try single mode G or mixed G and N exhibit these issues?
-
Martin thank you for all you are doing. I just hope that when you find the cause D-Link stands up and recalls these bad routers and fixes the issue.
I'm not convinced that the routers themselves are bad. Looking at my logs, I see some things that make me think the software is far more likely to be an issue. Examples with mundane parts removed:
Feb 9 13:13:06 notice [truncated] m
Feb 9 13:12:58 notice [truncated] m
...
Feb 9 10:37:00 notice [ 1011.430909] CALL && CALLI on stack:
Feb 9 10:37:00 notice [ 1011.430784] Kernel Stack:
Feb 9 10:37:00 notice [ 1011.430754] Starting backtrace: PID 0 'swapper'
...
Feb 9 09:17:07 debug [ 616.302568] jcpcore: Unknown condition 0x6a81
Feb 9 09:17:02 debug [ 611.302326] jcpcore: Unknown condition 0x1e00
Feb 9 09:16:57 debug [ 606.302198] jcpcore: Unknown condition 0x00
Feb 9 09:16:52 debug [ 601.301946] jcpcore: Unknown condition 0x00
Feb 9 09:16:47 debug [ 596.302115] jcpcore: command not found
Feb 9 09:16:42 debug [ 591.301704] jcpcore: Unknown condition 0x303a
Feb 9 09:16:37 debug [ 586.301664] jcpcore: Unknown condition 0x3082
Feb 9 09:16:32 debug [ 581.301565] jcpcore: Unknown condition 0xe300
Feb 9 09:16:27 debug [ 576.303422] jcpcore: Unknown condition 0x200
Feb 9 09:16:20 debug [ 568.801761] jcpcore: Unknown condition 0x4f50
Feb 9 09:16:15 debug [ 563.798469] jcpcore: Unknown condition 0x6865
Feb 9 09:16:10 debug [ 558.795568] jcpcore: Unknown condition 0x80f0
Feb 9 09:16:05 debug [ 553.792750] jcpcore: Unknown condition 0x00
Feb 9 09:16:00 debug [ 548.782593] jcpcore: Unknown condition 0x06
Feb 9 09:15:55 debug [ 543.772312] jcpcore: Unknown condition 0x72fe
...
Feb 8 19:13:12 debug [ 558.677998] jcpcore: Unknown condition 0x00
Feb 8 19:13:12 debug [ 558.576833] jcpcore: Unknown condition 0x00
AFAICT, jcpcore may be a Java process that's running into conditions that it doesn't understand. I have no idea what the truncations at the top are, but the backtrace is another story. I'd love to know why swapper is crashing and, even better, get the backtrace itself.
-
What current FW version was this tested on?
Happening on both versions?
What this over a wireless or wired conenction?
If wireless, what modes was the router set for?
-
Having 3 4500s and now a 657 seemingly doing the same thing, might also indicate you have a external environmental condition effecting your area and these routers.
What wireless modes are you using now on the 657?
Try single mode G or mixed G and N exhibit these issues?
Apparently you did not read any of my post. Are you so much a D-Link fanboy that you can not accept that they have faulty products? Or perhaps you simply get paid in one way or another to keep signing their praises here and blaming the end users for all the companies problems.
Just to correct things for everyone else I was not having any problem with the DGL-4500s dropping WiFi. The original 4500 would randomly reboot for no reason. The 2 4500s they sent me as replacements would not broadcast the SSID. They never had the chance to drop because the SSID was NEVER broadcast in the first place.
Wireless Radio : Enabled
802.11 Mode : 11n
Channel Width : 20/40 MHz
Channel : 11
WISH : Inactive
Wi-Fi Protected Setup : Enabled/Configured
I see no reason why I should switch to single mode G or mixed G and N in order to use my router. I paid for an 802.11n router. Had I wanted the lower grade 802.11g router I could have saved myself a considerable amount of money.
However, to test the issue I will try 802.11gn and report back.
I am also only getting 130MBs and not 300MBs. I have followed the guidelines in the stick and with the exception of having D-Link adapters all my setting are correct. And yes my adapters are 20/40 MHz compatible.
-
I'm not convinced that the routers themselves are bad. Looking at my logs, I see some things that make me think the software is far more likely to be an issue. Examples with mundane parts removed:
Feb 9 13:13:06 notice [truncated] m
Feb 9 13:12:58 notice [truncated] m
...
Feb 9 10:37:00 notice [ 1011.430909] CALL && CALLI on stack:
Feb 9 10:37:00 notice [ 1011.430784] Kernel Stack:
Feb 9 10:37:00 notice [ 1011.430754] Starting backtrace: PID 0 'swapper'
...
Feb 9 09:17:07 debug [ 616.302568] jcpcore: Unknown condition 0x6a81
Feb 9 09:17:02 debug [ 611.302326] jcpcore: Unknown condition 0x1e00
Feb 9 09:16:57 debug [ 606.302198] jcpcore: Unknown condition 0x00
Feb 9 09:16:52 debug [ 601.301946] jcpcore: Unknown condition 0x00
Feb 9 09:16:47 debug [ 596.302115] jcpcore: command not found
Feb 9 09:16:42 debug [ 591.301704] jcpcore: Unknown condition 0x303a
Feb 9 09:16:37 debug [ 586.301664] jcpcore: Unknown condition 0x3082
Feb 9 09:16:32 debug [ 581.301565] jcpcore: Unknown condition 0xe300
Feb 9 09:16:27 debug [ 576.303422] jcpcore: Unknown condition 0x200
Feb 9 09:16:20 debug [ 568.801761] jcpcore: Unknown condition 0x4f50
Feb 9 09:16:15 debug [ 563.798469] jcpcore: Unknown condition 0x6865
Feb 9 09:16:10 debug [ 558.795568] jcpcore: Unknown condition 0x80f0
Feb 9 09:16:05 debug [ 553.792750] jcpcore: Unknown condition 0x00
Feb 9 09:16:00 debug [ 548.782593] jcpcore: Unknown condition 0x06
Feb 9 09:15:55 debug [ 543.772312] jcpcore: Unknown condition 0x72fe
...
Feb 8 19:13:12 debug [ 558.677998] jcpcore: Unknown condition 0x00
Feb 8 19:13:12 debug [ 558.576833] jcpcore: Unknown condition 0x00
AFAICT, jcpcore may be a Java process that's running into conditions that it doesn't understand. I have no idea what the truncations at the top are, but the backtrace is another story. I'd love to know why swapper is crashing and, even better, get the backtrace itself.
That is very interesting. It would be nice if it is the software as it makes for an easier fix. Also means no need to exchange the actual routers themselves. But it does mean that D-Link still has to admit there is a problem and then FIX it.
Jeff
-
Hmmm, interesting reading. What I did not pull out of this was, is it one particular device that is causing the problem, like an Android phone?
802.11N was in draft for so long, there are all kinds of crazy configurations out there, hardware and software based. For the longest time I had problems when I tried to log in with an Android phone to my WiFi, it would always take the router out, the final solution, lock the IP in the router and physically enter it into the phone(Handshake/DHCP problem?), I have never had a problem since with NO OTHER DEVICE. Quite honestly I don't think 802.11N has been around long enough for all the draft stuff to catch up. I think I did see someone actually turn off the Short GI, good call, most older radios do not have that fast of an AGC circuit to compensate, unless it is a newer design.
Seems we have a lot of knowledge out here, myself, Masters degree in electrical engineering emphasizing on RF communications with 35+ years experience.
The 2.4Ghz Industrial, Scientific and Medical(ISM) band is crazy noisy to start off with. Honestly, to have someone put out 1500 watts in this band is NOT unheard of(Microwave oven anyone?), YOU just can't do it with a WiFi network because YOU are considered to be a secondary user of this band, secondly, you have to be licensed to radiate more then 4 watts ERP on this band, but never forget, you are a secondary user and therefore must put up with the INTERFERENCE on the 2.4Ghz ISM band.
Seeing we have so many experienced people out here, have we tried to scientifically eliminate what 802.11N device is causing the problem(s) like I did at home? A lot of HARDWARE(ASIC in nature) is coming out these days that is not 100% compliant with the 802.11N spec (they call themselves DRAFT). One vendor mentioned above, Atheros, has so many revisions on it's ASIC's, it makes you wonder WHY, if the simple fix was just firmware, why did Atheros actually revise the hardware? Lets not forget the Ralink RT2770/RT2750, it is so deaf they are paying people to take them on Flea Bay. Is it D-Links fault that a certain chipset is buggy or has no tolerance for error? I see Cisco gear all the time that has had 100's of revisions, why? It would be great if we could use FPGA's and CPLD's to design with and simply fix every problem with a simple firmware revision, but with ASIC's this is impossible! ALL manufacturers have hardware design problems, especially with the wave of new smart phones and laptops coming out, there is no way to 100% test for every condition a piece of hardware/software will encounter in it's life, at the rate new phones and laptops are being released. Are people out here really under the impression that every revision of a chipset was a die shrink/upgrade?
As Furry said, this forum exists for US/WE to try and help each other. I have a brand new Android phone waiting at home as I type that has a 5Ghz radio in it, why? To get away from the over crowding on the 2.4Ghz ISM band. My routers at home put out quite a bit more then the standard 15-20Mw, but I still have interference as indicated by a spectrum analyzer. Heck, just the recent M and X class solar flares we have had is enough to knock out comms from HF to Microwave, but we expect our home routers to be rad hardened or something, all for a 100 bucks or less.
I have had to take a LOT of Netgear and Cisco routers out because they won’t work with other stuff. So let me see, Dlink, Cisco/Linksys, Netgear….. Who is left? I was thrown off the Cisco forum for posting my findings on their JUNK and trying to find a solution. Just a couple of weeks back I had to take a Netgear router out of a friends home because it would not work with his NEW tablet, Netgear worked with everything else. I put D-Link in, now everything works fine again. Can you say DRAFT “N”?
One person posted above that they do lots of WiFi installs. So I assume you install something that works 100% of the time? Can we get the name of the manufacturer and P/N of the equipment? Because I sure could use something that is wireless and works 100% of the time with no 802.11N problems for 100 bucks, if they make it in dual band, can I get that P/N too?
Figure out what is causing the problem by adding 1 device at a time. But I know without a doubt, Xbox slims and Android phones/tablets are high on my suspicion list.
Lunch is over,
Later!
-
I am also only getting 130MBs and not 300MBs. I have followed the guidelines in the stick and with the exception of having D-Link adapters all my setting are correct. And yes my adapters are 20/40 MHz compatible.
Well, if you were as smart as you proclaim to be, you would understand that when you turn short GI off it slows the throughput down, also you profess to know 802.11N, then you are aware that to be compliant with 802.11N(non draft), when it detects another WiFi signal in range it MUST narrow it's signal down to 20Mhz thus cutting the throughput in half. Must have overlooked that part EH'?
-
Well, if you were as smart as you proclaim to be, you would understand that when you turn short GI off it slows the throughput down, also you profess to know 802.11N, then you are aware that to be compliant with 802.11N(non draft), when it detects another WiFi signal in range it MUST narrow it's signal down to 20Mhz thus cutting the throughput in half. Must have overlooked that part EH'?
So now the sprit of the forum is to bash those that do not agree with the D-Link gods?
First off I do NOT have short GI off. So there goes that thought.
Second I don't recall ever to have "profess to know 802.11N". Not sure where you got that from either.
What I do profess is that if I am purchasing a router that is advertised to be a 802.11n cappable of delivering speeds of 300MBs then I should get a router that delivers that!
Jeff
-
So now the sprit of the forum is to bash those that do not agree with the D-Link gods?
First off I do NOT have short GI off. So there goes that thought.
Second I don't recall ever to have "profess to know 802.11N". Not sure where you got that from either.
What I do profess is that if I am purchasing a router that is advertised to be a 802.11n cappable of delivering speeds of 300MBs then I should get a router that delivers that!
Jeff
Then maybe you should read the 802.11N spec, it is IMPOSSIBLE in a crowded network environment to get 300Mbps, regardless of who's 802.11N COMPLIANT gear you use. Also you spell capable with only 1 "P".
-
Then maybe you should read the 802.11N spec, it is IMPOSSIBLE in a crowded network environment to get 300Mbps, regardless of who's 802.11N COMPLIANT gear you use. Also you spell capable with only 1 "P".
I guess the D-Link employees here on the forum are getting heat for those of us complaining about the poor products D-Link is putting out. Need to resort to calling names and picking on spelling errors. Man you in 3rd grade or what?
If as you say it is "IMPOSSIBLE in a crowded network environment to get 300Mbps" then why even bother making this post sticky http://forums.dlink.com/index.php?topic=45154.0. Hmm maybe to boost the sale of D-Link adapters? Of course you are assuming with that statement I am in a "crowded network environment" which I have never stated I was.
Jeff
-
Then maybe you should read the 802.11N spec, it is IMPOSSIBLE in a crowded network environment to get 300Mbps, regardless of who's 802.11N COMPLIANT gear you use. Also you spell capable with only 1 "P".
You really shouldn't get pedantic on spelling when your capitalization isn't perfect. It's not possible to get a full 300Mbps (or any other connection speed you have), but it should be possible to hit somewhere in the range of 25% to 50% of connected speed for throughput absent serious other traffic.
Come on, guys. I know I got a little testy with Furry, but let's not let it degenerate further.
I've downloaded the source code and am extracting it (all 3.2GB of it) to sort through the versions and see if something has been reported in the various bug trackers. This is starting to stretch my knowledge, but it is kind of fun.
I've pinned down a few versions here and there (the nmap scan was helpful to some extent, the source code more helpful), but I still want to get some decent logs to further pin down some possibilities. My router has been stable for a couple of days, but I expect it to go sideways sometime this weekend.
-
You two are assuming that Furry and I work for D-Link and we are PAID tech support people?
As I stated above, I am an Electronics Engineer, Pro Bono! Furry is the same, this forum was unmanned before Furry came along and he walked me through a fix for my router. I have watched Furry help more people out of the kindness of his heart and sit here and take abuse and I wonder why? Then a couple of jerks like you come along.
Name calling? What is fan-boy and the other stuff you tossed at Furry?
"Lets NOT degenerate now that I have thrown a few stones". Ha! you are a class act, unbelievable!
My wireless network transfers at 300Mbps and my internet transfers at 100Mbps x 5Mbps, but yours is crawling along and crashing? TOO BAD! Maybe next time you will learn to keep your traps shut and take a little advice from a couple of people that are willing to help others.
As far as 300Mbps via wireless, Google "802.11n good neighbor policy" and figure it out like we did.
Oh, and as far as what I do for a living, think stuff that flies and US defense, think stuff that keeps your skin safe everyday.......
Here's a link for ya!
http://www.speedtest.net/result/1765778208.png (http://www.speedtest.net/result/1765778208.png)
Furry is the guy that very well could have helped you, at 50, I have no patience for know it all punks unless I am firing one!
-
You're confusing posts made by other people. I never claimed any links between you or Furry and DLink. I figured that since DLink engineers have titles that say so and you two do not that you are volunteers. Fans of DLink? Certainly for Furry, but I just met you, so I have no idea.
I'm sure Furry has helped a lot of people. Some very basis issues come up that people don't understand and a change of frequencies or other simple fix often addresses them. My issues with Furry's attempts assistance in this thread have been that they did not address the problems even when they'd already been tried. He has recommended the same things be tried when they've already failed or when they clearly have nothing to do with the situation.
I did try the various settings early on, and indeed left it on .11g instead of .11n for several weeks. But I want to find out why the higher speed isn't working. You're welcome to lend your assistance, but if you've decided that you don't like me, that's fine. Ignore me and I'll do the same for you. But lambasting us isn't going to get any issues solved.
-
@ Martin Blank,
OK, now that I have some personal time, lets see if we can work something out for you. I have to go to my real job tomorrow, so replies will be sporadic, but unless a war with Iran breaks out, I should have time daily to try and help you as Furry has asked me to. As I stated above, my specialty is RF with a minor in digital. I have used just about every major brand of networking gear out there. My kids have been pushing the limits of home networking for at least a decade. I have drawn the line though, if it requires SFP modules or even takes them, it is a little rich for personal gaming and media (and my wallet).
A few years back I purchased a new product that was not mature and it had some bugs that later got worked out through firmware updates, I have no doubt that your firmware still may have some bugs in it, it was just released 7-8 months ago. I have the Dir-825 which was purchased for it's IPV6 support, which is still stellar to this day, my router at the time was said to reset itself daily. My personal best on it was 6 months and it had to be reset because of internet provider issues. I do not use the RF portion of my Dir-825 any longer, it is not powerful enough to cover the area which I need to cover, but in the beginning I did use the RF section. I have to run 2 A/P's at home, we have too many things connected to WiFi and when the throughput of the WiFi gets saturated, games and media start lagging, so if you have 10 high bandwidth/packet rate clients connected to 1 A/P, that can be a problem and cause stuff to crash. Or gaming parties as my kids do. Want a nightmare? 5 Xbox's and a house full of teenagers on Saturday night, pray your provider does not go down!
I am major leaning towards firmware issues with your series of router just because I had similar problems that the owners of the Dir-657 are having, but I have no doubt that D-Link is working on them and they do read this forum, how often, I have no clue. My personal opinion is that RF should have never been added to these routers, if the internal shielding is not 110%, your going to have problems. My 3 kids have beat the heck out of my home network, and mine could be considered an "extreme" case for most home networks.
My understanding with your case, the WiFi works fine until you enable "N" mode? Sorry to be redundant, but reading through the 5 pages there was a lot of "me too's" from several people.
What WiFi clients are you running/what are you connecting to WiFi with on the other end, what mode of WiFi do they support (B/G/N)?
Lastly, are you interested in a workaround until D-Link fixes any problems we find? The workaround should NOT include turning "N" mode off, because of the Good neighbor policy required by the FCC, I would prefer that we try with 20Mhz channels only though(at first). This will usually get you 65-150Mbps depending on the WiFi client and the distance between the 2. My router will do every bit of 300Mbps with short GI turned on(270 without), but a lot of stuff chokes with short GI because of the quality of the clients radios can't handle a TX-RX transition that fast.
I am more interested in your clients then interference and router settings, though I may just need to verify some router settings initially. Simple stuff like, if you have no "B" clients, set the router to G/N only.
-
Hello all, I'm not really too good when dealing with routers at all so I'm sure that when I read through this thread I didn't understand some of it.
Anyways, I'm running the DIR-657 right now and it's been having its dropping problems. I bought it a couple months back, maybe in October or so, and it was working fine until a relative screwed up the router somehow by setting it up the router up in a faulty way. My problems may or may not have come as a result of said naive actions by my relative but drops in my connections have started occurring since around that time period. I use a Wii or a Xbox 360 most of the time as well as a laptop running at the same time. Not sure how I should adjust the settings so I kinda need help.
Here are just some of the settings, I'm sure I'll probably need to give more but this is all I really know what to give so far. Sorry for being so bad around routers, haha.
http://i44.tinypic.com/w1bjmv.png
EDIT: Yes, I have reset the router back to factory default settings. I've even tried switching back to my older WBR-2310 router and I just still have the same problems.
I should also note that most of my problems are coming from the wii, although drops do occur with the 360. I can stay online the Wii but whenever I try joining some online room I disconnect in 5 from the room in 5 minutes and my internet drops for a second or two.
-
ErikN: Make sure you're on the latest firmware. It's 1.01, and so far available only from the website. Checking current firmware from within the router doesn't show the update,
I have to run 2 A/P's at home, we have too many things connected to WiFi and when the throughput of the WiFi gets saturated, games and media start lagging, so if you have 10 high bandwidth/packet rate clients connected to 1 A/P, that can be a problem and cause stuff to crash.
I have, at the most, five devices connected:
- Two Samsung Galaxy S II phones
- One HP TouchPad
- One Roku XD
- One Asus notebook with Intel 6150 WiFi card
- One Dell notebook with Intel 4650 WiFi card
On very rare occasions, a Palm Pre is also attached, but that's by far the exception these days and has not been the norm for about three months. The highest throughput devices are the Roku when streaming (though recently it has been fairly quiet) and the notebook when playing video or various MMORPGs. My experience with Intel cards has been top-notch. I've successfully recommended that notebooks at work be purchased with Intel cards instead of the default Broadcom cards that have produced all manner of problems.
My understanding with your case, the WiFi works fine until you enable "N" mode?
Everything works fine under .11g, and things eventually break under .11n. My suspicion at this point is either a service or a driver. My reasoning for the former is the odd reply cycle in at least one situation that suggests a buildup of data followed by a rapid release of responses. My reasoning for the second is the proper functioning of the wireless network under one standard and not the other, even within the same frequency band.
Lastly, are you interested in a workaround until D-Link fixes any problems we find? The workaround should NOT include turning "N" mode off, because of the Good neighbor policy required by the FCC, I would prefer that we try with 20Mhz channels only though(at first).
I've tried that, but I've just reset it to that just because that's the major compatibility variable that makes some level of sense. MMS works over .11g, as does every other shared setting. The major difference between them is that .11n uses a different coding for OFDM and it allows for 40MHz bandwidth. Given the prevalence of .11g APs around here, though, it has zero chance to use it. It froze up again this evening, but nothing useful appeared in the logs before I finally rebooted it, though I waited for a few hours for something to crash and be visible. There were no frames whatsoever leaving the router. Thousands of frames came in, and not one frame left.
I see Atheros hardware involved (port ID ath0), so it may be Atheros's constantly evolving drivers. They make some good hardware, but their drivers always seem to need some work. Maybe we'll see some of that (with the recent security fixes) in 1.02.
-
Lambasting, belittling and getting in our panties all in bind isn't helping either. It was Martin and Jeff who came to the thread and refused any help from me. Martin and I discussed the issues at hand and I hoped that we could conclude to continue to post good information about this issue with out getting into any heated discussions or name calling and belittling anyone.
This is not a contest either between us. I could care less who is an engineer or who has had the longest experience in there particular career or what title people carry. This is forum, again, as I said before, its for trying to help with immediate problems. Any other problems that can't be resolved by us here in the forums get recommended to DLink support directly after that.
Yes, if any good professional useful information provided is also great for users and DLink, and will help improve there products for current and future use. Many users and myself are very grateful for all the extra information that use contribute to the forums. I have made DLink aware of these issues manytimes. However, they carry the pink slip and its' there company. They run it how they desire. If there desires don't match ours then we as consumers who don't find satisfaction have means to let them know directly.We also have means to find other solutions to the dis-satisfaction by finding other solutions. Ranting, flaming and being unprofessional here in the forums is a waste of your time and everyones time. It gets NOTHING accomplished.
This thread has become a bit off topic and distracted away from the OP. I don't even know of the OP has resolved his issue yet, moved on or found something else.
I highly recommend and I would like those of you who want to delve more into this with more detail and troubleshoot this down as far as you can, lets start a new thread. ::) Call it what you want. I recommend that you remove the most resent posts, copy and paste and move them to the new thread and lets continue to try and be civil please. If not then people need to move on. Theres more to life out there than all this.
@EirikN Please start a new thread and Martin, I, and any others wanting to help you will follow you there and continue to help you out.
Have a great week.
You're confusing posts made by other people. I never claimed any links between you or Furry and DLink. I figured that since DLink engineers have titles that say so and you two do not that you are volunteers. Fans of DLink? Certainly for Furry, but I just met you, so I have no idea.
I'm sure Furry has helped a lot of people. Some very basis issues come up that people don't understand and a change of frequencies or other simple fix often addresses them. My issues with Furry's attempts assistance in this thread have been that they did not address the problems even when they'd already been tried. He has recommended the same things be tried when they've already failed or when they clearly have nothing to do with the situation.
I did try the various settings early on, and indeed left it on .11g instead of .11n for several weeks. But I want to find out why the higher speed isn't working. You're welcome to lend your assistance, but if you've decided that you don't like me, that's fine. Ignore me and I'll do the same for you. But lambasting us isn't going to get any issues solved.
-
There is a beta build available if anyone is interested:
http://forums.dlink.com/index.php?topic=53645.0 (http://forums.dlink.com/index.php?topic=53645.0)