D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: smapdi on May 01, 2009, 04:16:46 PM
-
I had this issue on 1.31 and 1.22b05, namely after a couple of days of use the router just drops off. I can't reach the WAN from both LAN or WLAN (1.22b05) or can't reach the WAN from the LAN and WLAN is completely down (1.31).
With both version the router is unreachable via browser or ping.
Could this be a symptom of overheating or just some wonkyness in the settings?
-
During that period, can you reach LAN?
-
During that period, can you reach LAN?
I didn't try to browse other computers on the LAN. Next time this happens I will give that a shot.
-
PLease let us know. If you can reach the LAN there might be a problem with your WAN device or even your OS/client.
-
Same here.
After upgrading, (from 1.22b5 and now at 1.31) it freezes in about 1.5 days I cannot connect to the router and lose WAN connectivity(LAN is fine). Have done the reset procedures suggested by Tipstr to no avail.
-
Same here.
After upgrading, (from 1.22b5 and now at 1.31) it freezes in about 1.5 days I cannot connect to the router and lose WAN connectivity(LAN is fine). Have done the reset procedures suggested by Tipstr to no avail.
How's your LAN / WAN connection configured (on both devices) ? Could be that your WAN device is causing the hickup/blocking since you don't seem to have a problem connecting on the LAN. If it's a total router freeze your LAN should also be blocked.
-
During that period, can you reach LAN?
LAN was reachable via wired connection to other wired clients. No access to router via HTTP or ping.
WLAN was completely dead.
I don't believe this is OS related since there have been 0 other changes to my network outside of 1.31
-
I have the exact same issue! After about 1.5 days my router just falls off the face of the earth. I have to reboot it for it to come back. Prior to upgrading to firmware 1.31 it was rock solid. I really am now regretting upgrading the firmware. :(
-
I recently updated as well on a DIR-825 and I'm seeing the exact same problem. I was running on 1.01 and waited until the full version which is 1.11 came out and it seemed to work fine, but with in a day or two I have the exact same symptoms. I can't connect to the router and nothing on the WAN side although the LAN appears fine. I have to reset the router each time to get things working again. I know the 825 and 655 are not identical, but seem similar and the firmwares came out within days of each other.
Jeff
-
I have this issue once in a while in that the internet seems to be running slower than normal and then the internet will just stop working. I can try to talk with the router via 192.168.0.1 and nothing responds, and this is on both computers, but I can connect to my other computers and see the files there. I have the beta 1.22b version with A4 firmware.
-
Ditto.
This problem occurred with 1.22b05, 1.30, and now 1.31.
There's also a bunch of people reporting it on the dslreports D-Link forum (http://www.dslreports.com/forum/r22335600-DIR655-Problems-with-websites-slow-loading-and-finally-404).
-
i do once in a while, but not too often, I dont blame it on the router though, even though I have to boot both router and modem.
-
Hardware revisions please...
-
A2, consistent failure after 1.5-2 days. Local DNS does not work but I can still ping using IP machines in the house. The router website is not responsive.
-
A2, consistent failure after 1.5-2 days. Local DNS does not work but I can still ping using IP machines in the house. The router website is not responsive.
Got an A2 myself and it's not a typical issue for the hardware revision.
How's you're settings?
-
A2 also... my HTTP traffic will gradually slow down till pages do not load, and attempts to access the router's UI fails. At this stage, I have to powercycle the router.
-
Happening to me on an A3. Also started with 1.22b05 as well.
-
This same thing is happenening to me on A4 1.31. My router requires a reboot every couple of days as web pages slow down to a halt both wired and wirelessly. I then can't access any HTTP pages at all, including the 192.168.0.1 router configuration.
-
I've noticed at times when this happens if I am able to get to the routers ip address, after the long wait, the pages will load with no formatting. But as before, rebooting solves the issue, since this never really happned before, I can only attribute it, at this time, to sever wireless degredation, interruption, or some unknown heavy load placed on the router. If that's the case, perhaps there is a memory leak in the OS or one of it's modules, that have not been found or corrected since 1.22
-
Same issue. I have been running into this since maybe 1.21 or something.
Its gotten to the point where I am actually looking at other routers.
Are you guys all using n clients or n/g missed? For some reason unknown to me, I thought I was able to connect once to the admin page with my iphone (g) but not my macbook (n) but maybe I am just crazy.
My Info:
A2, Qos On, firmware 1.31 but noticed this around 1.2+. Wireless is n/g mixed, 20mhz only on empty channel. Wish is also on. Not advanved dns or secure spot. I don't use the usb port.
-
I have been having this same issue since 1.21 on two different A2 units. This thread is similar to the following other threads on this issue:
http://forums.dlink.com/index.php?topic=5349.0
http://www.dslreports.com/forum/r22310851-DIR655-131-Firmware-available~start=100
http://www.dslreports.com/forum/r22335600-DIR655-Problems-with-websites-slow-loading-and-finally-404
-
I'm hardware A2, firmware 1.31, freezing every few days.
Hardware revisions please...
-
I have cleared my NVRAM between firmware upgrades using the method described here (http://www.dslreports.com/forum/r22315498-Info-Flush-out-the-NVRAM-Before-you-ReFlash-Your-Router-Updat). Though this problem still persists.
-
According to my uptimes, it's around every 3 days for me. Perhaps D-link can make an xml file that pulls the routers processes, memory and cpu usage and make a widget out of it. I know there are tonnes of .xml files already in the router that can display a lot of information, along with some other hidden pages that could peek some interest to some people.
-
yes you got a idea, what about a export "router report" that reports memory usage, whats running on the router etc for support?
might give firmware engineers alot more info about the condution the router is in before or after it freezes
i havnt updated mine yet am still on 1.22, 2009/02/10
-
I joined the forum just to post about this...
My revision is A4 and since updating to 1.31 I have had spontaneous reboots every 2 days or so...did a "clean" upgrade from 1.22b5...although 1.22b5 isn't perfect I did not have these reboots...also I do see the "slowing internet" with eventual disconnect (wired connection)...
-
I have had some random slowdowns and freezes for a while, and have told it here before too. A3 revision and it just do this whenever it feels like. Sometimes it takes a long time to open any pages, and suddenly it just works ok after this few second or longer freezes. Up and down. When this freezing happens, it takes ages to load router front page too. I have been used to this so havent see this to any problem until now theres same problems with others too... Same freezes with or without traffic.
-
I'm having the same issues. I'm about to throw my DIR-655 out the window and contact consumerist regarding this faulty firmware causing the router to basically brick.
-
I'm having the same issues. I'm about to throw my DIR-655 out the window and contact consumerist regarding this faulty firmware causing the router to basically brick.
Good luck.... Dlink and Dlink-lites are going to tell us its our environment or something lame like that.
I am getting pretty close to switching brands, but its annoying to switch considering I have the matching PCIe and external antenna, I have kind of invested in the dlink platform.
-
Bump...
Can we get a comment on this..? happened again to me last night.
-
4 days 21 hours uptime router is going strong on A2 f/w 1.22b05.
My problem can only be attributed to heavy load on the network or extreme interference, as I had suspected.
-
I am seeing the exact same problem on A2 hardware revision. Previous builds worked fairly well, but I do have to reset ever 2-4 days now :(.
If I had an option, I would happily move back to an older version.
-
I am seeing the exact same problem on A2 hardware revision. Previous builds worked fairly well, but I do have to reset ever 2-4 days now :(.
If I had an option, I would happily move back to an older version.
My A2 revision hasn't rebooted in weeks... ???
-
That's what i'm getting at. At least in my situation, where I explained that the network could not be reached, or if I am able to gain access to the router after a very long period of timeout, it would appear unformatted.
I suspect, that in my senerio, that it may have to do with one of the LAN computers doing some wierd torrenting, however I did see in the logs, whether or not it was during this time, that there were uPnP conflicts. But everything is still fine, going strong. Had to reboot the router today because one of the XP SP2 clients could not connect wirelessly, but the others could.
As usualy I would have thunked it to be localized to that computer. After doing work on it, and not connecting, I decided to just reboot the router and it connected. Must have been a noisy channel, since before it was on 1 and now it's on 8 (auto scan)
-
A3 version same freezing problem on 1.31. Last stable version that i remember was 1.11. Switching back to my old g router until new firmware solves this issue.
-
A3 version same freezing problem on 1.31. Last stable version that i remember was 1.11. Switching back to my old g router until new firmware solves this issue.
I'm staying on version 1.20 until this gets sorted out.
-
My A2 revision hasn't rebooted in weeks... ???
What kind of load do you put on your router? I have 6 people using a 655 for a total of 4n and 4g clients and an xbox and popcorn hour on the lan. This is happening all the time for me.
-
I have HW A2 and my router freezes every time I put it in the freezer. Don't underetand why this keeps occurring. The power cord fits fine through the freezer door and I thought it would keep itself warm to the touch, but it keeps freezing. HELP!
-
My load consist of 3 wired PC's, 1 wired xbox360 and 1 wireless -N- PC. Pages would load slow and it wasnt my bandwidth.
-
Xbox360, PS3, 1 Wired 4 wireless. but not all are on at the same time.
-
What kind of load do you put on your router? I have 6 people using a 655 for a total of 4n and 4g clients and an xbox and popcorn hour on the lan. This is happening all the time for me.
Load:
1 wired PC W7 x64; Torrents, NZB's, streaming media
3 laptops, wireless G (2) and wireless N (1); P2P and visdeostreaming
1 mediaplayer wireless G; watching streaming movies (2-3 hrs+)
On USB:
1 7-port hub (powered)
1 HDD (powered)
1 Samsung laserprinter
1 HP deskjet
1 USB pendrive
-
I also joined this forum to hopefully get a response from Dlink sooner rather then later.
1st off the only reason I even updated my firmware was because I decided to try VOIP with Vonage.
my setup:
Vonage: static ip
2 desktops with encore wireless n cards with XP
2 desktops with realtek gig run of the mil builtin cards with XP
1 xbox360 wired
1 wii wireless g
1 laptop Intel 4965 n wireless with XP
Everything worked great with firmware 1.21 with assigned Mac's to local network ip's.
After I figured out the only way I could do VOIP with the network traffic I have is with a static ip the new firmware 1.31na was released.
Now I'm getting locked up or non-connection on both wired & wireless everyday since I updated.
The only way I've been able to resolve the issue to to reboot the router.
It's not my systems nothing has changed, it's Dlink's firmware!
I understand that 1.31 from all the issues people are having will need to be tweaked.
Sooner rather then later...the wife and kids are ready to hang my ass.
-
I was going to copy & paste my config. screens in hopes of maybe someone might see a issue with my setup but decided not to as to much info.
However if you go into the advanced setup of the router and drag your mouse across the screen highlighting it and then paste it as if you were going to post on the message board you will see different categories that is pasted then what was on the sceen.
Not really of any importance, just kinda interesting options. I guess to many options is to much and the engineers are saving us for ourselves.
-
This is happening to me with 1.31 as well on a rev. A4. I wish I hadn't upgraded, because it was working fine with 1.21 and had been up for well over a month. Now, I have to power cycle it every couple of days, otherwise web browsing gets unusably slow and I can't access the web interface anymore.
-
This is happening to me with 1.31 as well on a rev. A4. I wish I hadn't upgraded, because it was working fine with 1.21 and had been up for well over a month. Now, I have to power cycle it every couple of days, otherwise web browsing gets unusably slow and I can't access the web interface anymore.
I found that if I disable DNS Relay on my DIR-655 FW1.31 my router does not exhibit the above issue. I'm up 8 days now! With DNS Relay enabled I would have to power cycle every 3-4 days. Seems the DNS Relay bug has yet to be fixed contrary to the change log.
-
I found that if I disable DNS Relay on my DIR-655 FW1.31 my router does not exhibit the above issue. I'm up 8 days now! With DNS Relay enabled I would have to power cycle every 3-4 days. Seems the DNS Relay bug has yet to be fixed contrary to the change log.
if you disable dns relay, does that mean you have to provide manual dns settings on all computers? Considering I am the only one that knows how to work the "internet box" as my roommates call it, that seems like a lot of trouble.
-
A2 also... my HTTP traffic will gradually slow down till pages do not load, and attempts to access the router's UI fails. At this stage, I have to powercycle the router.
A2 as well with the same exact issue! Dlink Engineers, is this enough people to qualify for some assistance?
-
A2 as well with the same exact issue! Dlink Engineers, is this enough people to qualify for some assistance?
So it's a a-typical issue, since my A2 works fine...
-
So it's a a-typical issue, since my A2 works fine...
I don't think your argument makes much sense. Just because you don't run into it, doesn't mean its an unusual issue. Maybe you just aren't doing whatever it is thats causing the issue.
I am a pretty technical person (software engineer), but my roommates are not. Its getting the point where they are getting fed up with this router and they don't know anything about firmware and router settings. They just want something that works after it had been running stable on 1.11 for a while(and upgraded past that for other issues).
-
if you disable dns relay, does that mean you have to provide manual dns settings on all computers? Considering I am the only one that knows how to work the "internet box" as my roommates call it, that seems like a lot of trouble.
I did not have to provide manual DNS settings to any of the computers (Win XP, Vista, Win 7, OS X, Netflix Roku, & XBOX 360). You may have to reset the network connection on the systems (or just reboot them) once after turning off the DNS relay feature so they get the revised DNS server addresses.
•If DNS relay is ON, the router gives the DHCP clients the router address for DNS lookup, and relays the request to the ISP DNS servers.
•If DNS relay is OFF, the router gives the DHCP clients the address of the ISP DNS servers directly.
-
So it's a a-typical issue, since my A2 works fine...
EddieZ - How many computers do you have connected via the DIR-655?
-
@alphad Here is EddieZ setup from page 3
Load:
1 wired PC W7 x64; Torrents, NZB's, streaming media
3 laptops, wireless G (2) and wireless N (1); P2P and visdeostreaming
1 mediaplayer wireless G; watching streaming movies (2-3 hrs+)
On USB:
1 7-port hub (powered)
1 HDD (powered)
1 Samsung laserprinter
1 HP deskjet
1 USB pendrive
-
EddieZ - How many computers do you have connected via the DIR-655?
Forgot some devices in the family setup* and traded in a laptop for PC ::), so this is the complete picture:
1 wired PC
1 wireless PC
2 wireless laptops
1 wireless streaming media center
*1 pocketPC wireless (not always connected)
*1 Samsung U600 Windows Mobile 6 Smartphone wireless (not always connected)
1 powered USB hub , with:
USB pendrive
1 HP Deskjet
1 Samsung laserprinter
1 500 Gb HDD
-
So does everyone getting freezes use DNS relay?
-
No, enabling/disabling makes no difference (ergo no issue)
-
I have Disabled the DNS Relay and for 2 days now, I have not had the Dir-655 freeze up and have not lost wireless connections!
Switched from 1.21 to 1.31 and have had nothing but problems from loads of dropped packets on the wireless to router freezing up and having to hard boot the router.
Time Warner Roundrunner is my ISP.
A1/A2 is what my router says I have.
Re: 1.21 Firmware causes slowdown with DNS resolution
« Reply #25 on: November 30, 2008, 01:03:38 PM » Quote
--------------------------------------------------------------------------------
Quote from: camber on November 30, 2008, 02:33:54 AM
Thats the point. But when i turn DNS relay off, the Internet wont work. When anyone has the solution i turn my DNS relay off forever.
After turning off DNS Relay, reboot your computers or release/renew their DHCP leases and they should be provided with the right DNS settings.
But, there's a second bug here. The second bug is that LAN-side DHCP requests that are filled before the auto uplink speed test is complete don't get DNS settings in their DHCP replies. (D-Link -- please acknowledge this bug, too!) To work around this bug, on Advanced - QOS Engine - set the automatic uplink speed test to manual and input the amount from the last auto test (usually shown there on the screen).
« Last Edit: November 30, 2008, 01:06:06 PM by funchords »
seems some issues were never fixed.
-
Guys, does anyone know where to download 1.30?
1.31 is a disaster comparing to 1.30
correction: I can't remember the previous version I had but it was the one with no-securespot.
-
Guys, does anyone know where to download 1.30?
1.31 is a disaster comparing to 1.30
correction: I can't remember the previous version I had but it was the one with no-securespot.
If you have 1.3x in your router, then you can only go to 1.3x :-[
-
so does anyone know a link to the previous 1.3x firmware
-
I have Disabled the DNS Relay and for 2 days now, I have not had the Dir-655 freeze up and have not lost wireless connections!
Switched from 1.21 to 1.31 and have had nothing but problems from loads of dropped packets on the wireless to router freezing up and having to hard boot the router.
Time Warner Roundrunner is my ISP.
A1/A2 is what my router says I have.
Re: 1.21 Firmware causes slowdown with DNS resolution
« Reply #25 on: November 30, 2008, 01:03:38 PM » Quote
--------------------------------------------------------------------------------
Quote from: camber on November 30, 2008, 02:33:54 AM
Thats the point. But when i turn DNS relay off, the Internet wont work. When anyone has the solution i turn my DNS relay off forever.
After turning off DNS Relay, reboot your computers or release/renew their DHCP leases and they should be provided with the right DNS settings.
But, there's a second bug here. The second bug is that LAN-side DHCP requests that are filled before the auto uplink speed test is complete don't get DNS settings in their DHCP replies. (D-Link -- please acknowledge this bug, too!) To work around this bug, on Advanced - QOS Engine - set the automatic uplink speed test to manual and input the amount from the last auto test (usually shown there on the screen).
« Last Edit: November 30, 2008, 01:06:06 PM by funchords »
seems some issues were never fixed.
Thats not a bug. All you need to do is renew the address of the PC AFTER the router is booted.
-
I have to disable the DNS to stop the Dir-655 from freezing up, dropping packets, slow speed...etc..
No I not talking about the release and renewing of an IP.
-
An interesting point to investigate is the role of DNS relaying in either the WAN configuration or PC client config. There could be a conflict there....
-
I feel like something must be up in the router for this to be happening.
I have a mix of windows, linux, xp, vista, and macs and its happening to everyone. I am going to turn of DNS relay and see how it works. Maybe something is wrong with the fix to DNS relay added in 1.22B05 and our router configurations.
-
Add me to the list of people with this issue.
My 655 has been rock-solid for over a year, and since updating to 1.31, I have had to reboot every couple of days.
DNS relay? That is off.
I have an A3 revision.
My network is as follows ::
1 Windows Home Server (wired)
1 XBox 360 (wired)
1 HP Network Laser printer (wired)
1 XBox 360 (wireless)
1 Tivo (wireless)
1 Macbook (wireless)
1 Windows 7 laptop (wireless)
2 Windows XP laptops (wireless)
1 Macbook Pro (wireless) -rarely used-
I torrent, usenet, play LIVE!, stream Netflix, etc.
As I said, I have had no issues at all until the update to 1.31.
NONE.
It is not me, it is you, fix please thanks. ;)
-
I've the same problem now too. A2 Hardware. 1.11 hadn't rebooted in 90 days prior to taking the 1.31 plunge. Now I've rebooted 3 times in the last week or so. Admin page becomes inaccessable, no new connections can be initiated.
However, my IPSec VPN tunnels to work strangely continue to function -- perhaps this is a clue. The WAN router is not completely frozen up.
-
Reboots are not the only problem. After the upgrade on A3 RTSP (over HTTP or UDP) is very glitchy and slow.
-
It's the Atheros chips on the miniPCI can't be the firmware it has to be hardware related issue. Two routers using Atheros one miniPCI A3 and the other like A4 integrated both show the same signs of issues. Disabling the DNS Replay isn't a good idea for a workaround. I just disable the wireless and use third party Wireless N Router with Wireless Access Point option. That disables all DHCP, NAT an etc and you just got Wireless Access Point with a Gig Green Ports. I've tried Broadcom it's okay but Ralink give more signal strength, wireless range and distance. No need to use DD-WRT firmware gear that support that.
Gone is the wireless issues weak signal, 404, slowness, freeze, drops an etc.. I can now access my business web site on my ISP host through wireless. I couldn't do that with Atheros, prior I could but slowly it won't connect it just times out from the router.
Now keeping the DIR-655 A3 as wired router and using third party Wireless B/G/N in mix mode, auto channel, auto width, 20/40Hz Protect Mode disabled (if that is on none of the systems can see the AP).
-
Was rebooting every 1.5 days, now up 3 days and counting with DNS relay option turned off.
-
Four days, and had to restart the wireless. Pictures below show what I come to after a period of timeout trying to connect to the router. Log file is included as a text file as well. Noticed that the router was dropping and blocking packets from and to my machine, as well as dropping DNS traffic.
The only thing that was going on at this time was I was downloading moblin beta 2 from www.moblin.org. Not sure if it was through the HTTP method or FTP. But the download was only going at 380Kb/s out of 600Kb/s that is my cap. Not to mention, I could be using all the WAN bandwidth, should not interrupt local traffic whatsoever out of a 300MB connection.
(http://hpzdfa.bay.livefilestore.com/y1pJOB6Q4TMDPjkxNtwaKnzzu9tkIMyxfwwNthwZbCfbkGCyQwIO3ZxBK-6Uy18MfBaHS40FzYRcI3EYhOSLvdFATyeZBxMpPa1/unformatted.JPG)
(http://hpzdfa.bay.livefilestore.com/y1pVOX9b-SYIYc_qfw30KaSSNY9jtf2EgIxTLyL8nh69_8o8y_t2EFZLxP-w2mRSPnlF6dAprpcNV8DTGT2VXPgvLzPOzY04WZL/unformatted2.JPG)
(http://hpzdfa.bay.livefilestore.com/y1pCoPr3qRP7ohcsvxh_3OpEJPE4PV55bfSXc2yiaOrbN2w4GSAozxBPFLQZYZM1hUO2yuWzTeZfszDsNjDVDBBjQn1V7efXm9H/log.JPG)
http://cid-b8468fd3ff19d4bc.skydrive.live.com/self.aspx/docs/Gatewaylog.txt (http://cid-b8468fd3ff19d4bc.skydrive.live.com/self.aspx/docs/Gatewaylog.txt)
-
I've seen this before. Are you seeing wired or wireless? Do a hard reset and hold it for 90 secs. Then release. Do this with power on and remove all WAN/LAN port connections. If it still does it. Take that router over to a friends house connect it directly to their PC. If you still see the above. Then the router has issue.
-
Are you running jumbo frames on your LAN?
-
Your download speed also depends on the upload speed the FTP or HTTP server has to offer. And that does not always equal your home bandwidth. So that would not necessarily be the cause.
-
YES!! I'm not going crazy. I'm seeing the exact thing on my A4 running 1.30 (DNS Relay on). Every couple of days my router goes kaput and i can't browse to the 192.168.0.1 to see whats going on. Unfortunately the only way to bring it back was to reboot the router (and sometimes i think it rebooted on its own due to some failsafe error). That would kill my logs and I couldn't see what was happening right before it died. However today I saw the "slowdown" beginning to happen so I immediately went to the logs to see what was being reported. I saw EXACTLY what lotacus's logs report on my router as well:
Dropped Packet... IP Protocol 17 (50 - 100 lines)
Dropped Packet... IP Protocol 6 (50-100 lines)
DNS Relay ALG rejected packet ( 50-100 lines)
After 5 min of above, the router ceased to work and I had to pull power from the router to reset.
Here is my network at the time of the failure...
Cable modem > wired > DIR-655
DIR-655 > wired > desktop pc
DIR-655 > wireless > laptop
DIR - 655 > wireless > DAP-1522
DAP-1522 > wired > desktop pc (was not on at the time)
-
Perhaps it is a good idea to send the board mods a detailled oevrview (printscreens?) of settings and paired modems. Perhaps they can reproduce the issue with this info. Just saying because I have a hunch they really are not able to reproduce...
-
If someone can relay what print screens I can provide and to whom, I'd be more than welcome. It's tough to catch some screens after the fact because the router reboots and loses the logs.
-
If someone can relay what print screens I can provide and to whom, I'd be more than welcome. It's tough to catch some screens after the fact because the router reboots and loses the logs.
Logs can be sent by email, let's say every 5 minutes. Just create a schedule (or more) and mark the checkboxes in Tools - Email settings ;D
I was aiming more at screens from the router setup chapters.
I've contacted Lycan with this idea. I think it's time to get some input about the different configs to the Dlink tech guys.
-
I'm not sure what's going on. I *thought* I could reproduce it by re-downloading moblin beta2 which seemed to work, or so I thought. BTW it was through HTTP that the download was happening, but even then, since the router konked out, the download failed anyways.
When this happened (at the time of my most recent post), it was only I on the network and only that download happening, no torrents either.
I'm trying to figure out what could be going on. I'll will see if I can reproduce it. There were 3 other wireless networks on Channel 1, at the time, since then I moved it over to another channel with weaker signals, just in case. I don't know if Wireshark will provide much detail to work with what could be the cause of the problem. I still think a widget or something to view cpu/mem/process information may be helpful to see IF the router is becoming too bogged or if there is some sort of memory leak.
-
I bought a new Dlink DIR-655 A4, it came with firmware v1.20 installed and I have not experiences any of this slow down or instability with mine. But from what I've read so far on this forum thread, it sure sounds like they have some sort of memory leak problem in those affected firmware releases.
To Dlink firmware developer(s), you should check your code to ensure that there are no memory allocation spaces being overwritten. Example is where you might have allocated a fixed array or table size and due to circumstances during use your program code fills up the array to its limit and tries to write more data to the array overrunning its bounds. Therefore it will start writing data into another reserved memory space and corrupt other data or code.
If it is a memory leak, that means you are not properly freeing up allocated memory when some "repeatedly used" routine is done using the memory space. Therefore it leaves the unallocated memory in place (using up memory) and when the routine is called over and over again to allocate memory for itself, it gradually eats up all the available memory and ... CRASH!
-
Most of these issues started with the new core/SDK from Ubicom being updated with 1.3x. So I'm thinking either the Ubicom update is flawed or the firmware needs more of your story; because of the changes in th new Ubicom core/SDK they cannot 'copy & paste ' anymore. They tend to do C&P quite a lot,...
-
I too am having the same problem every couple of days my DIR 655 A2 1.31NA router will become non-functional and I have to reboot.
How soon do you think DLINK will release a fix to this, quite annoying.
-
Pull out Atheros MiniPCI (A1, A2, A3) out and re-seated it.
Did 180 seconds reset.
First 30 seconds press reset
Second 30 seconds unplug the power cord and still press reset
Third 30 seconds plug in the power cord and still press reset
Fourth re-flash to 1.31NA
Fifth 30 seconds press reset
Sixth 30 seconds unplug the power and press reset
Seventh 30 seconds plug in power and press reset
Now ready to use the router.
It's working no issues..
-
I just tried Tipstir's idea and will post back in several days under this topic if problem still exists.
@Tipstir: Are you still running your upgraded chip or the original one. I ask because i seen ur topic at dslreports
-
CHEAK YOUR LAN.
-
I think what people are not understanding is that this is an issue "over time". I can certainly reseat something, 30/30/30, reboot, stand on my head, worship a false idol, whatever... and I will get it up and running every time. However, after a few days of working fine, there is a point in time where I will get diminishing returns until it freezes. I will certainly try Tipstir's approach as well as Eddie's scheduled emails. With that said it is very hard to reproduce. I can relay every setting and screenshot if Dlink wants to try and recreate our issue.
I thought it was only affecting myself, but after reading this board and dslreports, it appears it's not completely atypical.
-
i'll let you know again, in two/3 more days to see if i have to rest it. :)
-
My A4 running 1.22b5 (I think its b5) currently has had its wan connection open for "51 Day 5 Hour 41 Min 39 Sec" (and increasing, obviously).
But, I'm sure "my setup" has little to do with why its so. I've got a static WAN port to another internal-network range, my wireless is off (location of router makes wifi useless, but I got it for gigabit anyway).
I know if I try to change the ntp server, the thing crashes (in an infinite loop, as best I can tell its because it tries to update NTP while doing the uplink measurement). I recall (approximately) 2 months ago when I updated the firmware that it gave me ABSOLUTE HELL about "measuring uplink speed" even -AFTER- I'd disabled the setting in the menu to do so. I know that if I turn on DNS relay I get more mdns resolution failures than with it off--but in my case turning off DNS relay just means that it hands off the IP address of the upstream router (also in my larger network) for DNS, which isn't really a problem.
Effectively I only use the thing as a logging firewall + DHCP server for this subnet. At this point things *SEEM* to have become stable enough to be acceptable, even though mdns occasionally fails for no reason (which I've now been attributing to OSX being confused by the double gateways).
But, I assume the most significant difference between my setup (aside from the uptime) and anyone else's that isn't working is the disabled wireless.
I still wish the 655's DHCP server behaved more like the one found in the DI604/614 router(s) however simple/broken they were they allowed machines connected though wireless and wired to switch connection media without dropping connections (I'm not sure how, but the DI604/614 did hand out the same address to both interfaces, and somehow between OSX/Linux/Router they kept it straight as to who was connected to where or whatever). /end tangential rant/
That was alot longer than I'd originally intended to write, oh well. Hope some feedback on a setup that seems to *work* (as screwed up as it is) might help somebody somehow.
-
Can anyone comfirm this problem is being looked at by the engineers?
-
Can anyone comfirm this problem is being looked at by the engineers?
I have been looking for that confirmation myself...
-
Ubicom products DO NOT have crash resets. The 30/30/30 that you guys are referring to does NOT effect 625/628/655/4500/825/855 model routers.
IF your unit is locking up at specific intervals throughout the day, I suggest a syslog program on a hardwired PC that way you can capture the logs before the unit fails. With the logs you should be able to determine the point of failure.
-
Ubicom products DO NOT have crash resets. The 30/30/30 that you guys are referring to does NOT effect 625/628/655/4500/825/855 model routers.
IF your unit is locking up at specific intervals throughout the day, I suggest a syslog program on a hardwired PC that way you can capture the logs before the unit fails. With the logs you should be able to determine the point of failure.
I bet they will start debating that it does work. ;) Those things are called 'myths'.
-
I just purchased another router because of this problem.
I did a little test, using an old g router from another company. My dir-655 keeps stuttering (along with the slow to freeze problem here, which does seem better since disabling DNS relay), and it causes me to drop my remote desktop connection into work. Switched to the old g router, stable. Then switched back to 655, drops.
I want to use my 655 as a g only access point, and I am hoping that by turning of the firewall, Qos, etc everything will work out ok.
-
I bet they will start debating that it does work. ;) Those things are called 'myths'.
What can i say... Provoke again with brown tongue too. ::)
I'm glad we have you, so our sad and dumbass world is in balance.
I bet next we get some explanation why you said that.
-
That's one bet you lost. You reacted though.
-
That's one bet you lost. You reacted though.
I have to ask, do you work for D-Link or are you just a fanboy? More often than not, your comments are just condescending worthless drivel.
As for me, I am fed up with D-Link and the progressively worse support for this product (EOL as it may be). This is definitely the last D-Link product I will purchase unless I hear from reliable sources that they cleaned their act up (reliable sources would be smallnetbuilder.net, broadbandreports, hardocp, etc.).
I think a WRT310N with DD-WRT will be a good replacement and at least I know that the community there is knowledgable and helpful and that the devs are more than willing to troubleshoot issues.
-
I have the same issue and it's making mad.... I need it to be reliable so I can remote login to my home computer.
I know it says you can't downgrade.
Is there a hack or way to downgrade anyway ?
-
That's one bet you lost. You reacted though.
Yep. I lost. We lost. Shame me. I should not doubt you. :-X
Blind lead blind...
-
I have to ask, do you work for D-Link or are you just a fanboy? More often than not, your comments are just condescending worthless drivel.
As for me, I am fed up with D-Link and the progressively worse support for this product (EOL as it may be). This is definitely the last D-Link product I will purchase unless I hear from reliable sources that they cleaned their act up (reliable sources would be smallnetbuilder.net, broadbandreports, hardocp, etc.).
I think a WRT310N with DD-WRT will be a good replacement and at least I know that the community there is knowledgable and helpful and that the devs are more than willing to troubleshoot issues.
If I was in anyway connected to Dlink I would behave more polite towards your kind probably.
Fanboy...is that you call somebody who wants to hear/say more than "It's the firmware"?
Good luck with the WRT (from the bottom of my heart. But you would have guessed that).
-
Ubicom products DO NOT have crash resets. The 30/30/30 that you guys are referring to does NOT effect 625/628/655/4500/825/855 model routers.
IF your unit is locking up at specific intervals throughout the day, I suggest a syslog program on a hardwired PC that way you can capture the logs before the unit fails. With the logs you should be able to determine the point of failure.
Hmmm... well 1st off there are sevral ppl that have came to this message board to try to figure out what the heck is going on.
If what you say is true about "Ubicom products DO NOT have crash resets" then I bet most ppl wish they did cause trying to track issuse that happen now & then is crazy. Example:I have an issue that only happens on friday if it's raining and I'm driving a red car with more then a hafe a tank of gas and I ware a white shirt with no stains from lunch which I had with my wife...etc...etc...etc..
People are having all kinds of issuse since updating to FW 1.31. LOOK at the posts not just "freezing router" but others also may have something in comin that the adverage joe can't see.
portforwarding: can't save port settings on reboot of router after changes are done
DNS Lan side issues: dropping wireless, packet loses, 404's sites, icmp 3 errors, shareport
I'm sure there are others but when ppl have issues with default settings after updating then somethings wrong.
-
The key to solving this is enabling Dlink to replicate the issues that are reported. Dlink has explained they cannot replicate the issues in the lab environment. So nobody seems to deny anything (I'm 100% sure Dlink staff have read each and every post), but if you want to solve it, you got to be able to diagnose in the lab to see what's going wrong. Only people reporting: 'it does not save x" or "it reboots" without the context of settings and configs is just not enough.
It's like asking a doctor to diagnose a disease when you only say to him "I don't feel well". But looking at the comments I've received this seems to be the genuine expectation of the local bunch here...
-
The key to solving this is enabling Dlink to replicate the issues that are reported. Dlink has explained they cannot replicate the issues in the lab environment. So nobody seems to deny anything (I'm 100% sure Dlink staff have read each and every post), but if you want to solve it, you got to be able to diagnose in the lab to see what's going wrong. Only people reporting: 'it does not save x" or "it reboots" without the context of settings and configs is just not enough.
It's like asking a doctor to diagnose a disease when you only say to him "I don't feel well". But looking at the comments I've received this seems to be the genuine expectation of the local bunch here...
EDDIEZ.........I did not quote you! Who are you?
Since you have to respond EDDIEZ I understand what you said and it makes sense and I know I did not post a screen capture, config. settings. I would almost bet DLinks customer service is getting hammered and DLink knows somethings wrong.
All I was trying to do was bring up issues that people have and keep engaged in a way that could be productive.
As for your comment about the local bunch here can be done without....not helpful.
I bought my Dlink and yes my expections from DLink if they want my $$$ in the future is to fix the problems, in whatever means that works.
I updated to fw 1.31 because I was trying out VOIP and had issues of dropped calls or choppy audio. As I don't claim to know anything, it was learning curve to find a way for me to make it work.
I'll try the next few days if I have time to post my details with colors pictures and just maybe I can do a powerpoint walk through.
-
i also have this problem when but i am also getting a slowdown when looking at web pages it will slowdown and speed up on and off it gets annoying
-
I'd be happy to send my router for analysis if D-link would send another in return
-
Turning off DNS relay made things much better for me.
-
Turning off DNS relay made things much better for me.
Yeah, I agree. Although now I am having problems where it seems to stall for a couple seconds, makes me drop any remote desktop sessions I have open. But the slow down to 404s to completely freeze seems to remedied by turning it off.
-
Yep no freezes for me since turning DNS Relay off.
-
EddieZ, do you use dns relay? Apologies if you already mentioned that you did/didn't.
-
The key to solving this is enabling Dlink to replicate the issues that are reported. Dlink has explained they cannot replicate the issues in the lab environment. So nobody seems to deny anything (I'm 100% sure Dlink staff have read each and every post), but if you want to solve it, you got to be able to diagnose in the lab to see what's going wrong. Only people reporting: 'it does not save x" or "it reboots" without the context of settings and configs is just not enough.
It's like asking a doctor to diagnose a disease when you only say to him "I don't feel well". But looking at the comments I've received this seems to be the genuine expectation of the local bunch here...
Actually, thats how every diagnosis should begin. The only problem here is that Dlink (playing the role of doctor) has not asked "what hurts". I think there have been a number of people willing to offer configurations, settings, screenshots, network topology, etc. One guy even posted his own log to show some of the exact errors. These submissions have received no response. Collectively, people are guessing and clicking off DNS Relay simply because one of the errors they see in the log mentions DNS relay specifically. I would wager that 90% of the people (including myself) here have no idea what DNS relay does. Most of us are not network engineers. We are simply purchasing a consumer level product and asking for consumer level support. Without Dlink commenting on "we are looking into it", people feel ignored and that their problems are dismissed.
-
Actually, thats how every diagnosis should begin. The only problem here is that Dlink (playing the role of doctor) has not asked "what hurts". I think there have been a number of people willing to offer configurations, settings, screenshots, network topology, etc. One guy even posted his own log to show some of the exact errors. These submissions have received no response. Collectively, people are guessing and clicking off DNS Relay simply because one of the errors they see in the log mentions DNS relay specifically. I would wager that 90% of the people (including myself) here have no idea what DNS relay does. Most of us are not network engineers. We are simply purchasing a consumer level product and asking for consumer level support. Without Dlink commenting on "we are looking into it", people feel ignored and that their problems are dismissed.
Very Basically: DNS is what i used to translate an hostname like www.google.com into an ip address like XX.XX.XX.XX. When you visit a website for the first time on your computer, it has to look up the ip address based on the address you give it. It then stores that information temporarily on your computer. Your internet provider provides DNS servers that provide your computer with this information. By using DNS relay, instead of connecting to those servers, your computer asks the router for this information and then the router connects to your isp to get it. The information is then relayed through the router to your computer.
This feature was broken in 1.21 I think and then was fixed officially in 1.31. Although it was fixed, it seems like there is a new issue. This corresponds to the symptoms people are seeing. It works when you reboot, and then over time (as you make more DNS requests), it starts to slow down to a crawl to a freeze.
So everyone should see if turning it off fixes this issue.
[edit]
I will also like to say that apparently the DNS relay in the 655 isn't cacheing so I am not even really sure what the point of DNS relay on the 655.
DNS caching means that if computer1 went to google.com, the router would get the DNS information and store it until it expires. Then when computer2 went to google.com, the router would already have the information and provide that to the computer. This would save the router from having to get that DNS information a second time.
However, since its direct, the router has to connect to the isp dns servers everytime there is a dns request. So really there is no point in using DNS relay.
-
It's a consumer level conveinance thing. We implemented it so that the router would be a known DNS agent plus it enables advanced DNS.
For all those that are suffering from the DNS slow down, can you confirm that advanced DNS is disabled?
-
I tried turning off DNS relay to see if it helped and when I did I couldn't no longer connect to the Internet? Turned it back on and I could connect again? How, or should I say why do I lose Internet connectivity by turning off DNS relay?
-
Where is DNS relay turned off?
"Advanced DNS Service" is turned off here, but can't find anything about DNS relay.
-
I tried turning off DNS relay to see if it helped and when I did I couldn't no longer connect to the Internet? Turned it back on and I could connect again? How, or should I say why do I lose Internet connectivity by turning off DNS relay?
When DNS relay is off the PC will need to renew it's IP address. You can simply restart the computer or you can repair the connection.
-
It's a consumer level conveinance thing. We implemented it so that the router would be a known DNS agent plus it enables advanced DNS.
For all those that are suffering from the DNS slow down, can you confirm that advanced DNS is disabled?
What DNS slowdown are you referring too? Are you referring to the problem this thread is based on or something else?
I had DNS relay on and advanced DNS off and securespot off. With DNS relay on, the router would eventually get so slow it would just freeze, the only way to get it back was to reboot. Is that the problem you are talking about? Cause thats not caused by slow DNS queries.
-
I had DNS relay on and advanced DNS off and securespot off. With DNS relay on, the router would eventually get so slow it would just freeze, the only way to get it back was to reboot. Is that the problem you are talking about? Cause thats not caused by slow DNS queries.
PLease tell us the most important part you left out....: did turning off DNS relay solve that issue for you?
-
PLease tell us the most important part you left out....: did turning off DNS relay solve that issue for you?
Sorry. Yes, it seemed to fix the that specific issue although now that i am not restarting it everyday I seem to be running into other "stutter" type issues where my connection to the WAN seems to pause.
-
Just happened again, and I managed to save a log.... many IP Protocol 6 and IP Protocol 17 errors and a DNS relay ALG rejected packet error. I can send it via PM to an admin if they want it. My router is currently slowed dramatically and it took me 4 min to get to this site to post this. I'll try and relay every setting I have configured although its tough because connecting to the router right now is slow and intermittent...
DIR-655 A4 1.30 NA
mixed g & n (SSID invisible)
DNS Relay is enabled
DCHP enabled w/ static ips reserved
WPA2 only enabled
MAC filtering enabled
SPI enabled Defaults (UDP address restricted, TCP port and address restricted)
Advanced DNS disabled
WISH inactive
Wifi Protected setup disabled
QOS inactive
Securespot disabled, no Port Forwarding, no application rules, disabled uPnP, no routes set up.
EDIT: Additionally, I can no longer get to the GUI to login to the router from both the hardwired and wireless desktops. I get a white screen with Please Try Again, or Connection: Close.
-
It's a consumer level conveinance thing. We implemented it so that the router would be a known DNS agent plus it enables advanced DNS.
For all those that are suffering from the DNS slow down, can you confirm that advanced DNS is disabled?
I can confirm that my advanced DNS is disabled.
-
I too am now stuck with this v1.31 problem. No longer is my network reliable. My unit will reboot on it's own or simply lock-up and prevent LAN access for no apparent reason.
Is there anyway to go back to a previous version? If so, please tell me how. I run a weather server and a few other community services that are now longer reliable because of this problem.
I can't believe that this is an official release and not some sort of beta version.
I run with Adv DNS disabled and SecureSpot disabled. WPA only on main WLAN w/ guest WEP WLAN as well. What other kinds of data do you require to help me?
-
I too am now stuck with this v1.31 problem. No longer is my network reliable. My unit will reboot on it's own or simply lock-up and prevent LAN access for no apparent reason.
Is there anyway to go back to a previous version? If so, please tell me how. I run a weather server and a few other community services that are now longer reliable because of this problem.
I can't believe that this is an official release and not some sort of beta version.
I run with Adv DNS disabled and SecureSpot disabled. WPA only on main WLAN w/ guest WEP WLAN as well. What other kinds of data do you require to help me?
In the router go to the setup tab, network settings, uncheck enable DNS relay and save settings. reboot router.
A temp fix until the techs can figure out the issue.
Worked for me and a few others, may for you also depending on your setup or config.
-
In the router go to the setup tab, network settings, uncheck enable DNS relay. reboot router.
A temp fix until the techs can figure out the issue.
Worked for me and a few others, may for you also depending on your setup or config.
Thanks so much for the response!
I thought people were talking about disabling the Advanced DNS Service as the fix. I didn't realize that the DNS relay was hidden on another screen. Thanks again so much! I hope it works.
-
It's a consumer level conveinance thing. We implemented it so that the router would be a known DNS agent plus it enables advanced DNS.
For all those that are suffering from the DNS slow down, can you confirm that advanced DNS is disabled?
Indeed I have Advanced DNS Service and DNS relay disabled. Everything seems back to normal, no slow downs or dropped packets like it was when both were enabled. FYI:RoadRunner ISP
Have VOIP with Vonage and a Static ip for Vonage outside the scope of DHCP which I had switched to during the time I had updated my FW to 1.31NA because Qos was not cutting it with the network traffic I have.
During the busy time of day phone service can still have choppy audio @ times but I' still trying to work through this.
-
Thanks so much for the response!
I thought people were talking about disabling the Advanced DNS Service as the fix. I didn't realize that the DNS relay was hidden on another screen. Thanks again so much! I hope it works.
I have both Advanced DNS Service and DNS Relay unchecked.
-
Now that I've got DNS relay setting switched off my weather server, which is on a dedicated IP, no longer knew how to get outside of the network, but I've changed that back to DHCP and reserved it in the D-Link so it should be able to find it's way once again.
Thanks again for the heads up on that setting. I'm looking forward to seeing things clear up.
Cheers!
-
Every post from page 7 starting at saint12 should be moved to the dns slowdown thread. :P
-
Along with tipstirs idea and jason1722x i no longer have these issues for now. Thank you.
Cant wait to hear the remarks eddiez will come up with now.
-
Along with tipstirs idea and jason1722x i no longer have these issues for now. Thank you.
Cant wait to hear the remarks eddiez will come up with now.
Hey I have not been hear but maybe a week and I'm just trying to help. Eddiez has alot of posts and seems involved from the posts he has made. Besides I take no credit for it wasn't my Idea.
I'm no IT guy at @ but people suck..lol, they for the most part create their own problems.
-
EddieZ, do you use dns relay? Apologies if you already mentioned that you did/didn't.
You don't like to hear this from me, but I'm error free with Advanced DNS enabled (so also DNS relay enabled).
Cant wait to hear the remarks eddiez will come up with now
I don't understand... Do you want to see a rude remark? My statement above will suffice. But if disabling fixes the issue...great!
-
Now that I've got DNS relay setting switched off my weather server, which is on a dedicated IP, no longer knew how to get outside of the network, but I've changed that back to DHCP and reserved it in the D-Link so it should be able to find it's way once again.
Thanks again for the heads up on that setting. I'm looking forward to seeing things clear up.
Cheers!
Give the weather server a puiblic DNS...............
-
Give the weather server a puiblic DNS...............
I have done that and don't have problems with my network servers anymore.
<<< BUT >>>
I just had an unexpected reboot out of the blue. The unit reconnected and is working fine now it seems, but it did reboot for no apparent reason.
-
Run a syslogger, see if you can capture it doing it again.
-
I'll see if I can get my Macbook setup next to it with a program like that running.
-
Yea syslog will be able to capture the logs before the unit reboots and drops the entries.
-
A2 - 1.21
Originally did not see any real problems with f/w 1.02 until the wireless was enabled. This then caused problems with the router at least once a day where the router would not display the login page and the network was either intermittent or non-existent. Upgrading to f/w 1.21 made the problem less frequent (once every 3 days), but is still not working. I was thinking of trying the 122b04 f/w but cannot find it available anywhere.
-
Would like to update that, as expected, the router is acting up again today. There is a point were wireless access is spotty, as well as fails completely. Devices can associate with the access point, but pinging an outside address fails. Can ping the router, but cannot access the web gui. The same effect with wired PC.
The logs show the same thing as my previous entry.
-
Today I had the first time this problem with my DIR-655.
It was still possible to connect to my NAS in the LAN (DNS-323). But it was not possible to get anything from the router or to go out to the internet.
I have a syslog from the time when this happend, and when I had to restart the router.
Lycan, if you send me a PM, then I can send you the syslog from that time.
/Geraner
-
Lycan, if you send me a PM, then I can send you the syslog from that time.
You can search for user 'Lycan' too in PM department...
-
I've seen this before. Are you seeing wired or wireless? Do a hard reset and hold it for 90 secs. Then release. Do this with power on and remove all WAN/LAN port connections. If it still does it. Take that router over to a friends house connect it directly to their PC. If you still see the above. Then the router has issue.
This would obviously temporarily fix the issue, since the issue arises over a period of time, usually for me, every 4-5 days, regardless of network activity.
Are you running jumbo frames on your LAN?
No. The lan is a typical home setup. Only one PC connected via ethernet @ 100Mb auto neg.
-
You can search for user 'Lycan' too in PM department...
Ok, I have send him a PM with the syslog included.
-
Hi, I've got H/W version: A3 and it also was working fine until i upgraded to firmware version: 1.31NA
My typical load is:
2 computers connecting at 1000Base-T
1 computer and an Xbox 360 connecting at 100Base-T
3-4 wireless laptops connecting over wireless-G
2-4 of the computers are regularly streaming video 3-8 hours a day each, in addition to a slightly larger than average amount of regular network traffic then you'd expect for 3 users
There was no problem with the router, but since i upgraded the firmware, every few days everything has been grinding to a halt on both the wireless and wired connections. When this occurs, the wired computers is unable to reach the router.
my question is, and I'd prefer if this was to be answered by the board mod/tech engineer (that's just what I'd expect, since this is D-Link's forum), could you make a single post with a clear and concise way to fix this issue.
I've been filtering through 10 pages of chatter on this thread alone and there seems to be a few things that sound legitimate, a handful of guesses and a couple of wild conjectures. A few people said turn off the DNS relay, a few people said that the DNS relay issue is just a symptom of the real problem and as far as I could see the only thing the technical engineer added so far was the following to defend the wild accusations that some people have thrown around that he knows to be false and to help explain some of the small issues related with the side effects of one possible fix, that nobody has seemed agree works, including the technician (except for a few people who have said they haven't seen a problem for 3 days after applying the fix, which is nice but not conclusive, as the issue seems to take about 5 days to fully disable the product)
I'd just like an official word on where this crippling issue stands and if there is a fix for this or possibly a new firmware in the works that could fix this issue.
-
Hi, I've got H/W version: A3 and it also was working fine until i upgraded to firmware version: 1.31NA
My typical load is:
2 computers connecting at 1000Base-T
1 computer and an Xbox 360 connecting at 100Base-T
3-4 wireless laptops connecting over wireless-G
2-4 of the computers are regularly streaming video 3-8 hours a day each, in addition to a slightly larger than average amount of regular network traffic then you'd expect for 3 users
There was no problem with the router, but since i upgraded the firmware, every few days everything has been grinding to a halt on both the wireless and wired connections. When this occurs, the wired computers is unable to reach the router.
my question is, and I'd prefer if this was to be answered by the board mod/tech engineer (that's just what I'd expect, since this is D-Link's forum), could you make a single post with a clear and concise way to fix this issue.
I've been filtering through 10 pages of chatter on this thread alone and there seems to be a few things that sound legitimate, a handful of guesses and a couple of wild conjectures. A few people said turn off the DNS relay, a few people said that the DNS relay issue is just a symptom of the real problem and as far as I could see the only thing the technical engineer added so far was the following to defend the wild accusations that some people have thrown around that he knows to be false and to help explain some of the small issues related with the side effects of one possible fix, that nobody has seemed agree works, including the technician (except for a few people who have said they haven't seen a problem for 3 days after applying the fix, which is nice but not conclusive, as the issue seems to take about 5 days to fully disable the product)
I'd just like an official word on where this crippling issue stands and if there is a fix for this or possibly a new firmware in the works that could fix this issue.
2nd that
-
Just an update.... again, it happened. :P
-
Can you post a pic of the advanced wireless page?
-
An update to my issue... I have been checking the logs periodically to try and ascertain where this freezing/reboot issue is occuring. I happened to check the log last night and didn't see any issues for the previous 2 days. When I checked the log this morning, the log was new because the router had reset itself sometime during the night. I don't know if this will help, but everytime this router resets itself, it reverts back to a previous date (I assume this is the date I did the 30/30/30 process and flashed the router with the new firmware). I have to re-copy my computer settings to get the right date back in. I have not changed any settings from my previous post.
-
I also get this issue consistently, and it's really obnoxious. :(
Is there a firmware update in the works? Or a way to revert?
-
Can you post a pic of the advanced wireless page?
As requested.
(http://hpzdfa.bay.livefilestore.com/y1pUtb27sRH_ywbdnr5AhECI1yzRWRBTUEjEy6_-vRPGaLMpcjVWwjunvVbet5AgXX-Unm2LhlNZn5rnhGKUP3wht57UOuh17NU/advanced_wireless.JPG)
-
Kill the short GI and tell me if that helps.
-
I'll give it a shot after E3, and let you know in four days. Let you know though, if this is the cause, dlink will have to re-work how short GI works because it affects lan as well as wan, brings the router right down.
-
Just on the offchance you want more data... I have the same settings only with WMM Enabled checked and Short GI unchecked.
EDIT*** Just an update to the scorecard, one reboot and two wireless restarts in the log for today without any user input.
-
Just an FYI - I disabled DNS Relay 5 days ago and so far so good, and the router admin pages seem snappier than they were previously...knock on wood
-
So Lycan, is there anything to report besides that you can't reproduce it. Since both the 825 and 655 are experiencing this dns relay problem, have they been able to figure anything out?
-
I'm able to use it no problem, however I him our PM team about the possiblity that there is still an issue with the feature, they said they've been following the thread and are following a few possibilities.
I'm not really sure what that means, but I'll ask for clarification today.
-
Try this
http://forums.dlink.com/index.php?topic=5841.0
-
Any comments on 1.32beta working or not on DNS and freezing issuse?
-
Try this
http://forums.dlink.com/index.php?topic=5841.0
It's BETA code ! :D
-
LOL..I was trying to responed but router locked up :-\ as I was using bit torrent earlier. 1.31na
45 Log Entries: Priority Time Message
[INFO] Thu Jun 04 08:57:58 2009 Blocked incoming UDP packet from 89.134.21.233:49000 to xx.xx.xx.xx:65003
[INFO] Thu Jun 04 08:57:57 2009 Blocked incoming UDP packet from 88.171.94.154:42952 to xx.xx.xx.xx:65003
[INFO] Thu Jun 04 08:57:56 2009 Blocked incoming UDP packet from 115.64.141.79:10574 to xx.xx.xx.xx:65003
[INFO] Thu Jun 04 08:57:56 2009 Blocked incoming UDP packet from 70.181.148.160:53266 to xx.xx.xx.xx:65003
[INFO] Thu Jun 04 08:57:56 2009 Blocked incoming UDP packet from 76.106.46.77:39112 to xx.xx.xx.xx:65003
[INFO] Thu Jun 04 08:57:54 2009 Blocked incoming UDP packet from 121.6.206.140:10016 to xx.xx.xx.xx:65003
I've been watching the response on the 1.32beta topic and I do understand it's beta.
It's seems most responding was directed towards shareport issuse.
-
LOL..I was trying to responed but router locked up :-\ as I was using bit torrent earlier. 1.31na
45 Log Entries: Priority Time Message
[INFO] Thu Jun 04 08:57:58 2009 Blocked incoming UDP packet from 89.134.21.233:49000 to xx.xx.xx.xx:65003
[INFO] Thu Jun 04 08:57:57 2009 Blocked incoming UDP packet from 88.171.94.154:42952 to xx.xx.xx.xx:65003
[INFO] Thu Jun 04 08:57:56 2009 Blocked incoming UDP packet from 115.64.141.79:10574 to xx.xx.xx.xx:65003
[INFO] Thu Jun 04 08:57:56 2009 Blocked incoming UDP packet from 70.181.148.160:53266 to xx.xx.xx.xx:65003
[INFO] Thu Jun 04 08:57:56 2009 Blocked incoming UDP packet from 76.106.46.77:39112 to xx.xx.xx.xx:65003
[INFO] Thu Jun 04 08:57:54 2009 Blocked incoming UDP packet from 121.6.206.140:10016 to xx.xx.xx.xx:65003
I've been watching the response on the 1.32beta topic and I do understand it's beta.
It's seems most responding was directed towards shareport issuse.
[/size]
When I'm torrenting, the router will show similar logs, however utorrent connections work fine. The router in my case is doing it's job because it detects something funny with the tcp headers so it blocks the connection.
As well for lycans suggestion a few days ago about killing short-gi, I'll be able to tell late tonight or tomorrow since it will be the four day mark, after a couple resets from changing some settings.
-
When I'm torrenting, the router will show similar logs, however utorrent connections work fine. The router in my case is doing it's job because it detects something funny with the tcp headers so it blocks the connection.
As well for lycans suggestion a few days ago about killing short-gi, I'll be able to tell late tonight or tomorrow since it will be the four day mark, after a couple resets from changing some settings.
I'm @ a loss as to how short-gi would affect a hard wired connection as my understand it's a wireless setting. ???
-
It doesn't, but probably some of these issues may very well be non-router related ;D
-
Jason, this is where everything got confusing. Your post that I replied to, was posted in the wrong thread.
However, my reply had a reply to two different posts, to kill 2 birds with one stone. So i replied to your post my experience, as well, to lycans asking me to turn off short-gi. Again, its a work-around but not a fix and if work-arounds work, then dlink doesn't have to fix it.
-
Jason, this is where everything got confusing. Your post that I replied to, was posted in the wrong thread.
However, my reply had a reply to two different posts, to kill 2 birds with one stone. So i replied to your post my experience, as well, to lycans asking me to turn off short-gi. Again, its a work-around but not a fix and if work-arounds work, then dlink doesn't have to fix it.
LOL..no problem. I tried it anyway, no affect that I could tell.
-
@ Lycan. Disabling the short-gi had no effect. When I came home from work today/night, wireless was frozen solid. Still havn't figured out what it could be. Strange thing is, that on the wired computer, msn messenger was still logged in and able to be used but browsing the web, or trying to get to the web gui, failed. The router just seems to be blocking all web access. I dont know if it's blocking ports or not.
I'm still stumped as what could be causing it. Now, I can tell you that I've previously created access rules allowing only ports 80, 443, 53 and blocking all other access, but for the longest time I had evertything disabled. Trying to think out of the box here, when this freezing router happens, it's almost as if it's doing the reverse, it's enabling the access control, but reversing the allowed ports to blocked ports. I only say that because Windows Live Messenger was the only thing allowed to remain connected on the wired pc, but again, for some reason, the router would deny any wireless associations.
-
Did you already try what happens if you disable all access rules / schedules - just with all needed settings as encryption.
If it doesn't lock then, enable one rule after the other and try again.
-
Aside from wpa2 encryption and mac address filters, I have every single function disabled. I get the same "freezing" issue that others get along with some spontaneous reboots from time to time. As stated earlier in the thread through logs, the freezes always seem to be preceeded by various errors but the most common include IP Protcol 17, IP Protocol 6, and DNS Relay error. I'm not sure what those errors actually mean.
However I should also state that I have not tried out 132 beta. I need this router to work and prefer only to use final versions of firmware with the Dlink seal of approval.
-
My router freezes too, every couple of days.
Nothing changed from the days when it used to work fine, except the firmware - I made the mistake to update to the latest available.
I am puzzled by the inefficiency of Dlink support, considering that so many people have this problem after changing the firmware.
How could you possible release bad products without testing?
-
Some Linksys routers had a similar issue. The NAT table would hold dead links for something like five hours. DDWRT allowed you to change the release time. Setting it for 90 seconds fixed the freeze problem.
http://en.wikipedia.org/wiki/Linksys_WRT54G_series (http://en.wikipedia.org/wiki/Linksys_WRT54G_series)
Some performance issues have been encountered with the Linksys firmware which may cause sluggish or total network failure. This is usually caused by a large number of connections clogging the router, in other words NAT table overflow. Symptoms of NAT table overflow include inability to initiate new network connections while existing connections remain active. This is due to the small size of the NAT lookup table in default Linksys firmware coupled with a long table entry timeout. Installing a third-party firmware such as DD-WRT allows the user to change these values to prevent or delay NAT table overflow occurring. Installing a third party firmware and increasing the maximum ports setting to allow more connections is the usual solution (in DD-WRT found under Administration->Management->Maximum Ports).
http://www.ben.geek.nz/linksys-wrt54gl-router/ (http://www.ben.geek.nz/linksys-wrt54gl-router/)
The first thing I changed was the NAT table settings, increasing the table size from the default 512 to 4096, and dropping the NAT timeout from 3600 seconds to 90. In English this basically tells the router “store heaps of connection details, but discard them pretty sharpish if you don’t need them anymore”, which is exactly the behaviour we want with Bittorrent and other P2P apps.
A quick GOOGLE for DDWRT and NAT tables brings up things like this
http://www.overclock.net/networking-security/370371-router-nat-table.html (http://www.overclock.net/networking-security/370371-router-nat-table.html)
All the gigabit routers I have have very small NAT tables - even with under 100 connections the table fills up (so no more connections can be made)
http://www.dslreports.com/forum/r20073419-Small-NAT-table-a-thing-of-the-past (http://www.dslreports.com/forum/r20073419-Small-NAT-table-a-thing-of-the-past)
A NAT table is tiny in comparison to the amount of memory used for IP buffers, especially when jumbo frames are supported.
The AT has 29MB of memory, less than 1/2 of which is used. That is far more memory than is available in typical consumer routers such as LINKSYS.
Each NAT table entry requires about 16 bytes for IPV4 addresses. The NAT table in VZ's firmware allows 128 entries. That is 2KB of memory.
If 3rd party firmware where to increase the NAT table from 128 to 2000 entries, that would only be 32KB of memory.
http://www.broadbandreports.com/forum/r22361134-Will-Tomato-DDWRT-really-increase-speed-for-15-Mbps-line (http://www.broadbandreports.com/forum/r22361134-Will-Tomato-DDWRT-really-increase-speed-for-15-Mbps-line)
Number of open connections are whether the router's CPU gets bogged down or a full NAT table. Both will affect the router's performance but neither will make data transfers any faster.
The last quote suggests a slow CPU may be causing the freeze.
Disabling DHT may help.
The problem is files with large seeds/peers. Those seem to cause a freeze for me.
-
Its strange that disabling "DNS relay" isn't working for you guys. I haven't had a freeze in a while. I am still having issues where my connection seems to stop for a couple seconds, but no freezes.
-
Some Linksys routers had a similar issue. The NAT table would hold dead links for something like five hours. DDWRT allowed you to change the release time. Setting it for 90 seconds fixed the freeze problem.
http://en.wikipedia.org/wiki/Linksys_WRT54G_series (http://en.wikipedia.org/wiki/Linksys_WRT54G_series)http://www.ben.geek.nz/linksys-wrt54gl-router/ (http://www.ben.geek.nz/linksys-wrt54gl-router/)A quick GOOGLE for DDWRT and NAT tables brings up things like this
http://www.overclock.net/networking-security/370371-router-nat-table.html (http://www.overclock.net/networking-security/370371-router-nat-table.html)http://www.dslreports.com/forum/r20073419-Small-NAT-table-a-thing-of-the-past (http://www.dslreports.com/forum/r20073419-Small-NAT-table-a-thing-of-the-past)http://www.broadbandreports.com/forum/r22361134-Will-Tomato-DDWRT-really-increase-speed-for-15-Mbps-line (http://www.broadbandreports.com/forum/r22361134-Will-Tomato-DDWRT-really-increase-speed-for-15-Mbps-line)The last quote suggests a slow CPU may be causing the freeze.
Disabling DHT may help.
The problem is files with large seeds/peers. Those seem to cause a freeze for me.
Lycan: your thoughts on this post?
-
@lizzi555: As stated in the post, I have the options disabled for a long time. I only enable it when someone is torrenting like crazy, causing sluggish performance, since it's impossible to block torrent traffic any other way.
@mackworth: Although DNS relay is an option, a lot of people are not about to disable it. Disabling DNS Relay, defeats the purpose of an easy network "set and forget". It is not an acceptable solution to have to configure every device for a static DNS server, which in my case involves 6 laptops now, 2 Desktops, Xbox 360 and a PS3.
I don't think that disabling the function would solve the issue. I can see that it could be a work-around if the router was dropping only DNS traffic, but that's not the case here in my scenerio.
-
More on NAT table overflow ( Some of this is old news but does define the issue)
http://www.dslreports.com/forum/r21881646-Why-doesnt-everyone-have-the-NAT-problem (http://www.dslreports.com/forum/r21881646-Why-doesnt-everyone-have-the-NAT-problem)
When a PC behind your router makes a connection to a server on the internet, the router has to "remember" which connection from which PC the request came from, since you have only one external IP address, so that when the response comes back, it is routed to the same connection on the same PC. This information is kept in the "Network Address Translation" (NAT) table.
When the NAT table is full, the router can't remember any more connections and so appears to hang. The two primary culprits in filling the NAT table are torrents, and refreshing large server lists in gaming servers such as Steam.
http://forums.whirlpool.net.au/forum-replies-archive.cfm/403131.html (http://forums.whirlpool.net.au/forum-replies-archive.cfm/403131.html)
Actually, I find this encouraging to see that a D-Link router does log a message when the NAT table overflows.
I've seen behaviour recently which suggests to me that I have been losing NAT translations and I have suspected that the table may have filled up. This has only happened when there have been multiple computers running net games that involve peer to peer connections rather than just server connections.
However, someone else posted a message to the effect that an NAT entry only requires 160 bytes, ie every 1MB of router memory can hold over 6500 NAT entries, so it is hard to imagine it running out of memory, unless there is something else also using up the memory or the NAT table has a fixed size. I asked D-Link about this, but they reckoned it didn't. Not convinced they actually knew the answer one way or the other anyway.
[D-Link] D-Link DGL-4100
http://www.speedguide.net/broadband-view.php?hw=78 (http://www.speedguide.net/broadband-view.php?hw=78)
NAT table size: 8192
That is double what the LINKSYS mentioned before was changed to. Nothing on release time. If it is possible to change the release time, say to the previously mentioned 90 seconds, it should stop NAT table overflow.
NAT problems are not specific to the D-link.If this is the case. Google search has a couple of more listed and the posts I linked to tend to be other brands.
Frequent gaming seems to cause problems. That was mentioned above.
-
@lizzi555: As stated in the post, I have the options disabled for a long time. I only enable it when someone is torrenting like crazy, causing sluggish performance, since it's impossible to block torrent traffic any other way.
@mackworth: Although DNS relay is an option, a lot of people are not about to disable it. Disabling DNS Relay, defeats the purpose of an easy network "set and forget". It is not an acceptable solution to have to configure every device for a static DNS server, which in my case involves 6 laptops now, 2 Desktops, Xbox 360 and a PS3.
I don't think that disabling the function would solve the issue. I can see that it could be a work-around if the router was dropping only DNS traffic, but that's not the case here in my scenerio.
As noted in this thread earlier, if you turn of dns relay, you don't need to configure DNS manually. I have an xbox, 2 wired pcs, 5 laptops and an iphone. After I turned off DNS relay I didn't have to manually set DNS on any of them. The worst case scenario is that you just have to restart your computer. On my macbook, all I had to do was renew my DHCP.
Try disabling DNS relay. My router was working for months on 1.11. I upgraded to 1.31 and got the freezes. I turned off DNS relay and I haven't had a freeze since.
-
Guys
In my case, after more than ONE year of perfect functionality, my router started those freezing episodes AFTER I up graded to firmware 1.31
So may I respectfully suggest to the Dlink guys to investigate what/where is the DIFFERENCE between previous firmware and the latest.
All people on this forum indicated that they started to have their routers freeze, AFTER the upgrade.
It should be very simple in my opinion to discover where the problem is and fix it, by comparing the firmware versions.
All those advises from different users, disable this, enable that, etc will not resolve the issue.
Makes sense?
-
Guys
In my case, after more than ONE year of perfect functionality, my router started those freezing episodes AFTER I up graded to firmware 1.31
So may I respectfully suggest to the Dlink guys to investigate what/where is the DIFFERENCE between previous firmware and the latest.
All people on this forum indicated that they started to have their routers freeze, AFTER the upgrade.
It should be very simple in my opinion to discover where the problem is and fix it, by comparing the firmware versions.
All those advises from different users, disable this, enable that, etc will not resolve the issue.
Makes sense?
I think the Dlink guys are trying to enable options such as "shareport" and maybe others that the chipset of the router can handle but was never programed into the firmware in the beginning. Thats where the problems starts.
Go back yourself and look @ the different features offered from firmware release to firmware release. Everything started going to hell with 1.20-1.21. They started making changes as it seems without thinking or knowing it would affect another portion of the router, DNS relay, Upnp, shareport, etc....
Linksys and others are starting to offer the USB connection so in the spirit of competition we get to be the ginnie pigs.
Not that I really mind an improvement on the product I bought but someone really dropped the ball on this.
-
There are some kernel changes in 1.3x. But this should not make a difference. You might want to try to reflash and configure manually after flashing (not restoring the saved config).
-
There are some kernel changes in 1.3x. But this should not make a difference. You might want to try to reflash and configure manually after flashing (not restoring the saved config).
I did that already as many others have also to no effect. :-\
-
I am pretty convinced that no one is even reading this thread before they post. The same thing has been said over and over and over again.
-
There are some kernel changes in 1.3x. But this should not make a difference. You might want to try to reflash and configure manually after flashing (not restoring the saved config).
not sure if you remember, but DNS relay was broken as far back as 1.21 (the thread at the top of the forum). I think 1.30 was the official firmware that fixed it. I really wouldn't be surprised if their fix was just bad. Based on that I am guessing its not a problem with the switch to a newer Ubicom SDK but I could be wrong.
-
Beats me, but all works fine with DNS relay. Also with Enhanced DNS feature. So myst be a hardware revision issue.
-
Beats me, but all works fine with DNS relay. Also with Enhanced DNS feature. So myst be a hardware revision issue.
Except that people with different revisions are experiencing this problem. The only somewhat consistent things we know:
This problem started in 1.3+
The only solution that has worked for people with this issue is to turn off DNS relay
This problem also happens in firmware 1.11 of the DIR-825
This happens on all revisions
-
It's not only with 1.31.
I am using h/w A2 with f/w 1.22b05 (which has been removed from the ftp server). I should try downgrading to the firmware that didn't introduce shareport to see if the router hangs again. I am trying to remember when this problem begain, because I remember when I first got the router, this didn't start happening until I started upgrading the firmware. I wonder, as stated by one of the posters here, if the shareport feature is the culprit, although, I am not using the shareport feature because, well, yea, i'll just say that Fatman and I have the same thoughts about it.
-
It's not only with 1.31.
I am using h/w A2 with f/w 1.22b05 (which has been removed from the ftp server). I should try downgrading to the firmware that didn't introduce shareport to see if the router hangs again. I am trying to remember when this problem begain, because I remember when I first got the router, this didn't start happening until I started upgrading the firmware. I wonder, as stated by one of the posters here, if the shareport feature is the culprit, although, I am not using the shareport feature because, well, yea, i'll just say that Fatman and I have the same thoughts about it.
I meant officially released. It would make sense that 1.22b05 would have this issue since because this was the first firmware that introduced the DNS relay fix.
-
To be clear Torrent and gaming (possibly anything with many pc's web browsing) freeze may be caused by NAT table overflow. That does not mean every freeze with a router is caused by the overflow. Obviously there are a number of reasons including user error that may be the culprit. But based on my personal experience this looks to be the problem with my dir-655.
As I said I had a similar problem with a Linksys wrt54gl. Even after installing DDWRT it continued to happen. But raising the NAT table and lowering the release time solved it.
NAT table overflow is a common enough problem with routers.
-
To be clear Torrent and gaming (possibly anything with many pc's web browsing) freeze may be caused by NAT table overflow. That does not mean every freeze with a router is caused by the overflow. Obviously there are a number of reasons including user error that may be the culprit. But based on my personal experience this looks to be the problem with my dir-655.
As I said I had a similar problem with a Linksys wrt54gl. Even after installing DDWRT it continued to happen. But raising the NAT table and lowering the release time solved it.
NAT table overflow is a common enough problem with routers.
What about the issues with DNS Relay? How would the NAT overflow relate to turning of DNS relay?
-
http://www.dslreports.com/forum/remark,14316664 (http://www.dslreports.com/forum/remark,14316664)
On certain specific D-Link router models that I have experience with (and probably others) there are known problems with the DNS cache implementation.
The DSL-604+ has a DNS caching feature called 'Proxy DNS'. There is a known problem where the memory allocated to the cache fills with DNS name resolutions, causing the router to 'hang'. The solution (with official instructions published by D-Link) is to disable Proxy DNS and configure the router's DHCP server to hand out the IP addresses of the ISP's DNS servers directly.
This problem is also present on other router products based on the GlobespanVirata Helium communications processor running ATMOS (the DSL-500 and DSL-504) so whether it is an inherent problem with that version of ATMOS or with specific D-Link firmware routines I do not know.
The line of products is now at 'end of life' so I don't expect it to ever be properly fixed.
The DSL-G604T has a similar problem with its 'DNS Relay' feature - again, the solution is to disable it and hand out explicit DNS server addresses. The same problem is also present on other T-series router products. Since these are based on embedded Linux running on the MIPS cpu within the TI AR7 communications processor, I suspect it's not an inherent problem, but a configuration issue.
This line of products is current, so if it's a configuration issue it will probably be fixed in later firmware. But there are already fairly tight memory constraints (see later) and the latest firmware with ADSL2+ support and additional features only makes the constraints worse...
In all cases I suspect the underlying cause is lack of physical memory. There is insufficient RAM available to allocate to a large cache, and also insufficient memory to run comprehensive error checking code with proper bounds checking and techniques such as the use of 'high water marks' so that cache entries are discarded as memory fills.
Let me rephrase that: the underlying cause is that these devices are designed and built to a very tight budget, and memory and other component counts are reduced to the absolute minimum to keep the cost down.
As far as performance improvement is concerned, successful DNS caching may shave 1 or 2 ms off a DNS request.
Sounds a lot like NAT table overflow.
http://www.dslreports.com/faq/11909 (http://www.dslreports.com/faq/11909)
How can I prevent problems when using eMule P2P software? (#11909)
There are several issues that might occur when using eMule P2P software and some routers (including some D-Link routers). Although we have seen several firmware releases that attempt to address eMule problems, they seem to persist and become frequent issues in the forum.
The most frequent behaviors related to overloading are spontaneous reboots, gradually reduced performance, or a non-responsive router:
•When KAD is used, the NAT table overflows and the router reboots. While some users have reported various improvements using various firmware versions, there is no certain cure except for not using KAD.
•Under normal use, the router slows, locks, or reboots. You may turn off the router's DNS Relay feature, which on later firmware versions is located on the "Home / LAN" configuration page.
•When there are hundreds of connections, the router slows or reboots. You may configure eMule to maintain fewer simultaneous connections.
DSLReports treats the problem as two separate issues. If DNS relay has a slow release time that may be what causes the problem. Either way the descriptions of NAT Table Overflow and DNS Relay caching filling with DNS resolutions on the surface look to be of similar nature.
http://www.broadbandreports.com/forum/remark,12342091~start=20 (http://www.broadbandreports.com/forum/remark,12342091~start=20)
KAD works by using UDP to transfer eMule information instead of TCP connections.
When the connections are TCP, the NAT table can open, track, and close the connection -- even if there are many of them simultaneously.
However, UDP is connectionless. The NAT table basically has to hold the entry for a while and then close it after some (undetermined) timeout. The timeout has to be long enough to avoid shutting down active communication. There is no way to know when communication is over.
As a consequence, it seems that the NAT table just builds and overflows with open UDP entries coming from everywhere.
There are many routers that exhibit this behavior, and many that do not -- and, no, I don't know the solution. But after reading up on this problem today, I thought I'd share what I've learned.
--
If this is true then UDP is the culprit.
Then again
http://www.broadbandreports.com/forum/remark,12342091~start=40 (http://www.broadbandreports.com/forum/remark,12342091~start=40)
The story goes that since UDP is connectionless, the NAT table fills up and each of these UDP connections has to time out.
I'm beginning to have my doubts about that theory. Scree's handy NATLIST.TXT reader / Connection Monitor is showing me that some TCP connections actually hang around in the NATLIST longer than the UDP connections.
http://www.broadbandreports.com/forum/remark,12342091~start=60 (http://www.broadbandreports.com/forum/remark,12342091~start=60)
Yep, I think the UDP theory is difficult to accept. I also found (not using eMule, but with other connections) that the NAT table does not hold UDP connections for a long time nor does it accumulate to anywhere close to maximum.
http://www.broadbandreports.com/forum/remark,12342091~start=60 (http://www.broadbandreports.com/forum/remark,12342091~start=60)
Sounds like there might be a solution in finding some way to reduce the amount of time that the router 'holds' onto a UDP connection. This thread has a bit to say about this - »forum.emule-project.net/lofivers···687.html - but my DI-624+ doesn't have this option. Sounds like firmware update time with a few new options.
Back to release time changing is a fix.
Someone made a D-link connection monitor.
http://www.broadbandreports.com/forum/remark,12608281 (http://www.broadbandreports.com/forum/remark,12608281)
-
That sounds like a different issue, an issue with DNS cache versus the nat table.
AFAIK although no final word has been given, the DNS relay in the dir-655 doesn't have caching. I am still convinced the issue has to do with their "fix" for DNS relay. If this same problem happened on 1.22B05 as reported on the page before, it makes all the sense since this is the (released/unreleased)first version that they had the fix.
-
That sounds like a different issue, an issue with DNS cache versus the nat table.
AFAIK although no final word has been given, the DNS relay in the dir-655 doesn't have caching. I am still convinced the issue has to do with their "fix" for DNS relay. If this same problem happened on 1.22B05 as reported on the page before, it makes all the sense since this is the (released/unreleased)first version that they had the fix.
No. It looks like both have excessive release times. Lowering that should stop the problem.
-
The 1.32 beta does not fix this problem, just in case anyone was curious.
I really wish I could downgrade to 1.21, because, though it had some bugs, at least it could stay up for more than a few days.
-
The 1.32 beta does not fix this problem, just in case anyone was curious.
I really wish I could downgrade to 1.21, because, though it had some bugs, at least it could stay up for more than a few days.
I'm not crashing that frequently. I do crash when there are lots of seeds/peers, or when there is some strange combination of tweaked Firefox and Utorrent.
As I said I've seen similar crashes with my Linksys router.
I'm assuming in your case it is something else.
Do you have anything listed in Event viewer? Is your OS up to date? Have you modified your services and "tweaked" the os?
I see a lot of posts here blaming the firmware but relatively few state what hardware is running/what os and updates are running/if registry has been modified/if a firewall is operating/what antivirus and antispyware is running/what activities happened just before the crash and if duplicating those creates another crash. Basically I see very little regarding user error.
With the case of NAT overflow I'm only familiar because it has happened to me before. So when it happens now I know what application or combination causes it.
If it happens randomly I would then remove everything and slowly start adding first to a single pc, if that works fine I would follow the same procedure with others. You need to eliminate any possible potential conflict to find a solution.
DNS relay and NAT table overflow seem to have the same cause with overlong release time. There is no setting to change that.
I may be wrong.
Still it is always best to start with user error as the first cause. Once that is ruled out, and user error covers every aspect of incompatibility with both hardware and software not just incompetence, then move onto other areas. I've had cards and devices that play well with one pc but not another. I've had av .dlls block net access after the software had been removed and they remained hidden. Only the slow and steady approach of eliminating each and every foreseeable device/service/driver lead to a fix.
Sure it takes hours or days or even weeks to sort out any failure/incompatibility. Sure it is a pain in the ass. But it is the only way to be absolutely certain.
-
I have a ton of stuff on my network, so it's really hard to troubleshoot what the problem might be if something on my network is causing problems with the router (2 Vista laptops, 2 XP laptops, 2 Vista desktops, 1 XP desktop, 1 Windows Home Server, 2 Vonage boxes and one each of a TiVo, PS3, Wii, HD-DVD player, Slingbox, and a LAN printer). I simply can't disconnect all of those but one device for testing purposes, especially not for the entirety of the few days the router stays up at a time without freezing, first of all I work from home and need at least two PCs and the Vonage boxes at all times.
However, the router worked (mostly) fine with the older firmware. I haven't tried disabling DNS relay, which I am going to do, but I shouldn't have to. It should just work. The only settings I've changed from the defaults are changing the SSID and enabling WPA2 security. This router has easily been the most problematic that I've owned (and there have been several), but I've put up with it because of the excellent QoS features and performance. I've been hoping that something will come along from a company other than D-Link with similar capabilities, but not yet.
-
I'm going to go sifting through the code once more to see if there is a NAT table that is hidden somewhere that can be accesses vie the web gui.
-
I'm not crashing that frequently. I do crash when there are lots of seeds/peers, or when there is some strange combination of tweaked Firefox and Utorrent.
As I said I've seen similar crashes with my Linksys router.
I'm assuming in your case it is something else.
Do you have anything listed in Event viewer? Is your OS up to date? Have you modified your services and "tweaked" the os?
I see a lot of posts here blaming the firmware but relatively few state what hardware is running/what os and updates are running/if registry has been modified/if a firewall is operating/what antivirus and antispyware is running/what activities happened just before the crash and if duplicating those creates another crash. Basically I see very little regarding user error.
With the case of NAT overflow I'm only familiar because it has happened to me before. So when it happens now I know what application or combination causes it.
If it happens randomly I would then remove everything and slowly start adding first to a single pc, if that works fine I would follow the same procedure with others. You need to eliminate any possible potential conflict to find a solution.
DNS relay and NAT table overflow seem to have the same cause with overlong release time. There is no setting to change that.
I may be wrong.
Still it is always best to start with user error as the first cause. Once that is ruled out, and user error covers every aspect of incompatibility with both hardware and software not just incompetence, then move onto other areas. I've had cards and devices that play well with one pc but not another. I've had av .dlls block net access after the software had been removed and they remained hidden. Only the slow and steady approach of eliminating each and every foreseeable device/service/driver lead to a fix.
Sure it takes hours or days or even weeks to sort out any failure/incompatibility. Sure it is a pain in the ass. But it is the only way to be absolutely certain.
People are blaming the firmware because this issue didn't occur with 1.21 and started in 1.22B05 and 1.31. Both of these releases fix an issue with "DNS Slowdown" that was in 1.21 and subsequently fixed in 1.22B05. Thats why 1.22B05 was released, to fix DNS relay as I remember. It makes that this fix was bad since if you turn off DNS relay, it works correctly.
And since DNS relay isn't caching (as far as I know), there is no point in using it. Yes you shouldn't have to turn it off to get a working router, but you also aren't gaining anything either by having it on.
Why everyone isn't hitting this issue, I have no idea. But I do know a lot of people are. If we look at what we know:
This problem started in 1.22B05
The only solution that has worked for people with this issue is to turn off DNS relay
This problem also happens in firmware 1.11 of the DIR-825
This happens on all revisions
So we can come up with all the issues we think it is, Nat overflow, DNS caching, but only dlink has the source code unfortunately. As a software engineer, I would love to look at it myself, but we can't.
-
However, the router worked (mostly) fine with the older firmware. I haven't tried disabling DNS relay, which I am going to do, but I shouldn't have to. It should just work. The only settings I've changed from the defaults are changing the SSID and enabling WPA2 security. This router has easily been the most problematic that I've owned (and there have been several), but I've put up with it because of the excellent QoS features and performance. I've been hoping that something will come along from a company other than D-Link with similar capabilities, but not yet.
Why should it just work? That is a dangerous assumption. I remember XP updates that would screw the system.
Things have bugs.
I've also has issues with security. I keep it off and go with invisible ssid. Security will slow down a connection. I may play with MAC filtering to only allow a limited amount of devices.
"And since DNS relay isn't caching (as far as I know)"
Why would it not?
http://www.dslreports.com/forum/r22013702-Help-Me-DIR655-DNS-Relay (http://www.dslreports.com/forum/r22013702-Help-Me-DIR655-DNS-Relay)
When you have the DNS Relay option enabled, the router acts as a DNS caching server; meaning instead of all DNS requests being sent straight to your ISP, the router makes the request on your behalf and than caches the response it received from the ISP. When you go to the same website you accessed before it doesn't have to contact the IPS dns server because it already has the information in its cache, making DNS resolution faster.
Has anyone tried keeping DNS relay on but turning off DNS cache in the os?
-
"And since DNS relay isn't caching (as far as I know)"
Why would it not?
There was a thread here a couple weaks ago and someone said that it wasn't caching. The documentation isn't clear but it doesn't mention caching. I had assumed that this was true since dlink had replaced the name of its DNS Cache feature to DNSRelay in its new models.
I could be wrong, but the points above still holds true.
-
There was a thread here a couple weaks ago and someone said that it wasn't caching. The documentation isn't clear but it doesn't mention caching. I had assumed that this was true since dlink had replaced the name of its DNS Cache feature to DNSRelay in its new models.
I could be wrong, but the points above still holds true.
Can confim that it does no caching what so ever. It does exectly what it's name says: relaying DNS
-
There was a thread here a couple weaks ago and someone said that it wasn't caching. The documentation isn't clear but it doesn't mention caching. I had assumed that this was true since dlink had replaced the name of its DNS Cache feature to DNSRelay in its new models.
I could be wrong, but the points above still holds true.
So does the fact that it may not be releasing fast enough.
D-link doesn't look to be responding. Others think it caches. Just because D-link changed the term doesn't mean it doesn't cache. Enhanced Interrogation technique is still Torture despite the fancy name.
Right now it doesn't seem to work. Turn it off. If D-link screwed it up they should simply remove it.
But even with it off I still occasionally get what looks to be NAT overflow.
DNS relay is not the cause of that.
If we had access to NAT settings we could experiment and see if it solves the problem.
Instead I have to reboot.
Or maybe it interferes with the OS DNS cache service. I had an XP machine I had to keep the service off on otherwise it would freeze my net access.
This thread keeps repeating the same accusations with no new information or perspective. If someone can explain just why the router freezes, weak cpu and memory for example, or why DNS relay fails maybe then it becomes a cornerstone to work from.
My assumption is release times are screwed up or NAT table isn't large enough most likely both. When D-link disproves that and offers their own explanation I may move on. But I don't really trust any company to be honest about defects in their product.
-
Can confim that it does no caching what so ever. It does exectly what it's name says: relaying DNS
Ok, how?
Are you a D-link employee? If so why change the service title from "cache" to "relay"?
Did D-link merely turn off the cache? Wouldn't that create other issues?
Not trying to be rude but owning this router and upgrading firmware entitles me to ask those questions. And everyone should ask as many and as thorough questions as possible.
Thanks.
-
No, I'm not from Dlink. Do you see a Dlink sign next to my name like all other Dlink techs have?
Because 'somewhere' in this forum Lycan has already confirmed that it doesn't do caching. regarding your other inquisits: do you want to validate the validation of the validation? Do you want tot know what colour underwear the programmer wore that day?
If you want to talk bits, bytes and code you're in the wrong place, even the Dlink moderators are not the coders.
-
No, I'm not from Dlink. Do you see a Dlink sign next to my name like all other Dlink techs have?
Because 'somewhere' in this forum Lycan has already confirmed that it doesn't do caching. regarding your other inquisits: do you want to validate the validation of the validation? Do you want tot know what colour underwear the programmer wore that day?
If you want to talk bits, bytes and code you're in the wrong place, even the Dlink moderators are not the coders.
So this forum is essentially useless with an uneducated D-link flack answering posts whenever he feels like it?
Then what is the point of any questions being posted here? Just to piss and moan?
That strikes me as useless.
And if I understand the history DNS RELAY was once DNS CACHE, then it got name changed. Then the D-Link employee claimed there is no caching. No reason was stated for the change. No information was given about how caching turned into relay. Nothing tangible except some employees talking points.
Does that sum it up?
And best of all the D-Link working slob has no idea about coding.
Strikes me as Pat Robertson being an expert on Homosexual Witchcraft.
Anyway if there are no specific answers from the company then why should anyone post ever?
-
So this forum is essentially useless with an uneducated D-link flack answering posts whenever he feels like it?
Then what is the point of any questions being posted here? Just to piss and moan?
That strikes me as useless.
And if I understand the history DNS RELAY was once DNS CACHE, then it got name changed. Then the D-Link employee claimed there is no caching. No reason was stated for the change. No information was given about how caching turned into relay. Nothing tangible except some employees talking points.
Does that sum it up?
And best of all the D-Link working slob has no idea about coding.
Strikes me as Pat Robertson being an expert on Homosexual Witchcraft.
Anyway if there are no specific answers from the company then why should anyone post ever?
Just be clear, I am not saying this router ever had something called DNS Caching. I merely meant that I was pretty sure that previous D-link models had it. But now, the 655 and 825 have something called DNS relay.
BTW, there are employees that post here and they are as helpful as they can be. They just seem to be MIA at the moment.
-
So does the fact that it may not be releasing fast enough.
D-link doesn't look to be responding. Others think it caches. Just because D-link changed the term doesn't mean it doesn't cache. Enhanced Interrogation technique is still Torture despite the fancy name.
Right now it doesn't seem to work. Turn it off. If D-link screwed it up they should simply remove it.
But even with it off I still occasionally get what looks to be NAT overflow.
DNS relay is not the cause of that.
If we had access to NAT settings we could experiment and see if it solves the problem.
Instead I have to reboot.
Or maybe it interferes with the OS DNS cache service. I had an XP machine I had to keep the service off on otherwise it would freeze my net access.
This thread keeps repeating the same accusations with no new information or perspective. If someone can explain just why the router freezes, weak cpu and memory for example, or why DNS relay fails maybe then it becomes a cornerstone to work from.
My assumption is release times are screwed up or NAT table isn't large enough most likely both. When D-link disproves that and offers their own explanation I may move on. But I don't really trust any company to be honest about defects in their product.
Basically my point is that this thread is about a specific issue, if you read it from the beginning. This issue is somehow DNS relay related which was first mentioned on page 4. If you think you have another issue when DNS relay is turned off and NAT overflow, then please start a new thread.
-
Just be clear, I am not saying this router ever had something called DNS Caching. I merely meant that I was pretty sure that previous D-link models had it. But now, the 655 and 825 have something called DNS relay.
BTW, there are employees that post here and they are as helpful as they can be. They just seem to be MIA at the moment.
First. Other sources, reliable trustworthy third party sources, claimed that DNS relay was cached.
Second. Helpful and informed are two different things. C'mon they are company men. Look at the whole Nvidia gpu fiasco and how to avoid recall solutions were to stretch serviceability to beyond warranty.
Third. No one knows just what is the problem, can you point to any employee post stating exactly the source and solution?
My choices for source of problem are either slow release time, small NAT table, or deficient cpu/memory.
The first two can be addressed in a firmware update allowing us to change NAT table size and release time for both NAT table and DNS caching. If it is cpu/memory then the product is not capable of fully applying itself to optimal usage and specific operating parameters should be offered so that capacity may be realized and not exceeded.
Anyone else have any ideas?
Please share them and hope someone from D-link corrects our errors in assumption if not judgment.
-
Basically my point is that this thread is about a specific issue, if you read it from the beginning. This issue is somehow DNS relay related which was first mentioned on page 4. If you think you have another issue when DNS relay is turned off and NAT overflow, then please start a new thread.
Can you prove that NAT table overflow is NOT the source of the problem?
Do you have any idea what the source is?
Please share with the class.
-
Can you prove that NAT table overflow is NOT the source of the problem?
Do you have any idea what the source is?
Please share with the class.
Thats the whole point. You can't prove its the nat table so stop trying to make it sound like you know what you are talking about. All we know is this:
This problem started in 1.22B05 which fixed an issue with DNS relay
The only solution that has worked for people with this issue is to turn off DNS relay
This problem also happens in firmware 1.11 of the DIR-825
This happens on all revisions
So based on the part 1 and 2, I am just saying it probably has something to do dns relay. I am not basing my argument on bs, I just saying that it makes sense the issue is dns relay related. get it?
-
First. Other sources, reliable trustworthy third party sources, claimed that DNS relay was cached.
Second. Helpful and informed are two different things. C'mon they are company men. Look at the whole Nvidia gpu fiasco and how to avoid recall solutions were to stretch serviceability to beyond warranty.
Third. No one knows just what is the problem, can you point to any employee post stating exactly the source and solution?
My choices for source of problem are either slow release time, small NAT table, or deficient cpu/memory.
The first two can be addressed in a firmware update allowing us to change NAT table size and release time for both NAT table and DNS caching. If it is cpu/memory then the product is not capable of fully applying itself to optimal usage and specific operating parameters should be offered so that capacity may be realized and not exceeded.
Anyone else have any ideas?
Please share them and hope someone from D-link corrects our errors in assumption if not judgment.
I checked those links you posted, maybe I missed something, but I didn't see anything anywhere that said the dir-655 has or had ever had dns caching. There was one guy that posted a generic definition of dns relay that mentioned caching but he offered no proof. All I am saying if that it was discussed here before and it was decided that it didn't and documentation doesn;t mention caching at all, although I think i checked documentation for an old dlink router that specifically mentioned that it did have caching, leading me to believe if they left it out of the 655 docs, that it doesn;t have it.
I am not saying I know everything, I just making conclusions based on evidence presented in this forum, not posts from dslreports about completely different routers. Dlink has already said they can not reproduce it. I am just trying to share the one solution that has worked for people.
-
So this forum is essentially useless with an uneducated D-link flack answering posts whenever he feels like it? Then what is the point of any questions being posted here? Just to piss and moan?
That strikes me as useless.
Did I say uneducated? I merely said they are not product management, not coders and not VP's of Dlink. Your question tend to sound like "i'd like to speak to the manager".
And if I understand the history DNS RELAY was once DNS CACHE, then it got name changed. Then the D-Link employee claimed there is no caching. No reason was stated for the change. No information was given about how caching turned into relay. Nothing tangible except some employees talking points.
Does that sum it up?
How about: they changes the name because "DNS caching" gave the wrong impression to users since there was no caching at all? Or is there a conspiracy behind this?
And best of all the D-Link working slob has no idea about coding.
Strikes me as Pat Robertson being an expert on Homosexual Witchcraft.
Anyway if there are no specific answers from the company then why should anyone post ever?
You haven't paid much attention to the board ...
-
Demonized, just why are you defending the company?
You own stock?
You dating the bosses daughter?
Or do you think they care about you other than to rake in your cash?
Really why would anyone defend a company that offers half fixed updates? Or half broken depending on how you look at it.
Oh and since the CODING guys you mentioned earlier would know the difference between CACHING and RELAYING you can bet that CACHING was and possibly still is in use.
Mackdaddy, the forum was specific to the DIR-655 and DSLREPORTS is about as reliable as they come.
Maybe you should read more carefully, it could be the source of your misunderstanding.
What you missed.
[Help Me] DIR-655 DNS Relay
I'll ask again: What do either of you consider to be the problem with the router? Not just the nebulous DNS relay, but WHY the DNS relay causes the freeze. Why the router will freeze even with DNS relay off?
Surely you must have some opinion, theory or best guess.
What is it?
I've been clear about mine.
Or is it simpler just to attack me and not offer a substantial alternative?
-
Demonized, just why are you defending the company?
You own stock?
You dating the bosses daughter?
Or do you think they care about you other than to rake in your cash?
Really why would anyone defend a company that offers half fixed updates? Or half broken depending on how you look at it.
Oh and since the CODING guys you mentioned earlier would know the difference between CACHING and RELAYING you can bet that CACHING was and possibly still is in use.
Mackdaddy, the forum was specific to the DIR-655 and DSLREPORTS is about as reliable as they come.
Maybe you should read more carefully, it could be the source of your misunderstanding.
What you missed.
[Help Me] DIR-655 DNS Relay
I'll ask again: What do either of you consider to be the problem with the router? Not just the nebulous DNS relay, but WHY the DNS relay causes the freeze. Why the router will freeze even with DNS relay off?
Surely you must have some opinion, theory or best guess.
What is it?
I've been clear about mine.
Or is it simpler just to attack me and not offer a substantial alternative?
I am not attacking you, I am just trying to explain to you that this thread started as an issue with freezing that occuring after users updated to 1.31. Those users (including me) found that disabling DNS relay fixed our issue with freezing. So why are you fighting this?
If you router is still freezing wit DNS relay off, then its not this issue and you should start a new thread explaining what your exact issue it and maybe people can help you. That way when people come here looking for answers, they don't have to read through 14 pages of results just to find out that turning off DNS Relay probably fixes their issue.
And dslreports is reliable as they come? I lurk there from time to time, and I see people still telling other users to use the 30/30/30 trick when flashing which dlink has already said doesn't do anything. Does that make dslreports unreliable? No, it just means that people there don't know anymore about anything than we do. And only one of your link (as far as I can see) was even specific to the DIR-655 and how do we know that one person that said it had caching even knew what he was talking about? Maybe he just assumed it had it?
-
I don't understand why you're spending such an effort on the DNS Relay's function.
You won't recognize a difference in speed, no matter whether it is relaying, caching or disabled.
The only real advantage of this function: It is easier to configure devices with static ip addresses.
You only need to enter the IP of your router as DNS server and don't have to care about the DNS addresses of your internet provider and whether they may change sometime in the future.
So it is only a comfort and not a performance feature.
(Not 100% - if you use complex measuring instruments you will find one or the other millisecond, which you saved at searching ;) )
-
Mackdaddy has no explanation, theory or guess as to what the source of the problems might be. But he still chooses to post. Is that useless or what? Why just regurgitate that there is a problem and never attempt to define that problem?
Is there a block function here? Now that I understand his posts are pointless I don't want to see them anymore. Why should I waste my time for tired old repetitious "I know nothing but you are wrong" posts?
Meanwhile new firmware is out.
I wonder if the release times are set properly and the NAT table increased?
-
GullyFoyle,
Let's just try and be a civilised guy and respects someone else's opinion without trying to ridicule them. Your assumptions have no solid basis and apparently you're not able to bring up some proof of your assumptions. Ask your "third party source" for more info if you really want to play with the big boys ;)
-
GullyFoyle,
Let's just try and be a civilised guy and respects someone else's opinion without trying to ridicule them. Your assumptions have no solid basis and apparently you're not able to bring up some proof of your assumptions. Ask your "third party source" for more info if you really want to play with the big boys ;)
So you can't answer the question either? No theory, best guess or attempted scrying.
Maybe you can tell me how to block you and Mackdaddy.
From your other answers, here and other topics, you seem to not have a solution for anything. John Lennon said you are either part of the solution or part of the problem.
I don't want to waste my precious time reading blah/blah/blah posts by part of the problem.
Unlike you I'm here for answers regarding a product I spent hard earned money for.
-
Your theories are unsubstantiated and sound more like guessing.
If you are setting a new rule that only people with answers are allowed to answer your questions...well, bad luck for you, that's not the way it works in this world. And you don't want to be called a troll surely?
-
So you can't answer the question either? No theory, best guess or attempted scrying.
Maybe you can tell me how to block you and Mackdaddy.
From your other answers, here and other topics, you seem to not have a solution for anything. John Lennon said you are either part of the solution or part of the problem.
I don't want to waste my precious time reading blah/blah/blah posts by part of the problem.
Unlike you I'm here for answers regarding a product I spent hard earned money for.
I gave you guess based on the evidence. Their fix for DNS relay that they introduced in 1.22B05 (the first firmware where people had this problem) was bad and its causing this freezing issue. What else do I need to guess? What would be the point of being going any further than this? I am a software engineer and thats the best guess I am willing to make without actually looking at the code, its a regression.
What you are doing is like if I told you I had a stuffy nose and I am sneezing, and then you went on webmd.com and started telling me all these illnesses that I might have, when you have no qualification to make those statements.
-
I gave you guess based on the evidence. Their fix for DNS relay that they introduced in 1.22B05 (the first firmware where people had this problem) was bad and its causing this freezing issue. What else do I need to guess? What would be the point of being going any further than this? I am a software engineer and thats the best guess I am willing to make without actually looking at the code, its a regression.
What you are doing is like if I told you I had a stuffy nose and I am sneezing, and then you went on webmd.com and started telling me all these illnesses that I might have, when you have no qualification to make those statements.
kudos
-
If DNS relay is causing your router to lock up and require a reboot, then you should seek a replacement asap. If you've already had a replacement for that same issue, let the technician know that and they will get you a brand new one and test it for you.
If you receive a brandnew replacement that claims to be tested and it continues this behavior let me know and I'll personally address the situation.
Please refrain from antagonistic behavior and "trolling". These forums are here for you to receive help and share information with the comunity. They are here for everyone to use respectfully.
-Lycan.
Also there is NO DNS caching being done by the router. The unit only has 16MB of ram and thats 100% used by statetable/configurations.
-
If DNS relay is causing your router to lock up and require a reboot, then you should seek a replacement asap. If you've already had a replacement for that same issue, let the technician know that and they will get you a brand new one and test it for you.
If you receive a brandnew replacement that claims to be tested and it continues this behavior let me know and I'll personally address the situation.
Please refrain from antagonistic behavior and "trolling". These forums are here for you to receive help and share information with the comunity. They are here for everyone to use respectfully.
-Lycan.
Also there is NO DNS caching being done by the router. The unit only has 16MB of ram and thats 100% used by statetable/configurations.
So Lycan, is that D-Link's official response, that this is hardware related? It isn't related to the fix introduced for DNS relay that first appeared in 1.22B05 where this issue was first encountered? Not to mention this problem is happening with the 825 in 1.10 also?
I already have a new outer in the 825 (haven't upgraded past 1.01). What about people that had this issue caused by 1.31 but are past the 1 year mark for a warranty?
-
The issue is this isn't a firmware problem globally, for some reason it only effects a small percentage of routers. I'm not trying in anyway to discount your issues. Trust me if I had the answer I'd gladly give it, but I don't. We're unable to reproduce the failing, and the units that we get back here don't exhibit the issue once they're tested in our labs.
The 655 is sold more then any other N router from D-Link. If this was a global issue we'd be seeing a lot more of this.
-
The issue is this isn't a firmware problem globally, for some reason it only effects a small percentage of routers. I'm not trying in anyway to discount your issues. Trust me if I had the answer I'd gladly give it, but I don't. We're unable to reproduce the failing, and the units that we get back here don't exhibit the issue once they're tested in our labs.
The 655 is sold more then any other N router from D-Link. If this was a global issue we'd be seeing a lot more of this.
I am not discounting that it could be a local issue, although I don't think that means it isn't firmware related. It just seems that there are too many coincidences here to not be firmware related. Considering this didn't happen in earlier firmwares (I ran a long long long time without freezes on 1.11 and 1.21, but had the DNS slowdown issue with 1.21), it also happens on the 825 with firmware 1.11, this was introduced in firmware that "fixed" issues with the very feature that is now causing crashes, etc.
Trust me, I understand where you are coming from, I have worked on some cases before where I wasn't able to reproduce something but was able to come to a solution via methods I don't think translate over to a router. And as I mentioned, I already have a 825 running 1.01 as my main router with no issues (no Freezes!) so I am more looking out for other users that don't feel like plunking down the money.
-
Also there is NO DNS caching being done by the router. The unit only has 16MB of ram and thats 100% used by statetable/configurations.
There are some people that want you to take a polygraph test for that ;)
-
The issue is this isn't a firmware problem globally, for some reason it only effects a small percentage of routers. I'm not trying in anyway to discount your issues. Trust me if I had the answer I'd gladly give it, but I don't. We're unable to reproduce the failing, and the units that we get back here don't exhibit the issue once they're tested in our labs.
The 655 is sold more then any other N router from D-Link. If this was a global issue we'd be seeing a lot more of this.
So which is it hardware or firmware and which are affected the most A1/A2 or A3/A4?
-
I'm pretty sure your statement should be rephrased. You make it seem like it's a small problem that only effects a small number of people.
Dlink only knows about the problem from people reporting it. So really, it's not that the problem only affects a small number of devices, but only a small number of people have reported it
-
If DNS relay is causing your router to lock up and require a reboot, then you should seek a replacement asap. If you've already had a replacement for that same issue, let the technician know that and they will get you a brand new one and test it for you.
If you receive a brandnew replacement that claims to be tested and it continues this behavior let me know and I'll personally address the situation.
Please refrain from antagonistic behavior and "trolling". These forums are here for you to receive help and share information with the comunity. They are here for everyone to use respectfully.
-Lycan.
Also there is NO DNS caching being done by the router. The unit only has 16MB of ram and thats 100% used by statetable/configurations.
Well there is the issue of Dlink customers upgrading their firmware to take full advantage of what Dlink products have to offer only to have problems with the chipset or firmware of the router not working correctly.
What now, are the customers just hung out to dry?
I really like the Dir 655 and Dlink in general and I not looking for something for nothing but I never had any issue til I upgraded past fw1.11 and since I can't go back I feel I along with others got a raw deal.
-
I'm pretty sure your statement should be rephrased. You make it seem like it's a small problem that only effects a small number of people.
Dlink only knows about the problem from people reporting it. So really, it's not that the problem only affects a small number of devices, but only a small number of people have reported it
I think your right, a small number of people come here to try to find the ansewer. LoL...customer service @ ISP's I'm sure have been getting hammered with questions.
-
I'm pretty sure your statement should be rephrased. You make it seem like it's a small problem that only effects a small number of people.
Dlink only knows about the problem from people reporting it. So really, it's not that the problem only affects a small number of devices, but only a small number of people have reported it
From a argumentative point of view that's not completely valid and factual. If you believe it's a fundamental issue (which from Lycan's words and experience with RMA'd devices it apparently isn't) you assume that there a tons of people who do not reported a seriously malfunctioning device. That sounds more like wishful thinking. The forum is not the only source (it's just the least reliable source IMHO): retailers get all the RMA requests which do not go through the forum but directly to Dlink labs. And if you participate on a forum: there's only questions and issues/problems on these boards, nobody goes to a forum to praise a product they just bought.
Your starting point is that there really is a serious issue but the numbers don't add up to that. It's like believing in extraterrestrial live. There are there but we just haven't seen them yet ;)
-
Lets say D-link sells 100000, units a year. Then take that an times it by the products lifetime of 2+ years.
Now look at the volume of failures that are specific to this ( not including hardware failure or misuse that results in a replacement that corrects the issue) and I can assure you that it's >1%.
Again, I'm not trying to in anyway discount the failures you guys are having, I'm simply trying to help everyone keep this in perspective.
We are working to correct this as quickly as possible.
Forums and Customer Service is where people go when there are problems with their products, this can make the issue seem much worse then it actaully is on a global scale.
Just a little FYI.
That being said, I'm working with the PM team to resolve any issues with this unit esp. the ones with shareport.
-
Well I think a more accurate projection would be tallying up all the units dlink has sold. of all the reivisions.
subtract the h/w a1 units
of the remaining unites, take seventy percent or so away due to the fact that its likely that number doesn't bother upgrading their routers firmware because they have no knowledge and are too timid to do so because they dont' want something to go wrong. The remaining 30 percent, than is a more accurate plausability than your less than one percent. :P This is why playing percentages is always shady.
Out of that 30 percent, then have upgraded their routers to 1.2+ ? Now you can summerize that it is indeed firmware related.
I can atess to that since I never encountered this problem before upgrading the f/w. As well never reported it until when I did because I didn't catch on to the trend and thought it was just someone torrenting.
However, i'm still tryign to find something in common with this 4/5 day router freeze
-
From a argumentative point of view that's not completely valid and factual. If you believe it's a fundamental issue (which from Lycan's words and experience with RMA'd devices it apparently isn't) you assume that there a tons of people who do not reported a seriously malfunctioning device. That sounds more like wishful thinking. The forum is not the only source (it's just the least reliable source IMHO): retailers get all the RMA requests which do not go through the forum but directly to Dlink labs. And if you participate on a forum: there's only questions and issues/problems on these boards, nobody goes to a forum to praise a product they just bought.
Your starting point is that there really is a serious issue but the numbers don't add up to that. It's like believing in extraterrestrial live. There are there but we just haven't seen them yet ;)
Your doing a lot of assuming. You should ask for clarification first :P and yes, my statement is very valid and true.
-
Lets say D-link sells 100000, units a year. Then take that an times it by the products lifetime of 2+ years.
Now look at the volume of failures that are specific to this ( not including hardware failure or misuse that results in a replacement that corrects the issue) and I can assure you that it's >1%.
Again, I'm not trying to in anyway discount the failures you guys are having, I'm simply trying to help everyone keep this in perspective.
We are working to correct this as quickly as possible.
Forums and Customer Service is where people go when there are problems with their products, this can make the issue seem much worse then it actually is on a global scale.
Just a little FYI.
That being said, I'm working with the PM team to resolve any issues with this unit esp. the ones with shareport.
Just curious since you are talking numbers. How many actually downloaded from Dlinks ftp fw1.31? I'm sure you can find that out easy enough.
I bet the numbers will also show the amount of traffic to the forum has greatly increased, along with customer service calls.
Also since fw1.31NA is only for North America if I'm not mistaken then a recalculation may be in order. How many of 100,000 were North America routers that could have upgraded?
A global scale? You want global scale then release it globally!
I bet the numbers wouldn't be >1% then.
-
Lets say D-link sells 100000, units a year. Then take that an times it by the products lifetime of 2+ years.
Now look at the volume of failures that are specific to this ( not including hardware failure or misuse that results in a replacement that corrects the issue) and I can assure you that it's >1%.
Again, I'm not trying to in anyway discount the failures you guys are having, I'm simply trying to help everyone keep this in perspective.
We are working to correct this as quickly as possible.
Forums and Customer Service is where people go when there are problems with their products, this can make the issue seem much worse then it actaully is on a global scale.
Just a little FYI.
That being said, I'm working with the PM team to resolve any issues with this unit esp. the ones with shareport.
Besides all the other issues people have brought up with your argument, such as how many people have actually installed 1.31, etc, dlink still hasn't explained how this can be hardware related when this problem arrived in a firmware that fixed the feature causing the freezes, along with how this is showing up on multiple products on the their latest firmwares.
-
So you're actually saying that it is more than 1 %. ::)
Lets say D-link sells 100000, units a year. Then take that an times it by the products lifetime of 2+ years.
Now look at the volume of failures that are specific to this ( not including hardware failure or misuse that results in a replacement that corrects the issue) and I can assure you that it's >1%.
Again, I'm not trying to in anyway discount the failures you guys are having, I'm simply trying to help everyone keep this in perspective.
We are working to correct this as quickly as possible.
Forums and Customer Service is where people go when there are problems with their products, this can make the issue seem much worse then it actaully is on a global scale.
Just a little FYI.
That being said, I'm working with the PM team to resolve any issues with this unit esp. the ones with shareport.
-
I guess there's a typo from Lycan?
@Mackworth: The question you're are asking (how many this, if, else etc) are effective in debating meetings in which you want to discredit the other party. ;)
The math is valid (taking the > -typo into account), assuming that there should be more is purely....an assumption, not substantiated. If people complain there is an issue. If people don't complain there is no issue, simple as that. Everything in this world will become a problem when you come up with al kinds of hypothetical situations.
I am a corporate guy and I understand perfectly that Dlink isn't obliged (and perhaps not willing too) to disclose all the nasty details about their equipment. I know everybody wants (or claims to be entitled to) complete transparency, but from a PR PoV this is not a wise thing to do.
Dlink should provide you with a solution and they are working on that.
And before you'll call me a Dlink fanboy or whatever: I really don't care about Dlink. It's just a router...
-
I <3 Typos. :)
-
I guess there's a typo from Lycan?
@Mackworth: The question you're are asking (how many this, if, else etc) are effective in debating meetings in which you want to discredit the other party. ;)
The math is valid (taking the > -typo into account), assuming that there should be more is purely....an assumption, not substantiated. If people complain there is an issue. If people don't complain there is no issue, simple as that. Everything in this world will become a problem when you come up with al kinds of hypothetical situations.
I am a corporate guy and I understand perfectly that Dlink isn't obliged (and perhaps not willing too) to disclose all the nasty details about their equipment. I know everybody wants (or claims to be entitled to) complete transparency, but from a PR PoV this is not a wise thing to do.
Dlink should provide you with a solution and they are working on that.
And before you'll call me a Dlink fanboy or whatever: I really don't care about Dlink. It's just a router...
Right, I understand dlink can't provide that information, and I don't expect them too. But If Lycan is going to make that argument he should back it up. It doesn't need to tell us the numbers, but if he said, "I looked at the number of individuals that have downloaded 1.31 and compared it to the increase in forum registrations/posts and call complaints and found that the number of complaints is less than 1%" people wouldn't be asking him those questions.
And in terms of providing a solution, so far D-Link hasn't even provided a light at the end of the tunnel. Lycan has said its not a firmware issue. So I am not sure what solution you think d-link is going to provide us unless they plan on RMAing all our routers with units running 1.11.
-
It's impossible to estimate how many users have 1.11, 1.20, 1.21, 1.30, 1.31 and 1.32. And issues also occur with early firmwares (below 1.3x) and all people use their riouter differently. There are just too many variables to give even en educated guess.
I am one of the lucky guys having a hassle free router it seems. My gut feeling is that there is a batch of routers that suffer from production errors (there a a lot of new parts used in newer revisions of the DIR) No, I cannot back this up (=> gut feeling). But that would also explain the 'lack' of communication ;)
-
well if that's the case, then it's safe to say that we would be able to confirm that with serial number to determine the batch run that's been affected.
-
It's impossible to estimate how many users have 1.11, 1.20, 1.21, 1.30, 1.31 and 1.32. And issues also occur with early firmwares (below 1.3x) and all people use their riouter differently. There are just too many variables to give even en educated guess.
EXACTLY THE POINT! You just proved my point. Lycan is arguing the rate of calls and returns is low. But you are saying its impossible to estimate how many users run 1.11, etc. He used his argument to claim that its not a firmware issue. If your argument above his true, you just invalidated his argument.
-
Blah blah blah...all I know is Dlink released a firmware with the intent of making my Dlink router better and I installed it with that understanding.
Lets face it most would not be here if there wasn't a problem.
-
EXACTLY THE POINT! You just proved my point. Lycan is arguing the rate of calls and returns is low. But you are saying its impossible to estimate how many users run 1.11, etc. He used his argument to claim that its not a firmware issue. If your argument above his true, you just invalidated his argument.
Nice try. You're using my words in a different context. It's a respone on
but if he said, "I looked at the number of individuals that have downloaded 1.31 and compared it to the increase in forum registrations/posts and call complaints and found that the number of complaints is less than 1%"
Shame on you. ;)
Lycan knows how many (absolute figures) returns have come in, and also which firmware that is on them. So if there were any anomalies specifically on 1.3x level he would know (and tell).
He also stated that (very many of)the devices returned/RMA-ed do not show the issues in the Dlink lab....That's funny, right?
-
well if that's the case, then it's safe to say that we would be able to confirm that with serial number to determine the batch run that's been affected.
In it's most simple form...yes. U 8)nless they don't know (yet) where the problem originates from
-
Nice try. You're using my words in a different context. It's a respone on Shame on you. ;)
Lycan knows how many (absolute figures) returns have come in, and also which firmware that is on them. So if there were any anomalies specifically on 1.3x level he would know (and tell).
He also stated that (very many of)the devices returned/RMA-ed do not show the issues in the Dlink lab....That's funny, right?
All I am saying is that just because an issue can't reproduced, doesn't mean its not an issue. I work with some of the largest retailers in the world, and sometimes I can't reproduce their issues. I make educated guesses at what the issue might be, and my code changes work. We have a firmware release that has caused users to run into an issue where it didn't before. The issue is happening over different product lines. The issue is happening with a feature that was "fixed" in the firmware that's causing the problem. No one has explained that.
-
Right. Ok, it takes 4 to 5 days for the issue to appear. I really don't believe dlink would spend those resources trying to reproduce the problem. sorry. I dont buy it. I also don't buy that the routers are RMA'd due to that problem. If by chance 1 got through, Dlink would simply plug the router in to a 30 second test, and deem it ok, and sell it as refurbished. That's reality in the corporate world.
-
Wrong. They're tested for 3-4 days before being released as replacements. Granted, some times failed units slip through the cracks but that generally results in us sending out a brand new unit thats been tested in house for that specific failure by an engineer.
-
I'm having issues as well, ever since updating to 1.31NA on my A3 revision. It typically happens between 2-5 days, but it depends on bandwidth usage. If I'm using a lot of bandwidth, the router quality deteriorates more quickly. Websites are slower to respond and/or don't completely load, and bandwidth is severely hindered. Accessing the router directly is a hit or miss, depending on when I catch the deterioration; the earlier I notice it, the better luck I have with navigating to reboot the router through the configuration page, although it often takes multiple clicks to finally get through. If I don't use my computer for a while, but others use theirs and it gets really bad, I have to power cycle the router physically because I cannot get to the router configuration page at all. So, to recap, things get worse seemingly depending on how much bandwidth is used over a period of time. If I download a whole lot in a short period of time, I might have to reboot within a 48 hours; the router lasts longer depending on how little traffic goes through.
The next time this happens, I'm going to try and remember to ping the router many times and see what the response time is and if packets get dropped. This has never been an issue with my router and uptime would go well beyond a month; since 1.31NA I can't go more than a few days without needing to reboot. I don't have a great understanding of how packets and bandwidth may affect the router, so I'm not sure if it's a number of UDP and/or TCP packets that reaches a ceiling, or if it's a number of concurrent stale connections that get left open and the router can't handle anymore, or if it's purely bandwidth that so many GB worth of data through the router causes it to go kaput. Hopefully this can be fixed since I supposedly cannot downgrade to a prior firmware version...this issue must be directly related to a permanent change within the 1.3x series which, for some reason, cannot be reversed.
-
I'm having issues as well, ever since updating to 1.31NA on my A3 revision. It typically happens between 2-5 days, but it depends on bandwidth usage. If I'm using a lot of bandwidth, the router quality deteriorates more quickly. Websites are slower to respond and/or don't completely load, and bandwidth is severely hindered. Accessing the router directly is a hit or miss, depending on when I catch the deterioration; the earlier I notice it, the better luck I have with navigating to reboot the router through the configuration page, although it often takes multiple clicks to finally get through. If I don't use my computer for a while, but others use theirs and it gets really bad, I have to power cycle the router physically because I cannot get to the router configuration page at all. So, to recap, things get worse seemingly depending on how much bandwidth is used over a period of time. If I download a whole lot in a short period of time, I might have to reboot within a 48 hours; the router lasts longer depending on how little traffic goes through.
The next time this happens, I'm going to try and remember to ping the router many times and see what the response time is and if packets get dropped. This has never been an issue with my router and uptime would go well beyond a month; since 1.31NA I can't go more than a few days without needing to reboot. I don't have a great understanding of how packets and bandwidth may affect the router, so I'm not sure if it's a number of UDP and/or TCP packets that reaches a ceiling, or if it's a number of concurrent stale connections that get left open and the router can't handle anymore, or if it's purely bandwidth that so many GB worth of data through the router causes it to go kaput. Hopefully this can be fixed since I supposedly cannot downgrade to a prior firmware version...this issue must be directly related to a permanent change within the 1.3x series which, for some reason, cannot be reversed.
Well, according to Lycan, you have a hardware problem even though it was working fine before 1.31.
-
Lycan
Any hint as to how long another released firmware aka 1.32 final may be?
-
Wrong. They're tested for 3-4 days before being released as replacements. Granted, some times failed units slip through the cracks but that generally results in us sending out a brand new unit thats been tested in house for that specific failure by an engineer.
I have a request. Would you please quote the post that you are responding to? Even if it's just the first few lines.
As a D-Link employee, and forum moderator, I do follow your posts.
-
Upgraded and my router went to sh*t:
http://forums.dlink.com/index.php?topic=6031.0
It happened occasionally before where I would lose connection but now it's really bad. Getting to the admin console is rare.
-
Upgraded and my router went to sh*t:
http://forums.dlink.com/index.php?topic=6031.0
It happened occasionally before where I would lose connection but now it's really bad. Getting to the admin console is rare.
Dirt (great name, by the way. No joke), have you tried taking your router out of the closet? (no double entendre intended). Do you have stainless steel studs in your walls? Do you live in an Airstream mobile home? (the one with the aluminum skin)
I'm having issues as well, ever since updating to 1.31NA on my A3 revision.
Jon, have you noticed whether or not your problems arise at the same time of day, or are they sporadic?
Do either of you have your routers placed near equipment that produce a lot of electromagnetic interference? Perhaps an aircondtioning motor on the other side of the wall, you live underneath high voltage transmission lines, your next door neighbor is a ham operator, your next door neighbor runs a hydroelectric power plant? Ok, sorry about that last one.
I know the both of you stated that the problem got worse after the flash upgrade but you were having these issues before the flash but not to this extent. Is that a true statement?
Forgive me if you think my questions are sophmoric. I'm just running over some things I'd try if I were having the same problem since I can't see exactly what your setup looks like, or whether you installed or unstalled software lately, or new drivers, or you changed some setting on one of your Windows services, or something - anything. Is your wireless setting set to "Always on"? Transmission rate set to "Best"? Channel width set to "Auto"? Auto channel scan enabled? (This particular feature is amazing. Everytime I reboot it never fails to select a channel that NO ONE else in my neighborhood is using) These are my settings and they work well for me. If yours are the same, well - hmmmmmmmmmmm.
When I look at my site survey I often see a neighbor's router pumping out a stronger signal than me and he is over a hundered feet away. But, I suppose that this should not have any effect on me if we are on different channels. Do you guys always select the same channel? I have noticed at times that I lose a bunch of signal strength every time my wife decides to come out to the garage (where I am) and talk on our 2.4GHz wireless handset. Other times the signal strength almost completely dies and I cannot figure out why but it is usually during the same time of day because when I crack the top on my laptop in the morning the signal is loud and proud. Don't kill me for this one but are your NICs Wireless G or Wireless N? I have a wireless printer that is Wireless G and one day I could not get it to connect until I figured out that while I was "playing around" with my settings I decided to check the "WLAN Partition" box in Advanced Wireless. It was one of those "Ah HA!" moments when I read the help file for that feature a second time. I discovered in real time that I had turned my wireless AIO printer into a very nice looking printer paper storage unit. Of course, UNchecking that box restored balance to the universe as sunlight came streaming through the windows, rainbows appeared and a unicorn went strolling through my living room. OK, I digress.
Just tossing a few bits of my stream of conciousness out there. Only a few though. I'm running out.
-
Have been having problems with my DIR655 freezing up for several months, sometimes it would go a week or two without a problem. It would freeze and no amount of resets would help. Would have to leave unplugged for several days then plug it back in and it would be ok. This last time I couldn't get it to do anything no matter how many times I reset it. When it was down I would go back to my old Buffalo router which worked fine. While on the Buffalo router tonight I went through these entire 17 pages of issues with this router. After reading I thought I would try the "DNS relay" trick. Put the DIR-655 back on the network and no amount of powering down, reseting did anything. WAN, LAN, nothing would work. Couldn't get into the router to do anything. Was about to give up when I remembered someone on here talking about unplugging their "weather station". Now whether it was coincidence or not, as soon as I unplugged the weather station the router came right up. I then went on in and disabled the "DNS relay". Of course will have to watch this for several weeks to know if anything fixed, but I am going to plug the weather staion back in and see if this fails with that on. If it does it again, will leave it off and see if that does anything.
Anyway, thanks to the forums for the tips. This is twice the forums have given me hope that the purchase of this router wasn't a total waste. Without your tips I would have kicked this thing to the curb a long time ago. Will keep you posted.
BTW. MY firmware is 1.21
Rusty
-
Well, that didn't last long. As soon as I plugged the "Weather Direct" Weather station in it knocked the router down. Unplugged and back up. Will leave this unplugged for now and let you know if any more problems.
Weird.
Rusty
-
I have a request. Would you please quote the post that you are responding to? Even if it's just the first few lines.
As a D-Link employee, and forum moderator, I do follow your posts.
He's replying to my post on page 16 about my feelings on their testing.
-
Here are my thoughts
I have bought a DR655 A4 in March. had the "DNS relay ALG rejected packet" error from the start.
Spent about two weeks with DLink support trying to get it fixed. (did almost every setting from wifi to DNS relay setting, 121 software) NONE WORKED.
After reboot the router cuts off internet in 1-3 days.
DLink suggested to return the first router, which i did. Did without it for more than 2 freakin months. ???
Got a new A4 with 1.20, upgraded to 121EU (it says). and guess what: the new one does exactly the same. :o
Each two seconds in the log it says "DNS relay ALG rejected packet"
In short this problem is in this product for about 4 months!! new versions have come out that still have this bug, unbelievable!! We are talking about a non working product guys
So yes i am kinda pissed >:(. Would like this resolved asap or will need to return the product. :-\
-
Jon, have you noticed whether or not your problems arise at the same time of day, or are they sporadic?
Do either of you have your routers placed near equipment that produce a lot of electromagnetic interference? Perhaps an aircondtioning motor on the other side of the wall, you live underneath high voltage transmission lines, your next door neighbor is a ham operator, your next door neighbor runs a hydroelectric power plant? Ok, sorry about that last one.
I know the both of you stated that the problem got worse after the flash upgrade but you were having these issues before the flash but not to this extent. Is that a true statement?
Forgive me if you think my questions are sophmoric. I'm just running over some things I'd try if I were having the same problem since I can't see exactly what your setup looks like, or whether you installed or unstalled software lately, or new drivers, or you changed some setting on one of your Windows services, or something - anything. Is your wireless setting set to "Always on"? Transmission rate set to "Best"? Channel width set to "Auto"? Auto channel scan enabled? (This particular feature is amazing. Everytime I reboot it never fails to select a channel that NO ONE else in my neighborhood is using) These are my settings and they work well for me. If yours are the same, well - hmmmmmmmmmmm.
When I look at my site survey I often see a neighbor's router pumping out a stronger signal than me and he is over a hundered feet away. But, I suppose that this should not have any effect on me if we are on different channels. Do you guys always select the same channel? I have noticed at times that I lose a bunch of signal strength every time my wife decides to come out to the garage (where I am) and talk on our 2.4GHz wireless handset. Other times the signal strength almost completely dies and I cannot figure out why but it is usually during the same time of day because when I crack the top on my laptop in the morning the signal is loud and proud. Don't kill me for this one but are your NICs Wireless G or Wireless N? I have a wireless printer that is Wireless G and one day I could not get it to connect until I figured out that while I was "playing around" with my settings I decided to check the "WLAN Partition" box in Advanced Wireless. It was one of those "Ah HA!" moments when I read the help file for that feature a second time. I discovered in real time that I had turned my wireless AIO printer into a very nice looking printer paper storage unit. Of course, UNchecking that box restored balance to the universe as sunlight came streaming through the windows, rainbows appeared and a unicorn went strolling through my living room. OK, I digress.
Just tossing a few bits of my stream of conciousness out there. Only a few though. I'm running out.
My router has not moved its location in about 2 years (I guess that's about how long I've owned it), and neither have surrounding objects, and it is not near any objects with strong and/or shifting fields of electromagnetism (I am writing my dissertation on certain effects of electromagnetism on the brain, in fact). The wireless portion of the router is irrelevant as well, because the most frequently used computers are wired directly...the main reason I have this router is because it supports 1gb ethernet and has new hardware within...I strongly dislike wireless connections, personally. The problem is noticeable by myself mostly, on my computer which is wired to the router with a 15 foot cat5e cable. I also use power conditioners and/or UPSes for my electronic devices, and use ferrite core chokes on cables that don't have shielding...and I personally wired my home with Belden ethernet and RG6 quadshield solid copper core cabling (most cable is rg6 and copper-clad aluminum core) with channel vision products in the central hub, and my signal to my cable modem is +0.7db. I also have RGB modded my older gaming consoles (crack them open and solder some new connections, or replace the PPU on the original NES console) and have had my television ISF calibrated by Bjorn's here in San Antonio (not by best buy or any of those commercial companies, which don't do a full ISF calibration, even though they say they do)...I'm a bit of a nut when it comes to electronics quality. I also don't use noise isolators when doing high-end car audio installations, because the way I install them, I prevent the problem from ever happening in the first place. I don't use a wireless connection, unless absolutely necessary, for anything besides talking on my cell phone.
Needless to say, I had suspected my modem was on the fritz until I remembered the firmware upgrade, which I hadn't considered since I had never experienced such a problem with a firmware upgrade on D-Link or other brand routers in the past. The firmware upgrade is the only change in the recent weeks, other than the environmental change of the major networks' analog antenna being turned off recently, but no new digital signals are in the area, either. I've used default settings on the router in addition to my saved settings, both to no avail.
I hope 1.32 can address this issue, but I may just have to RMA the router and get one with older firmware. I was not able to run ping tests on the router yesterday when it became unusable, because someone reset the router when I wasn't home.
EDIT: oh yeah, it's all on the LAN side, incase that hasn't been mentioned before. I cannot access the router configuration page many times, and cannot communicate among computers within the LAN. I will see if a LAN ftp transfer works next time the router grinds to a hault...maybe certain ports function and others don't? It's probably the whole that doesn't function though.
-
Router haulted again today.
Screenshot just last night (this morning) when performance was being slugglish, noticed something that i've never seen before.
(http://hpzdfa.bay.livefilestore.com/y1pfrVRuaei95lvb7D80lJLU3eP0Jfvj6r-Wnt9WlqgvlTGaazHqV_FBKNOmM_wkGBUKQhfJakmRE-3TqMlPatHwk_WAoo-A2eA/low_mem_router.png)
-
My router has not moved its location in about 2 years (I guess that's about how long I've owned it), and neither have surrounding objects, and it is not near any objects with strong and/or shifting fields of electromagnetism (I am writing my dissertation on certain effects of electromagnetism on the brain, in fact).
OK, next time please mention first that you are a freakin' genius before I make myself look like the no nothing I am! :'(
Well, since you have covered all bases with a tarp the size of a Ringling Brothers, Barnum and Bailey circus tent, the only thing left for me to bring up is your TCP/IP settings and have you ever optimized them? That's all I'm saying becasue I fear another slam dunk coming. :-\
(I'm MORE than impressed with your setup)
-
Router haulted again today.
Screenshot just last night (this morning) when performance was being slugglish, noticed something that i've never seen before.
I see your problem, your Icons are too big. ::) Have you been taking your Ginko Biloba? It's supposed to help with memory loss. ???
It looks like you are using Vista which means you probably have at least 2G (or more) of onboard ram. Is this true? Have you ever experienced problems with other applications running out of memory? Have you tried closing some of your other apps that are open? Does Vista have the "Advanced" setting where you can tell it to use more memory for programs instead of background services?
-
I see your problem, your Icons are too big. ::) Have you been taking your Ginko Biloba? It's supposed to help with memory loss. ???
It looks like you are using Vista which means you probably have at least 2G (or more) of onboard ram. Is this true? Have you ever experienced problems with other applications running out of memory? Have you tried closing some of your other apps that are open? Does Vista have the "Advanced" setting where you can tell it to use more memory for programs instead of background services?
Yeah, i have 4Gb memory in my DIR-655 too... It must be the problem here when windows use it all and give nothing to router. Damned!
-
Well ...Clancy and Xinot ....you did´nt solve my router problems....but your sense of humor is surperb :D
+1 to you both
-
My router has not moved its location in about 2 years (I guess that's about how long I've owned it), and neither have surrounding objects, and it is not near any objects with strong and/or shifting fields of electromagnetism (I am writing my dissertation on certain effects of electromagnetism on the brain, in fact). The wireless portion of the router is irrelevant as well, because the most frequently used computers are wired directly...the main reason I have this router is because it supports 1gb ethernet and has new hardware within...I strongly dislike wireless connections, personally. The problem is noticeable by myself mostly, on my computer which is wired to the router with a 15 foot cat5e cable. I also use power conditioners and/or UPSes for my electronic devices, and use ferrite core chokes on cables that don't have shielding...and I personally wired my home with Belden ethernet and RG6 quadshield solid copper core cabling (most cable is rg6 and copper-clad aluminum core) with channel vision products in the central hub, and my signal to my cable modem is +0.7db. I also have RGB modded my older gaming consoles (crack them open and solder some new connections, or replace the PPU on the original NES console) and have had my television ISF calibrated by Bjorn's here in San Antonio (not by best buy or any of those commercial companies, which don't do a full ISF calibration, even though they say they do)...I'm a bit of a nut when it comes to electronics quality. I also don't use noise isolators when doing high-end car audio installations, because the way I install them, I prevent the problem from ever happening in the first place. I don't use a wireless connection, unless absolutely necessary, for anything besides talking on my cell phone.
Needless to say, I had suspected my modem was on the fritz until I remembered the firmware upgrade, which I hadn't considered since I had never experienced such a problem with a firmware upgrade on D-Link or other brand routers in the past. The firmware upgrade is the only change in the recent weeks, other than the environmental change of the major networks' analog antenna being turned off recently, but no new digital signals are in the area, either. I've used default settings on the router in addition to my saved settings, both to no avail.
I hope 1.32 can address this issue, but I may just have to RMA the router and get one with older firmware. I was not able to run ping tests on the router yesterday when it became unusable, because someone reset the router when I wasn't home.
EDIT: oh yeah, it's all on the LAN side, incase that hasn't been mentioned before. I cannot access the router configuration page many times, and cannot communicate among computers within the LAN. I will see if a LAN ftp transfer works next time the router grinds to a hault...maybe certain ports function and others don't? It's probably the whole that doesn't function though.
Have you tried disabling "DNS relay" setting yet?
-
Yeah, i have 4Gb memory in my DIR-655 too... It must be the problem here when windows use it all and give nothing to router. Damned!
Smart-aleck. >:( You want me to sick my big brother on you?
I have the answer but I'm not sharing it until you apologize. :P
-
Well, since that message was the first thing I saw, it is starting to back up my suspicion about the dir having a memory leak and not releasing memory when it's needed.
I'm going to see if it's the logging feature that is the memory pig, which is causing the router to lock up.
-
Nope no way in hE** could it be the Dir 655's firmware. After 1k's of posts about recent firmware updates I have determined that you guys are a bunch of Idiots! LOL>>> ;D ::)
-
Smart-aleck. >:( You want me to sick my big brother on you?
I have the answer but I'm not sharing it until you apologize. :P
We dont need answers, WE NEED MORE INFORMATION! ;D
-
Yesterday my router got freezing again, after about 5-6 days uptime. :-(
I unplugged the power for a two seconds, and but it back again. Router running normally since then. This never happened with firmware 1.11 which I had before on the router.
-
We dont need answers, WE NEED MORE INFORMATION! ;D
YOU WON'T GET IT! ;D
-
YOU WON'T GET IT! ;D
I don't need answers. There's not much use in getting answers, nice firmware will do so we can all do something useful with our life.
-
I'm still amazed that Dlink hasn't been able to recreate this issue based on the number of people that are having the same symptoms. There are about 5-10 threads in this forum all describing the similar issues. In fact, just as I queued up this particular thread, in came the IP Protocol 17, IP Protocol 6, and DNS Relay errors. Had to power cycle the router to force a reboot just to post.
I'm not beating on the Dlink engineers here. I just want to know if there is more information besides the router logs and configurations that we can submit to help.
-
I don't need answers. There's not much use in getting answers, nice firmware will do so we can all do something useful with our life.
If tomorrow brought a fix to the Shareport thingy, (non)problem type situation, you could color me gone. I would break free from this "Hotel Portmeirion". Until then, I'm the smelly Uncle that lays around all day, drinks all the booze, eats all the food, puts his feet on the furniture, makes long distance phone calls, hogs the TV, makes uncouth noises and is about as welcome as a case of athlete's foot that just won't go away. Got any more chips?
-
I'm still amazed that Dlink hasn't been able to recreate this issue based on the number of people that are having the same symptoms. There are about 5-10 threads in this forum all describing the similar issues. In fact, just as I queued up this particular thread, in came the IP Protocol 17, IP Protocol 6, and DNS Relay errors. Had to power cycle the router to force a reboot just to post.
I'm not beating on the Dlink engineers here. I just want to know if there is more information besides the router logs and configurations that we can submit to help.
Everybody is talking about " the number of people that are having the same symptoms". How many people really have these issues (fact based, counting the number of reads of posts in a thread surely will not suffice)?
Not denying the issues, but making a lot of noise doesn't make a huge army... (Roman tactics, by the way, and they did work (sometimes))...
-
Valid point Demon. My counter point would be... how many do you need to consider it a problem? I think we would agree that there is a number (whatever that number is) of people coming to this forum with these common symptoms of some issue. Mind you that there are similar instances of this reported on the other router forums (8XX, etc) There are also a number of people who don't suffer or don't know they have the problem. There are also a number of people that don't know this forum exists or just expect wireless to be funky and do nothing. Without spending ridiculous resources to identify those people, I think its safe to say that the number will remain ambiguous shy of any statistical analysis.
This forum is based off of the squeaky wheel gets the grease concept. I don't see a form up anywhere where I can report issues. I don't see a poll. What else can we as the common consumer do to help make this issue more definitive?
-
How to define a problem...That depends on the number of units sold.
Again, not saying that if your unit does not work properly you don't have a problem. But a problem needing firmware resolving that's a whole different matter.
Your final consideration is a nice one for the Dlink guys :)
-
I'll just add for the record again that I was having the slowdown/freezing issue after upgrading from 1.11 to 1.31NA, which would occur after 3-5 days. Hardware A2. I disabled DNS Relay, and so far my router has been up 15 days with no noticeable issues. Prior to upgrading to 1.31, router had been up 90 days with no issues on 1.11.
As noted previously, I typically have a few IPSec VPN tunnels going to my company and interestingly find that when this issue occurred, I could still communicate to hosts over the tunnel, just couldn't initiate new connections to the internet.
-
I see your problem, your Icons are too big. ::) Have you been taking your Ginko Biloba? It's supposed to help with memory loss. ???
It looks like you are using Vista which means you probably have at least 2G (or more) of onboard ram. Is this true? Have you ever experienced problems with other applications running out of memory? Have you tried closing some of your other apps that are open? Does Vista have the "Advanced" setting where you can tell it to use more memory for programs instead of background services?
Clancy
Correct me if I'm wrong but I always thought that the router is stand alone hardware and not OS dependant for memory. I mean this is a home router not a corp. router or switch with extra memory and cpu's that kick in when loads get heavy.
-
Ok my (damn lost count) time. :'(
655 A4 bought in March. After on average each 2 days the router loses it and goes bananas (Internet is gone, DNS ALG stuff).
Discussed with DLink support back then. Did all the dances with settings DLink told me to make and new software (upto 1.21EU) for 2 weeks , no luck because after two weeks DLink decided to just ignore me. ???
Send my router for 'repair'.
After two months plus got a brand new one (A4 with 1.20). After 5 calls of what was going on with my product.
New one had again the same problem (shipped with 1.20), so 1.21 EU again (saved settings first). Reloading my settings into 1.21 EU and the router effectively stops functioning (log in not possible, keeps rebooting). (seems not related to DNS bug, yet another)
Found by myself it has to do with NTP settings or at least something with TIME. If you remove that from the settings (so leave those default) but set all else to your preference, you can indeed restore your old settings....
1.21 EU, same problem: DNS goes crazy and no internet access anymore (nothing todo with settings!!! in all settings it does this!)
went to 1.32. which gave a different (but not new) problem. Again bananas after on average 2 days but now it starts by switching of wifi first so effectively my wireless clients also have no internet anymore.
So it looks like the same kind of unstability (always a few days) but different symptom with 1.32 (al other versions it starts with DNS relay ALG stuff; cutting off internet)
Have done everything i can but DLink is avoiding me like the plague (all my posts here are left unanswered) and left me hanging for four months now. Why on earth? Are you guys going for a record of some sort?
Please tell me something because it is frustrating the hell out of me (and many more I see). This really harms the DLink brand you know. People within you company get hunderds of thousands a year to try and build up the brand but at the backdoor you are effectively throwing away your money in this way.
Can any of the DLink support crew give us a decent answer / fix for this problem? Or at least tell us then to return the product cause you can't seem to fix it? Product replacement an option?
now for the 3rd time this week wifi drops away and can't log in. Typing the correct password brings back the password screen again. Typing a wrong password gives (naturally) and dialog stating it is a wrong password.........
Nothing left to do the pull the plug again..... (but hey this normal for the 655?)
-
I'll just add for the record again that I was having the slowdown/freezing issue after upgrading from 1.11 to 1.31NA, which would occur after 3-5 days. Hardware A2. I disabled DNS Relay, and so far my router has been up 15 days with no noticeable issues. Prior to upgrading to 1.31, router had been up 90 days with no issues on 1.11.
As noted previously, I typically have a few IPSec VPN tunnels going to my company and interestingly find that when this issue occurred, I could still communicate to hosts over the tunnel, just couldn't initiate new connections to the internet.
Thank you post. This is the exact same thing that happened to me. Ran months without restarting on 1.11 but with 1.31 it was freezing every couple of days with 1.31 with dns relay on. Hopefully we can get more posts like this to show Lycan this isn't a hardware problem.
-
Clancy
Correct me if I'm wrong but I always thought that the router is stand alone hardware and not OS dependant for memory. I mean this is a home router not a corp. router or switch with extra memory and cpu's that kick in when loads get heavy.
Jason, every day I visit here I learn something new. The error in question resembled something I've seen from Windows. My answer was my best WAG (wild *** guess) work. Sometimes I actually know what I'm talking about. On other occasions, Xinot will point out the flaw in my logic with laser like precision. I should call him "Mack the knife" because he can slice me up like roast beef and in such a nice way that when he's through I'm left wondering "I'm not sure, but did he just call me an idi*t?". Moral of the story: sometimes I make guesses and if they are wrong I will undoubtedly learn something when someone posts the real answer. If you ever see me correcting anyone it is only because I am dead-level certain that I am right. There's a lot of frustration in this thread. I hope relief is not far away.
-
Clancy
Correct me if I'm wrong but I always thought that the router is stand alone hardware and not OS dependant for memory. I mean this is a home router not a corp. router or switch with extra memory and cpu's that kick in when loads get heavy.
This router (and all modern routers home or otherwise) has an OS and memory management. The features that are added on all have a memory cost. Any microcontroler based device that has a problem based on uptime (that is repeatable or not) I would begin by looking at 4 things.
- processor temperature
- power supple current stability
- power supply temperature
- possible memory management issues
I do not know anything about the issues with this (or any home class product) other than where I stick my nose in to try to help. I am not part of product management and have no access to their procedures or processes. But I can tell you they know the above list as well as me.
As for the comment I read somewhere in this thread about the forum being based on the "squeaky wheel" theory, this is as I have stated more times than I care to count not a D-Link contact. You are here to speak with other users, we are only here to make sure you play nice. Any contact from D-Link is because that person wanted to help, not because D-Link views this as a customer channel.
-
This router (and all modern routers home or otherwise) has an OS and memory management. The features that are added on all have a memory cost. Any microcontroler based device that has a problem based on uptime (that is repeatable or not) I would begin by looking at 4 things.
- processor temperature
- power supple current stability
- power supply temperature
- possible memory management issues
I do not know anything about the issues with this (or any home class product) other than where I stick my nose in to try to help. I am not part of product management and have no access to their procedures or processes. But I can tell you they know the above list as well as me.
As for the comment I read somewhere in this thread about the forum being based on the "squeaky wheel" theory, this is as I have stated more times than I care to count not a D-Link contact. You are here to speak with other users, we are only here to make sure you play nice. Any contact from D-Link is because that person wanted to help, not because D-Link views this as a customer channel.
Just to be clear about the subject matter Fatman, the router's OS and memory management system has nothing to do with a persons computer OS and management system. Correct?
If this is the case, from recent Dlink firmware releases and problems reported from the users it seems Dlink may be overextending the DIR-655 ability under certain circumstances to handle the loads. Example: torrents,Qos,portfowarding,Dns relay...etc. Most computer users can only multitask so much befor their computer systems start showing signs of sluggishness or even crashing, this is my thoughts on the Dir 655.
Dlink is trying to put 10 gallons of crap in a 5 gallon bucket. :-\
It all stated with shareport, KICK it to the curb! You bought a router not a NAS device. ;)
-
Dlink may be overextending the DIR-655 ability under certain circumstances to handle the loads. Example: torrents,Qos,portfowarding,Dns relay...etc. Most computer users can only multitask so much befor their computer systems start showing signs of sluggishness or even crashing, this is my thoughts on the Dir 655.
Dlink is trying to put 10 gallons of **** in a 5 gallon bucket. :-\
It all stated with shareport, KICK it to the curb! You bought a router not a NAS device. ;)
Correct, it is the router's not the PC's resources which matter here. I was trying to confirm that we are no longer in the days of static memory maps. Which is what I feared was meant.
Now, I do not know that this is a memory exhaustion issue, but I know I fear one.
I have been one of the founding fathers of the kick Shareport to the curb club for a while now. Then again the only thing I want my gateway to do in an ideal world is NAT and routing, no one makes products for me.
Shareport was added because it was the lightest way to add the features that people were DEMANDING, I put this in caps cause about the time we started this forum, every thread was "My DIR-655 works great but add NAS to the DIR-655" or "Add Print Server functionality to the DIR-655". It was aggravating feeling I was the only one who wanted to use a router as a router and no more.
C'est le vive!
-
Jason, every day I visit here I learn something new. The error in question resembled something I've seen from Windows. My answer was my best WAG (wild *** guess) work. Sometimes I actually know what I'm talking about. On other occasions, Xinot will point out the flaw in my logic with laser like precision. I should call him "Mack the knife" because he can slice me up like roast beef and in such a nice way that when he's through I'm left wondering "I'm not sure, but did he just call me an idi*t?". Moral of the story: sometimes I make guesses and if they are wrong I will undoubtedly learn something when someone posts the real answer. If you ever see me correcting anyone it is only because I am dead-level certain that I am right. There's a lot of frustration in this thread. I hope relief is not far away.
I'm learning also Clancy but the problem is the older I get the more I forget..dang waht was I talking about? >:(
This whole thread is crazy as I had mentioned in my replay to Fatmans comment, it may not be any users problem, it may be just Dlink pushing the chipset and memory of the router.
Ofcourse their are people on this thread that dose not have a problem and are treating others like dumb a**es. Thats fine, good for them! I'm sure I could tweak a few settings that I may not have a complete understanding about but I never had an issue or problem until after 1.11fw.
The bad thing is there are so many different config.'s, times like this you have to back track to narrow down the issues. I may be wrong but I'm sticking to shareport to start. :'(
-
Correct, it is the router's not the PC's resources which matter here. I was trying to confirm that we are no longer in the days of static memory maps. Which is what I feared was meant.
Now, I do not know that this is a memory exhaustion issue, but I know I fear one.
I have been one of the founding fathers of the kick Shareport to the curb club for a while now. Then again the only thing I want my gateway to do in an ideal world is NAT and routing, no one makes products for me.
Shareport was added because it was the lightest way to add the features that people were DEMANDING, I put this in caps cause about the time we started this forum, every thread was "My DIR-655 works great but add NAS to the DIR-655" or "Add Print Server functionality to the DIR-655". It was aggravating feeling I was the only one who wanted to use a router as a router and no more.
C'est le vive!
The Ideal of router resouces being depleted makes sense to me with all the odd-ball issues people are having.
Grant it we are only end users for the most part, I'm in no way a network tech or computer tech but through google I manage. ;D
Early in the posts I was reading how somebody was tracking some of the resources used, maybe it was just inbound & outbound, total connections..etc but to get to the point. Can you find out if there is a treshold? Just like with torrents, to many connections the rest of the network slows and the wife is screaming @ me. ;D To many processes and the router may be doing the same.
I know yourself & Lycan has been dealing with silly & stupid & crazy questions with the lasts few FW releases, maybe it could be this simple to explain to the PM. This could help explain the unexplained.
-
As for the comment I read somewhere in this thread about the forum being based on the "squeaky wheel" theory, this is as I have stated more times than I care to count not a D-Link contact. You are here to speak with other users, we are only here to make sure you play nice. Any contact from D-Link is because that person wanted to help, not because D-Link views this as a customer channel.
Thanks for the help you guys then give....
But hard to imagine you are not on the DLink payroll... why else do this?
It says forum.dlink.com..... Kinda creates expectations...
... and you expect to get support here because you can't get it elswhere at Dlink it seems....
-
partach1
I fill your pain but looking @ it from Dlinks prospective, this is not their only product or business. However I'm sure they sold alot of Dir 655 because it's (was for most)a good product. Until the firmware issues. Which for myself I can deal with for now, they'll (Dlink) will have another released firmware soon.
-
Thanks for the help you guys then give....
But hard to imagine you are not on the DLink payroll... why else do this?
It says forum.dlink.com..... Kinda creates expectations...
... and you expect to get support here because you can't get it elswhere at Dlink it seems....
Perhaps I was unclear, Those of us who have Mod or Tech badges under out names are on D-Link payroll. But we are not here as Tech Support. We are here as individuals. The only thing we do here that is D-Link assigned is modding duties, beyond that we are at liberty to post or not when and where it amuses us. And when we do post it is as ourselves, not as a D-Link representative.
There is Tech Support available, call the number on the box. I believe you mentioned having had a bad experience there, but that can be looked in to. If you need to communicate with D-Link then call CS or TS. If you want to know where a forum is that some of D-Links most advanced users (regardless of payroll) hang out come on in.
This site is operated by D-Link, but it is not a TS portal, it is a place for users to convene and either discuss D-Link products or assist each other.
-
So it looks like the same kind of unstability (always a few days) but different symptom with 1.32 (al other versions it starts with DNS relay ALG stuff; cutting off internet)
partach1, have you looked into this?
This text has been blatantly ripped from dsl reports.
From funchords:
And even with DNS Relay disabled, you're still getting the following? :
[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
[WARN] Fri Dec 02 10:05:50 2005 Packet Dropped waiting to resolve MAC for IP 192.168.0.150
Hmmm.
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.
Read this KB article: »http://support.microsoft.com/default.aspx?scid=kb;en-us;305553&sd=tech (http://support.microsoft.com/default.aspx?scid=kb;en-us;305553&sd=tech)
Take a look at the section entitled "How to modify DNS dynamic update behavior" and make sure that "Register this connection's addresses in DNS" is unchecked.
Hope that helps -- or at least gives us a lead ...
-
Now, I do not know that this is a memory exhaustion issue, but I know I fear one.
I have been one of the founding fathers of the kick Shareport to the curb club for a while now. Then again the only thing I want my gateway to do in an ideal world is NAT and routing, no one makes products for me. ...
I agree. Get rid of it. Router stability, and performance is paramount.
-
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.
-
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...................
-
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 (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...
-
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.
-
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.
-
What about flushing the DNS cache on each machine?
-
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.
-
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)
-
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?
-
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?"
- where is the software created?
Demonized knows. I read it in an another post. I just can't remember which one.
- 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.
-
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.
-
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.........
-
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....
-
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?).
-
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.
-
With this you insinuate that actually the product has no problem? Are you (then you ARE one the payrol:)?
My training is complete.
Yes. Yes I am on the payroll. In fact, I am the president of D-Link and I intentionally sold YOU a faulty product so I could come here and enjoy hearing you complain yet pretend I am sympathetic. Personally, I don't use D-Link. I think they sell junk so I bought a Linksys. My suggestion to you would be to head to nearest skeet range and see how many shells you can pump into your DIR-655 before it hits the ground. By the way, those links I put in another post? They work for me so it MUST be your router.
(I didn't really buy a Linksys because I can't seem to break my 655 no matter what I do. I gotta be doing something wrong)
I truly hate urination matches, Partach, so ... off I go into the ether(net).
To the rest of you, if you thought my suggestions were lame well, it's probably because they were. If I at least made you think, then it was worth it. If you've tried every single thing in the book, studied it from all angles, sought help but got no answers, then maybe it is time you took it back. If you''re fed up with D-Link in particular, buy something else. That's probably the best advice I've given.
-
How does it feel to be "EddieZ-ed"? ;)
-
Demonized knows. I read it in an another post. I just can't remember which one.
Shareport? Silex. SX Virtual Link clone.
-
So even the president of DLink has nothing better to do, I knew it! :D
Clancy it was all a test. The router is fine, perfect, peachy. the hundreds of people here are all in on it.
Sadly you didn't live up to our expectation, you can't even get jokes. Do you know how hard it is to get all these people together for you, jeeez. But you do make it fun.
But seriously, www.speedguide.net is not reachable for me!? OMGWTFBBQ?
Maybe all the things we are experiencing are in fact features! What does Dlink have against that site?
Or I bet DLink has a fitness program and they help us out by letting us walk to the router each day to reset it. Great thinking
-
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)
It seems you're part of the 'pack of losers' with a degenerated device. Just wanted to let you know that my DIR is working perfectly and is not showing all the issues you have. So it really does not matter what insults you bring on. At the end of the day my router is working! ;D
-
Insults? where? Lame answers get lame responses.
It´s my second one, so also did that trick already. But hey it could be two broken ones after each other. Two times A4. Maybe the HW version is the problem. Bought it discount maybe factory batch gone wrong dumpt on the market....
Please read my NTP feedback. http://forums.dlink.com/index.php?topic=6167.0
It probably depends on how you use and or configure the router .
But tell me:
- your hardware version?
- none of the software version gave you problems?
- which firmware did you have installed that works so great?
- Do you use many clients / much data?
- Do you use many wireless clients?
- Do you use NTP?
- Do use schedules?
- Virtual server?
- DHCP?
Please give as much data as you can.
-
Insults? where? Lame answers get lame responses.
It´s my second one, so also did that trick already. But hey it could be two broken ones after each other. Two times A4. Maybe the HW version is the problem. Bought it discount maybe factory batch gone wrong dumpt on the market....
Please read my NTP feedback. http://forums.dlink.com/index.php?topic=6167.0
It probably depends on how you use and or configure the router .
But tell me:
- your hardware version?
- none of the software version gave you problems?
- which firmware did you have installed that works so great?
- Do you use many clients / much data?
- Do you use many wireless clients?
- Do you use NTP?
- Do use schedules?
- Virtual server?
- DHCP?
Please give as much data as you can.
Using it with 5 wireless devices, 2 Shareport printers, I USB HDD and 2 wired devices.
And using all the features . How about that.
-
and
-
Alright guys thats enough mud flinging. As with MANY other threads I can sense some hostility so I'm going to do what a Mod does. Lock the thread.
I will say this however, I understand everyone is on edge about their units not working properly. I understand that from the outside it seems like D-Link isn't listening or doesn't care. That couldn't be further from the truth. Unfortunatley the D-Link employee's you're interacting with here at this level can't do much but take in your complaints and push for new code.
We're working to end this for the 655 and the 4500 but it takes time, a lot of time apparently. See as there is no solution for this issue and this thread has degenerated to name calling and figer pointing I'm left with only one recourse. Lock.
If you feel you've reached this recording in error, please check the number and dial again.
-Lycan.