Print

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

[samssf]

Hello all,

I recently purchased the DIR-655, and have had quite a few problems. My setup is a Motorola modem w/ AT&T broadband --> D-Link with firmware 1.32NA ---> Wired win 7. Other devices:  wireless macbook pro, wired PS3.

When I first set it up, I was having problems pinging computers on my network by name, and I assumed there was a problem with DNS lookup etc. I upgraded to the most recent firmware and I'm not sure if that helped, but I can ping machines on my network by name, now.

However, within a couple minutes of resetting my modem, any webpages that have references to a lot of other content... ie, msn.com, which has lots of ads and content which causes the internet browser to fetch images from other servers... these sites take minutes to load. Simple sites that only consist of one http request, such as google.com, load in a fair amount of time (a few seconds). But overall sites take about 50 times longer to download than they normally would. But I don't think its the actual connection *speed*, it has to do with the initial session creation when my browser connects out to servers on the web to grab content.

Obviously something is very wrong... Resetting the router seems to resolve this for a few minutes. And for some reason it seems that every once in awhile the problem will just resolve itself for a short while.

Other devices on my network have the same problem (laptop, PS3, etc). When they try to connect to something, it takes forever.

If I ping my modem, which is directly behind the DLink, I can ping it with a few quick response time and no dropped packets. However, if I try to bring up the modem's web manager, it will take forever to load. This isn't the modem's fault... I just add this information because it seems like this whole problem has to do with the router's DNS lookup or packet routing or something... I'm not a network specialist so I don't really know.

When I look at the D-Link's logs, I don't notice anything too suspicious (like session timeouts etc) but can provide that if requested. I'm hoping someone will recognize these symptoms right away and have a solution (or at least the same problem) and maybe I can just trash the POS and buy a cheap wrt54g off ebay since I'm unemployed.

Thanks for any help...

-------------------------------
Solution:

My modem connects to my ISP over PPPoE. PPPoE has a max MTU of 1492. Set MTU on router to 1492 and have not experienced lag since... going on five hours.

The symptoms were likely caused by dropped outgoing packets when my browser would try to request images and other content from web pages. So pages would only download partway, stall, load a little more, stall, etc.

http://www.dslreports.com/faq/695

[samssf]

*Update*

So I updated with the beta firmware from November. The D-Link router management page still says hardware A4 and firmware 1.32NA, but the date now shows November 5, 2009.

The problem still occurs. And it's actually not isolated to initial connections... I tried downloading a large file. It would download at around 240Kbps, and then every 30 seconds or so it would stop downloading and freeze for about two minutes, and then it would continue downloading.

