• March 29, 2024, 09:55:54 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 ... 18 19 [20] 21

Author Topic: Freezing router?  (Read 194180 times)

anonposter

  • Level 2 Member
  • **
  • Posts: 58
Re: Freezing router?
« Reply #285 on: June 25, 2009, 08:11:47 PM »

I'm curious... can router resources be blamed when most are shut off?  As stated much earlier in the thread, I suffer the same symptoms with practically everything turned off.

A snapshot of my router config...
DIR-655 A4
WPA2 enabled
Mac Filtering enabled
DNS Relay enabled
SPI enabled
everything else disabled including sharepoint, wish, wifi prot, securespot, etc.
« Last Edit: June 26, 2009, 09:11:08 AM by anonposter »
Logged

grking

  • Level 1 Member
  • *
  • Posts: 18
Re: Freezing router?
« Reply #286 on: June 25, 2009, 08:19:06 PM »

I can add a few more to your list: spi disabled and DNS disabled. The reboots are only occuring once per hour now. It was happening much more often but disabling everything seems to have helped.............for now...................
Logged

partach1

  • Level 2 Member
  • **
  • Posts: 52
Re: Freezing router?
« Reply #287 on: June 26, 2009, 10:05:10 AM »

Thanks for you response!

partach1, have you looked into this?
Yes did a lot of setting changes including DNS relay, no help


[INFO] Fri Dec 02 10:05:50 2005 DNS Relay ALG rejected UDP packet from 192.168.0.150:1381 to 67.21.13.6:53
This then happens every second in the log (after going bananas; first couple of days of router operation is n.p. and you do not see these messages) making the log full pretty fast...


Can you look at the eventvwr.msc (assumes XP) and take a look and see if you have any error messages regarding DNS registration failures? This is a weak area of knowledge for me, technically, but I do know that DNS queries typically occur a lot faster than one every 10-15 minutes or so. But 10-15 minutes sounds like the right interval for DNS Registration retries.
Have different clients: mostly Vista, Lunix, sometimes XP (not often) but all clients suffer from not having internet when the router goes bananas

Read this KB article:  »http://support.microsoft.com/default.aspx?scid=kb;en-us;305553&sd=tech
Still believe it is an issue inside the router. it has different instability sympthoms like not broadcasting a wifi network anymore. (also after a couple of days of operation). This new sympthom has poped up with 1.32NAb2. so i reboot the router now because of no wifi network and not because I see the DNS ALG info messages....


Hope that helps -- or at least gives us a lead ...[/color]
As stated i have done a lot of things with settings and all, it is somewhere in the firmware of the router (I am sure.) Other routers (sitecom N300, WRT54G all work brilliantly. but not fast enough  ;D)

Can send a log if that might help....
old one:
[INFO]   Fri Mar 27 14:54:50 2009   DNS relay ALG rejected packet from 192.168.1.197:61372 to 88.159.1.200:53
[INFO]   Fri Mar 27 14:54:50 2009   DNS relay ALG rejected packet from 192.168.1.197:53426 to 88.159.1.200:53
[INFO]   Fri Mar 27 14:54:49 2009   DNS relay ALG rejected packet from 192.168.1.197:61372 to 88.159.1.201:53
[INFO]   Fri Mar 27 14:54:49 2009   DNS relay ALG rejected packet from 192.168.1.197:53426 to 88.159.1.201:53
[INFO]   Fri Mar 27 14:54:49 2009   DNS relay ALG rejected packet from 192.168.1.195:62671 to 88.159.1.200:53
[INFO]   Fri Mar 27 14:54:48 2009   DNS relay ALG rejected packet from 192.168.1.197:61372 to 88.159.1.200:53
[INFO]   Fri Mar 27 14:54:48 2009   DNS relay ALG rejected packet from 192.168.1.197:53426 to 88.159.1.200:53
[INFO]   Fri Mar 27 14:54:47 2009   DNS relay ALG rejected packet from 192.168.1.195:62671 to 88.159.1.201:53
[INFO]   Fri Mar 27 14:54:45 2009   DNS relay ALG rejected packet from 192.168.1.195:62671 to 88.159.1.200:53
[INFO]   Fri Mar 27 14:54:44 2009   DNS relay ALG rejected packet from 192.168.1.195:62671 to 88.159.1.201:53
[INFO]   Fri Mar 27 14:54:43 2009   DNS relay ALG rejected packet from 192.168.1.197:59365 to 88.159.1.201:53
[INFO]   Fri Mar 27 14:54:43 2009   DNS relay ALG rejected packet from 192.168.1.195:62671 to 88.159.1.200:53
...
...
[INFO]   Fri Mar 27 14:52:25 2009   DNS relay ALG rejected packet from 192.168.1.195:52142 to 88.159.1.201:53
[INFO]   Fri Mar 27 14:52:24 2009   DNS relay ALG rejected packet from 192.168.1.195:52142 to 88.159.1.200:53
[INFO]   Fri Mar 27 14:43:56 2009   Administrator logout

