• February 22, 2025, 06:42:50 PM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Pages: 1 ... 3 4 [5] 6

Author Topic: Wireless dropping Issues  (Read 62465 times)

swetoast

  • Guest
Re: Wireless dropping Issues
« Reply #60 on: February 09, 2012, 07:42:41 AM »

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 :)
Logged

JeffC71

  • Level 1 Member
  • *
  • Posts: 9
Re: Wireless dropping Issues
« Reply #61 on: February 09, 2012, 04:30:34 PM »

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
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49923
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: Wireless dropping Issues
« Reply #62 on: February 09, 2012, 05:40:18 PM »

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?
Logged
Cable: 1Gb/50Mb>NetGear CM1200>DIR-882>HP 24pt Gb Switch. COVR-1202/2202/3902,DIR-2660/80,3xDGL-4500s,DIR-LX1870,857,835,827,815,890L,880L,868L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L,960L and 8000LH.

Martin Blank

  • Level 1 Member
  • *
  • Posts: 12
Re: Wireless dropping Issues
« Reply #63 on: February 09, 2012, 08:24:35 PM »

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:

Code: [Select]
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.
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49923
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: Wireless dropping Issues
« Reply #64 on: February 10, 2012, 07:05:12 AM »

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?
« Last Edit: February 10, 2012, 07:38:49 AM by FurryNutz »
Logged
Cable: 1Gb/50Mb>NetGear CM1200>DIR-882>HP 24pt Gb Switch. COVR-1202/2202/3902,DIR-2660/80,3xDGL-4500s,DIR-LX1870,857,835,827,815,890L,880L,868L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L,960L and 8000LH.

JeffC71

  • Level 1 Member
  • *
  • Posts: 9
Re: Wireless dropping Issues
« Reply #65 on: February 10, 2012, 02:35:19 PM »

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.
Logged

JeffC71

  • Level 1 Member
  • *
  • Posts: 9
Re: Wireless dropping Issues
« Reply #66 on: February 10, 2012, 02:40:25 PM »

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:

Code: [Select]
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
Logged

Patrick533

  • Level 3 Member
  • ***
  • Posts: 271
Re: Wireless dropping Issues
« Reply #67 on: February 10, 2012, 02:59:57 PM »

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!



    


 

      
Logged

Patrick533

  • Level 3 Member
  • ***
  • Posts: 271
Re: Wireless dropping Issues
« Reply #68 on: February 10, 2012, 03:16:00 PM »

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'? 
Logged

JeffC71

  • Level 1 Member
  • *
  • Posts: 9
Re: Wireless dropping Issues
« Reply #69 on: February 10, 2012, 03:27:36 PM »

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
Logged

Patrick533

  • Level 3 Member
  • ***
  • Posts: 271
Re: Wireless dropping Issues
« Reply #70 on: February 10, 2012, 03:33:48 PM »

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".
Logged

JeffC71

  • Level 1 Member
  • *
  • Posts: 9
Re: Wireless dropping Issues
« Reply #71 on: February 10, 2012, 03:39:57 PM »

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
Logged

Martin Blank

  • Level 1 Member
  • *
  • Posts: 12
Re: Wireless dropping Issues
« Reply #72 on: February 10, 2012, 08:23:00 PM »

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.
Logged

Patrick533

  • Level 3 Member
  • ***
  • Posts: 271
Re: Wireless dropping Issues
« Reply #73 on: February 10, 2012, 10:42:24 PM »

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

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!





Logged

Martin Blank

  • Level 1 Member
  • *
  • Posts: 12
Re: Wireless dropping Issues
« Reply #74 on: February 11, 2012, 09:24:44 AM »

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.
Logged
Pages: 1 ... 3 4 [5] 6