Please help =(

[Krusher]

How long have you had your router?  I had similar web page access and admin page problems as you described with the official 1.32NA, but my problems took 1-3 weeks to "build up" to the point where I had to unplug it.

Since the Beta09 did not fix it for you, if your router is new, maybe you just have a bad router?

[samssf]

Well, I didn't notice the problems with connectivity until I flashed it with the 132NA firmware. And I got it a couple months ago but was on a trip for a month, so it's probably too late to return it.

[samssf]

I see that my log file now has these entries:

Blocked outgoing TCP packet from 192.168.0.199:59308 to 65.197.197.43:80 as FIN:ACK received but there is no active connection
[INFO]   Sat Jan 31 12:38:16 2004   Blocked incoming TCP packet from 65.55.236.162:443 to 192.168.1.64:52424 as RST:ACK received but there is no active connection
[INFO]   Sat Jan 31 12:35:18 2004   Above message repeated 58 times
[INFO]   Sat Jan 31 12:10:01 2004   Blocked outgoing TCP packet from 192.168.0.191:59315 to 65.200.11.154:80 as RST:ACK received but there is no active connection
[INFO]   Sat Jan 31 12:09:53 2004   Blocked outgoing TCP packet from 192.168.0.191:59330 to 198.107.130.104:5223 as RST:ACK received but there is no active connection
[INFO]   Sat Jan 31 12:08:57 2004   Blocked outgoing TCP packet from 192.168.0.191:59315 to 65.200.11.154:80 as FIN:ACK received but there is no active connection
[INFO]   Sat Jan 31 12:08:49 2004   Blocked outgoing TCP packet from 192.168.0.191:59330 to 198.107.130.104:5223 as FIN:PSH:ACK received but there is no active connection
[INFO]   Sat Jan 31 12:07:53 2004   Blocked outgoing TCP packet from 192.168.0.191:59315 to 65.200.11.154:80 as FIN:ACK received but there is no active connection
[INFO]   Sat Jan 31 12:07:45 2004   Blocked outgoing TCP packet from 192.168.0.191:59330 to 198.107.130.104:5223 as FIN:PSH:ACK received but there is no active connection
[INFO]   Sat Jan 31 12:07:09 2004   Blocked outgoing TCP packet from 192.168.0.191:59347 to 65.200.11.154:80 as RST:ACK received but there is no active connection
[INFO]   Sat Jan 31 12:06:49 2004   Blocked outgoing TCP packet from 192.168.0.191:59315 to 65.200.11.154:80 as FIN:ACK received but there is no active connection
[INFO]   Sat Jan 31 12:06:41 2004   Blocked outgoing TCP packet from 192.168.0.191:59330 to 198.107.130.104:5223 as FIN:PSH:ACK received but there is no active connection
[INFO]   Sat Jan 31 12:06:05 2004   Blocked outgoing TCP packet from 192.168.0.191:59347 to 65.200.11.154:80 as FIN:ACK received but there is no active connection
[INFO]   Sat Jan 31 12:05:45 2004   Blocked outgoing TCP packet from 192.168.0.191:59315 to 65.200.11.154:80 as FIN:ACK received but there is no active connection
[INFO]   Sat Jan 31 12:05:37 2004   Blocked outgoing TCP packet from 192.168.0.191:59330 to 198.107.130.104:5223 as FIN:PSH:ACK received but there is no active connection
[INFO]   Sat Jan 31 12:05:01 2004   Blocked outgoing TCP packet from 192.168.0.191:59347 to 65.200.11.154:80 as FIN:ACK received but there is no active connection
[INFO]   Sat Jan 31 12:04:44 2004   Blocked outgoing TCP packet from 192.168.0.198:58204 to 72.14.203.95:80 as FIN:ACK received but there is no active connection
[INFO]   Sat Jan 31 12:04:41 2004   Blocked outgoing TCP packet from 192.168.0.191:59315 to 65.200.11.154:80 as FIN:ACK received but there is no active connection
[INFO]   Sat Jan 31 12:04:33 2004   Blocked outgoing TCP packet from 192.168.0.191:59330 to 198.107.130.104:5223 as FIN:PSH:ACK received but there is no active connection
[INFO]   Sat Jan 31 12:03:57 2004   Blocked outgoing TCP packet from 192.168.0.191:59347 to 65.200.11.154:80 as FIN:ACK received but there is no active connection
[INFO]   Sat Jan 31 12:03:37 2004   Blocked outgoing TCP packet from 192.168.0.191:59315 to 65.200.11.154:80 as FIN:ACK received but there is no active connection
[INFO]   Sat Jan 31 12:03:29 2004   Blocked outgoing TCP packet from 192.168.0.191:59330 to 198.107.130.104:5223 as FIN:PSH:ACK received but there is no active connection

These were all created while I was trying to play PS3 online but was experiencing lag and disconnects.

I didnt have any problem before I flashed with the 1.32NA firmware. Does anyone know of any settings etc I can change that might improve this? It would have to have something to do with whatever they changed in that firmware.

[ironic77]

I am having the same problems.

I bought the router a couple months back and immediately put 1.32NA release version on the router.  I had problems everywhere from several times a day to only once per week.  In general, it was pretty calm until recently.

I stumbled on the forums and tried the suggested November beta.  If anything, now the problem is even worse.

The router appears to basically disappear even though the lights are all shiny and blinking.  It's like a really expensive Christmas decoration though, because you can't reach the router at all.  Sometimes it comes back on its own after a minute or so, but even if it does, it will just disappear again in a minute or so.  Basically it's best to just reboot it and buy more time.

I have default configuration, although I just found a DIR-625 thread where a guy suggests some things that I decided to run without in the hopes that maybe the firmware bugginess is in those features.  Will see how it goes.

[samssf]

I think I have fixed the problem, but will report in again later.

My modem connects via PPPoE, and my so my max MTU is 1492. So I changed the MTU in my internet settings on the router. The only thing is that my router isn't communicating over PPPoE (I'm not doing passthrough / bridging on my modem) so I don't quite understand why changing the MTU on the router would help. But I don't know much about networking, so.

Anyway, I'm not seeing any lag at the moment, so hopefully that's the last of it. Good luck to others in finding solutions.

*Edit* after running this command a few more times (ping -f -l 1472 www.dslreports.com), I see that I can no longer cause a "packet needs to be fragmented" error. I'm guessing this is because of the max MTU change on the router... and so I'm pretty sure this was my fix. Thanks for all the help people.

Solution:  If your internet browser is load websites very slowly (lagging while loading, loading half the page and then stopping for a minute, etc) your MTU might be set incorrectly on the router.
http://www.dslreports.com/faq/695

Now what I'm wondering is why I didn't have to change the MTU with my original firmware...

[ironic77]

Oh yeah, MTU will definitely burn you.  I have cable though, so not an issue.  Most routers do detect MTU problems.

My issue is with connections on the LAN, not Internet, though obviously that is also failing.

[Krusher]

Ah, you must have read my post to Islander because you're referencing the same web page. 

Anyway, AT&T broadband uses PPPoE?  I thought only DSL did that.  Glad you figured it out; maybe that will help others too.  dslreports.com (broadbandreports.com) has a lot of good generic troubleshooting info I've found.

[samssf]

Ah, you must have read my post to Islander because you're referencing the same web page. 

Anyway, AT&T broadband uses PPPoE?  I thought only DSL did that.  Glad you figured it out; maybe that will help others too.  dslreports.com (broadbandreports.com) has a lot of good generic troubleshooting info I've found.

Yeah I'm sure it was your response, thanks =)

Yeah AT&T is actually DSL, not broadband. So pretty sure that did help, although I'm logging on again tonight because I'm still having problems. Same symptoms although less severe, probably a different cause. General poor performance and lagging when playing games. I attributed it to normal lag at first, but I'm pretty certain now it's because of the router. I had very minimal lag with my old router, and consistent lag always with the D-Link.

[Krusher]

I'm not sure what your whole configuration setup is, but if you have "Enable Traffic Shaping" checked, try turning it off.  I saw someone else suggested that in another posting some time ago.

Which doesn't make sense, traffic shaping is supposed to improve your ping time, not reduce it.  But I can see if you're using an application that the algorithm does not pick up on, it will give it a low priority.

If that doesn't do it, since you're using the beta anyway, did you maybe think about trying 1.33NAbeta01?  You can reverse this patch if it makes things worse.

[Cobra]

Yeah AT&T is actually DSL, not broadband.

Could have sworn back in the day of dial up modems that DSL and cable were considered broadband.