see different clients!!

Btw just saw something interesting. I  tried to log in with Chrome but each time i type the correct password it brings me back to the same login screen (so i can log in until doomsday).

I used another browser (firefox) and that one was able to log in.
But have just switched over to Chrome so this does not mean it contributes to the problems I am having for four months...

« Last Edit: June 26, 2009, 10:14:03 AM by partach1 »
Logged

mackworth

  • Level 3 Member
  • ***
  • Posts: 204
Re: Freezing router?
« Reply #288 on: June 26, 2009, 10:55:01 AM »

I'm curious... can router resources be blamed when most are shut off?  As stated much earlier in the thread, I suffer the same symptoms with practically everything turned off.

A snapshot of my router config...
DIR-655 A4
WPA2 enabled
Mac Filtering enabled
DNS Relay enabled
SPI enabled
everything else disabled including sharepoint, wish, wifi prot, securespot, etc.

Turn of DNS relay and it will probably be fine.
Logged

mackworth

  • Level 3 Member
  • ***
  • Posts: 204
Re: Freezing router?
« Reply #289 on: June 26, 2009, 10:55:58 AM »

I can add a few more to your list: spi disabled and DNS disabled. The reboots are only occuring once per hour now. It was happening much more often but disabling everything seems to have helped.............for now...................

Are you getting reboots or freezes?  Turning of DNS relay shoudl take care of the freezes.  If you are getting reboots, that could be a different issue altogether.
Logged

Clancy

  • Level 3 Member
  • ***
  • Posts: 202
  • I am not a number. I am a free man!
Re: Freezing router?
« Reply #290 on: June 26, 2009, 11:20:49 AM »

What about flushing the DNS cache on each machine?
Logged
Thread derailment: So easy a caveman can do it.

grking

  • Level 1 Member
  • *
  • Posts: 18
Re: Freezing router?
« Reply #291 on: June 26, 2009, 11:33:53 AM »

Turning off the DNS relay as well as everything else listed by anon has made a very significant improvement in router stability. I have not lost my internet connection for 12 hours now. I haven't tested this with the XBOX Live yet which will be the 'true test'. My son hasn't played live for more than a few minutes before loosing his connection.  This memory exhaustion issue seems like it really could be the plauible explanation for my problem anyway.
Logged

partach1

  • Level 2 Member
  • **
  • Posts: 52
Re: Freezing router?
« Reply #292 on: June 26, 2009, 01:15:57 PM »

What about flushing the DNS cache on each machine?

Was this a hint for me?
I have a NAS linux based client on 24h, a set top box on a lot (linux), windows enabled smart phone, vista laptop, xp laptop.
In short the router has quit some clients to serve.
flushing the DNS cache on these machines will not help with the router problems

Regarding your link of setting a decent TCP-IP connection with DNS settings.... this i know of-course. The DNS settings are nomally passed on via DHCP (the router being the host).
All clients are DHCP configured. (i can expect the router to perform this function I hope)

I read from many that they switch of a lot features of the router in order to get it a bit more stable.
This kinda defeats the point of buying a sophisticated router?
It is spec-ed with these features so it better be able to do them properly?

Can someone from DLink be frank here by answering some questions:
- where is the software created? (somewhere in asia i´ll bet; this would explain the slow response to submitted issues and the ´quality´of the software and the fact that subsequent releases have the same problems or have regression)
- is the firmware in active development or is the business case of the 655 down the drain a long time ago and nobody really wants to maintain it any further?
- Does it have a hardware bug that is the center of the problems? (there could be a hardware fault that the software can´t circumvent)
- what do owners need to do to get a good tested new release with important items resolved (In other words: what would it take for DLink to give this some priority?)
- how many issues are open on this product and what is the priority listing? be open tell how it is. can we vote on the prios?

Probably nobody will even try to answer these question but if  somebody is brave enough it would give us (investors in a 655) a feeling of hope (depending on the answers though..)

I really would like this product if it was stable and does what it should do . But if there is no hope on a decent solution (in reasonable time; says the guy waiting for four months....) i must return it. (and urge others to do the same)
Logged

Jon8RFC

  • Level 1 Member
  • *
  • Posts: 12
Re: Freezing router?
« Reply #293 on: June 26, 2009, 01:35:44 PM »

Have you tried disabling "DNS relay" setting yet?
I have not--it's always been enabled.  My understanding is that DNS is intended for typing domains instead of typing an IP to access an external site.  I'll give it a whirl and see how things work.  I do have DNS caching disabled on one computer wired to the router, but the other computers (with caching enabled) have the same problem when the router performance declines.

When my router begins to perform poorly, the router configuration page becomes a hit or miss for trying to navigate and takes multiple tries to get through the pages.  If the router performance gets very poor, then I cannot even access main router configuration page, at all.  The router never stops functioning in an instant, it's a noticeable decrease in performance over a period of time.  The DNS Relay setting is independent from accessing the router configuration page via IP, unless I'm misunderstanding something about DNS...am I?  AND/or could the firmware have some funky problem with DNS where even the router cannot be accessed unless a physical reboot is performed?
Logged

Clancy

  • Level 3 Member
  • ***
  • Posts: 202
  • I am not a number. I am a free man!
Re: Freezing router?
« Reply #294 on: June 26, 2009, 02:10:21 PM »

Regarding your link of setting a decent TCP-IP connection with DNS settings.... this i know of-course.

Yeah, I always run the risk of being the guy that walks up to Mario Andretti, points at a IRL car and says, "Mario, that's a race car. Ever heard of the Indy 500?"

Quote
- where is the software created?

Demonized knows. I read it in an another post. I just can't remember which one.

Quote
- what do owners need to do to get a good tested new release with important items resolved (In other words: what would it take for DLink to give this some priority?)

- how many issues are open on this product and what is the priority listing? be open tell how it is. can we vote on the prios?

Probably nobody will even try to answer these question but if  somebody is brave enough it would give us (investors in a 655) a feeling of hope (depending on the answers though..)

I really would like this product if it was stable and does what it should do . But if there is no hope on a decent solution (in reasonable time; says the guy waiting for four months....) i must return it. (and urge others to do the same)

Don't want to rain on your parade but it has been fairly well documented that D-Link moderators post when and if they feel like it. Their main function is to referee. Your best bet is to let the company know how you feel through customer service (and that's a whole 'nother can of worms). If you can get every person on these boards to ditch their D-Link products I believe that is your prerogative and I don't think I would be wrong to say that none of the mods would try to stop you so long as you follow the rules. I hate to see all of the frustration in everyone's voice that can't seem to get the blasted thing to work. Mine does exactly what I need it to do and more. I wish your's did too.
Logged
Thread derailment: So easy a caveman can do it.

Fatman

  • Level 9 Member
  • ****
  • Posts: 1675
Re: Freezing router?
« Reply #295 on: June 26, 2009, 02:20:24 PM »

Clancy, you are getting good at doing my job for me, it is a good thing you are not going to be threatening my job from where you are.
Logged
non progredi est regredi

Clancy

  • Level 3 Member
  • ***
  • Posts: 202
  • I am not a number. I am a free man!
Re: Freezing router?
« Reply #296 on: June 26, 2009, 02:31:11 PM »

Clancy, you are getting good at doing my job for me, it is a good thing you are not going to be threatening my job from where you are.

My training will be complete just as soon as someone vaguely insinuates that I am on the payroll.

With the expert advice I give, you might take it under advisement to mysteriously discover that my IP address has been blocked. Maybe I'll start my own technical advice board and charge a monthly fee. Now do you feel threatened? Why are you laughing? Where's that customer service email address.........
Logged
Thread derailment: So easy a caveman can do it.

partach1

  • Level 2 Member
  • **
  • Posts: 52
Re: Freezing router?
« Reply #297 on: June 27, 2009, 03:08:24 AM »

Your best bet is to let the company know how you feel through customer service (and that's a whole 'nother can of worms). If you can get every person on these boards to ditch their D-Link products I believe that is your prerogative and I don't think I would be wrong to say that none of the mods would try to stop you so long as you follow the rules.
Clancy if you are not from DLink that it is a waste of time to discuss this with you.
If you read carefully you would have read i did contact TS (several times actually). The minute they run out of ´tricks´ (o try swithing of DNS relay, o setup wifi differently, o new software, etc.) answers on their standard response list they just decide not to react anymore (TS boss are you reading along please). Recently i send all  my findings AGAIN to info@dlink.nl (the website suggests to). And so far it looks like a black hole. So what am I supposed to do next?


I hate to see all of the frustration in everyone's voice that can't seem to get the blasted thing to work. Mine does exactly what I need it to do and more. I wish your's did too.
With this you insinuate that actually the product has no problem? Are you (then you ARE one the payrol:)? Most here would beg to differ about the product being ok judging from the comments
Many have proven it is faulty (dlink acknolwedges by bringing out new firmware) so why not fix it properly in one go an be done with?

And what is the statement `react if we feel like it´?! What is the job description here? This looks like a great Dilbert cartoon. Was it an overact employee who said ´hey we need to have a forum, every big company does´. Boss: ´what kinda value add would it bring to our company?´ Dilbert: ´well none other than we would have one´ Boss: ´will it fit within the project budget and what risks are involved? Dilbert: ´Project? Budget? it just give us something to do and we will not promise anything to visitors and just say we are only responding if we feel like it´ Boss: ´so just another day at the office´ Dilbert: ´you said it´

Sorry for giving you guys grief (well juding by how easy you can distance yourself by just reacting how and if you feel like it..) because believe me i do have better things to do. But after months I am getting kinda desperate. Really I have gone through all the hoops you have put in front of me. But everytime the show ends you make me jump into a concrete wall.

Can you agree with this:
Fact: software is not stable. Fact: software needs fixing. Fact: resolution time is too slow. Fact: customers don´t like to be left dangling....
Logged

mackworth

  • Level 3 Member
  • ***
  • Posts: 204
Re: Freezing router?
« Reply #298 on: June 27, 2009, 05:52:45 AM »

I have not--it's always been enabled.  My understanding is that DNS is intended for typing domains instead of typing an IP to access an external site.  I'll give it a whirl and see how things work.  I do have DNS caching disabled on one computer wired to the router, but the other computers (with caching enabled) have the same problem when the router performance declines.

When my router begins to perform poorly, the router configuration page becomes a hit or miss for trying to navigate and takes multiple tries to get through the pages.  If the router performance gets very poor, then I cannot even access main router configuration page, at all.  The router never stops functioning in an instant, it's a noticeable decrease in performance over a period of time.  The DNS Relay setting is independent from accessing the router configuration page via IP, unless I'm misunderstanding something about DNS...am I?  AND/or could the firmware have some funky problem with DNS where even the router cannot be accessed unless a physical reboot is performed?

A couple pages back we talk about how the DNS relay feature is useless.  It seems this feature is causing the router to slow down a freeze.  You should probably read the whole thread as long as it is, but atleast you will understand the problem better and you will see that the dlink response so far is that there is no problem with the firmware(funny huh?).
Logged

Alein

  • Level 1 Member
  • *
  • Posts: 19
Re: Freezing router?
« Reply #299 on: June 27, 2009, 11:57:32 AM »

I am new here, so I was planning to made a new post,but I have found this topic, so sorry for the form.

Hi,
I have a problem.
it seems that there is a bug in new firmware 1.31->

But lets start from beginning.

Product Page: DIR-655
Firmware Version: 1.31NA
Hardware Version: A2

Since firmware 1.31, my router become unstable. My connection are freezing, (P2P slow down to 1%(10-20KB/s on 10Mb/s network), WWW very slow, VoIP is working correctly (Linksys PAP2T) (static all settings), WDMyWorldBook 2T almost (FTP,CUPS,WWW,SAMBA slow down to ~10%, but services are working ), DIR-655 web interface is not reachable. However I have syslogng, so I was able to read log.

Log

First entry of 'ALG fail' Jun 20 , this same day of firmware upgrade. (This same entries I am getting almost everyday)


Jun 20 19:13:34 192.168.0.2 Sat Jun 20 20:13:36 2009 AWARE-AP System Log: Port forwarding ALG failed to allocate session for UDP packet from 192.168.0.15:65531 to 79.97.179.31:64567
Jun 20 19:14:04 192.168.0.2 Sat Jun 20 20:13:36 2009 AWARE-AP System Log: DNS relay ALG rejected packet from 192.168.0.5:3077 to 204.194.232.200:53
Jun 20 19:14:04 192.168.0.2 Sat Jun 20 20:13:36 2009 AWARE-AP System Log: Port forwarding ALG failed to allocate session for UDP packet from 192.168.0.15:65531 to 124.244.247.236:64268
Jun 20 19:14:04 192.168.0.2 Sat Jun 20 20:13:36 2009 AWARE-AP System Log: Port forwarding ALG failed to allocate session for UDP packet from 192.168.0.15:65531 to 202.152.90.75:18174
Jun 20 19:14:04 192.168.0.2 Sat Jun 20 20:13:37 2009 AWARE-AP System Log: Port forwarding ALG failed to allocate session for UDP packet from 203.90.63.129:18199 to 87.207.240.146:65531
Jun 20 19:14:04 192.168.0.2 Sat Jun 20 20:13:37 2009 AWARE-AP System Log: Port forwarding ALG failed to allocate session for UDP packet from 92.247.236.61:21319 to 87.207.240.146:65531
Jun 20 19:14:04 192.168.0.2 Sat Jun 20 20:13:37 2009 AWARE-AP System Log: Port forwarding ALG failed to allocate session for UDP packet from 207.47.173.50:62726 to 87.207.240.146:65531
Jun 20 19:14:04 192.168.0.2 Sat Jun 20 20:13:37 2009 AWARE-AP System Log: Port forwarding ALG failed to allocate session for UDP packet from 192.168.0.15:65531 to 93.125.200.128:44356
Jun 20 19:14:04 192.168.0.2 Sat Jun 20 20:13:37 2009 AWARE-AP System Log: Port forwarding ALG failed to allocate session for UDP packet from 192.168.0.15:65531 to 41.250.200.217:31432
Jun 20 19:14:04 192.168.0.2 Sat Jun 20 20:13:37 2009 AWARE-AP System Log: DNS relay ALG rejected packet from 192.168.0.5:3077 to 204.194.234.200:53
Jun 20 19:14:04 192.168.0.2 Sat Jun 20 20:13:38 2009 AWARE-AP System Log: Port forwarding ALG failed to allocate session for UDP packet from 122.27.142.215:10023 to 87.207.240.146:65531
Jun 20 19:14:04 192.168.0.2 Sat Jun 20 20:13:38 2009 AWARE-AP System Log: Port forwarding ALG failed to allocate session for UDP packet from 114.42.129.240:23005 to 87.207.240.146:65531
Jun 20 19:14:04 192.168.0.2 Sat Jun 20 20:13:38 2009 AWARE-AP System Log: Port forwarding ALG failed to allocate session for UDP packet from 114.39.174.72:21601 to 87.207.240.146:65531
Jun 20 19:14:04 192.168.0.2 Sat Jun 20 20:13:38 2009 AWARE-AP System Log: Port forwarding ALG failed to allocate session for TCP packet from 92.237.14.213:3185 to 87.207.240.146:65531
Jun 20 19:14:04 192.168.0.2 Sat Jun 20 20:13:38 2009 AWARE-AP System Log: Port forwarding ALG failed to allocate session for UDP packet from 192.168.0.15:65531 to 77.232.13.147:43063
Jun 20 19:14:04 192.168.0.2 Sat Jun 20 20:13:38 2009 AWARE-AP System Log: Port forwarding ALG failed to allocate session for UDP packet from 84.202.66.181:35590 to 87.207.240.146:65531
Jun 20 19:14:04 192.168.0.2 Sat Jun 20 20:13:38 2009 AWARE-AP System Log: Port forwarding ALG failed to allocate session for UDP packet from 192.168.0.15:65531 to 123.2.251.116:62266
Jun 20 19:14:04 192.168.0.2 Sat Jun 20 20:13:38 2009 AWARE-AP System Log: DNS relay ALG rejected packet from 192.168.0.5:3077 to 204.194.232.200:53
Jun 20 19:14:04 192.168.0.2 Sat Jun 20 20:13:39 2009 AWARE-AP System Log: Port forwarding ALG failed to allocate session for UDP packet from 192.168.0.15:65531 to 84.202.66.181:35590
Jun 20 19:14:04 192.168.0.2 Sat Jun 20 20:13:39 2009 AWARE-AP System Log: Port forwarding ALG failed to allocate session for UDP packet from 192.168.0.15:65531 to 82.72.215.58:46761
Jun 20 19:14:04 192.168.0.2 Sat Jun 20 20:13:39 2009 AWARE-AP System Log: Port forwarding ALG failed to allocate session for UDP packet from 192.168.0.15:65531 to 81.232.190.99:26998
Jun 20 19:14:04 192.168.0.2 Sat Jun 20 20:13:39 2009 AWARE-AP System Log: Port forwarding ALG failed


As you can see it affect TCP,UDP,DNS forwards. P2P (Torrent) is working on :65531 (forwarded), but it affect my WDMyBook too, DNS and SAMBA. All devices are affected, WiFi inaccessible.

I had this same configuration before upgrade,so there is no difference in settings.

My friend use this same router and he is getting similar problem, but without syslogng he can not check it, like I guess almost all of you.(e-mail with log is working)

Log is quite clear about the problem, it seems that there is a limit for forwarded connections.(Wrong limit, connections are not closing correctly,or they do not expire when not needed).That is what I expect . If you have similar problem , perhaps it is it.


Solution, turn off forwarding ALG is not an option. Actually it is like ask about time and get date.

Reboot is not connected with this problem.



By the way, I wish that one day we will be able to choose firmware without securespot, or USB support.Both services are useless (1st is $, and there is nothing interesting, 2nd it's nice joke, additional software is available only for x32 win, and even it is not working as it should.). Table for MAC filtering and WEB filtering should be bigger.Or my dream, configurable DHCP settings, I want to forward different gateway than DIR-655, for example PROXY.SNMP why not.




Logged
DIR-655 A2 FW 1.3x :(

Pages: 1 ... 18 19 [20] 21