D-Link Forums
The Graveyard - Products No Longer Supported => DIR-825 => Routers / COVR => Beta Code => Topic started by: arod on July 21, 2009, 03:59:13 PM
-
Post your feedback and comments here regarding topic firmware.
-
Im trying it so far so good for the last 30min keep you posted if I need to reboot or something
-
I switched to this firmware a few minutes ago. I hope it resolves the issues that 1.11 had. I'll post if I notice anything strange. Thanks for getting this out there.
-
Ive been running it for about 4 hours router seems very fast. faster then 1.01 no ill effect so far
-
Installed last night and OK so far... but it usually took 3-4 days for my problems to show up (DNS relay-related).
-
I've been having issues with the 5ghz network acting slower and occasionally cutting out compared with the 2.4 ghz one. I have a brand new laptop so I dont think it is the card in my comp. Then again it is a mac....
-
24 hours in, no bad issues, played ps3 today wifi no lag, no router freeze, i will repost in a week see how its doing
-
Installed 30x minutes ago, as needed to move on from 1.11NA with its weird hangs and slow downs. Using speedtest noted the LAN upload is 10% faster then 1.11NA 1.1Mbps. Download is same at 14Mbps. More testing tomorrow with wireless links.
Hopefully won't have to power off/on unit every week, as like with 1.11NA. Never had problems with DIR-665 so the DIR-825 has been a little disappointing as a (on reliability concerns) replacement.
-
Ok, after every 2 day lock ups I have upgraded to 1.12 before I put a bullet in this once great router!
The good is that my upload speeds have increased 2-3X Don't know why. Seems stable so far but up only a few hours.
The bad, still have a bug in the "Status---> Wireless" section that was present in 1.11 and not in 1.01. Seems that there is no info on the wireless connections as the window for the 2.4 and 5G bands are missing. It was working fine with the firmware upgrade to 1.12. When I enable some port forwarding, the wireless status window disappears. I could not get it back by uploading the last known good configuration and I had to factory default to get it back. Will keep ya posted.
-
Ru-Fi-Oh,
Is it still recommended all settings be loaded manually with 1.12 rather than importing from a previously saved file? I'm using 1.10 and haven't had any issues (other than Shareport). I'd prefer to simply import the 1.10 settings if possible but will enter everything page by page manually if you think it's advisable.
Thanks
-
What happened to multifunction printer, scanner, fax support with shareport since 1.01, was completely broken in 1.11 and now only printer function sorta works. It prints, but a one page document gets printed with half on one page and half on another. The scan and fax features no longer work, printer software gives off an communication error. This happens in all versions of Windows... XP, Vista, and Win7 with an HP Officejet J5700 series multifunction printer, everything worked perfect prior to updating from 1.01 to 1.11, all other issues experienced with 1.11 seem to have been resolved in 1.12b5.
-
I had worked around issues in 1.11 by disabling the 'dns' option, but moved to 1.12b5 to see if it would net any improvements with gaming. I played a couple of games of wc3 last night and didn't have any issues. I'll be testing more over the weekend, but bandwidth seems good.
I do have the wireless session display bug that was noted a few posts above, I guess I'll try resetting back to defaults and reconfiguring, and see if that clears.
-
Ru-Fi-Oh,
Is it still recommended all settings be loaded manually with 1.12 rather than importing from a previously saved file? I'm using 1.10 and haven't had any issues (other than Shareport). I'd prefer to simply import the 1.10 settings if possible but will enter everything page by page manually if you think it's advisable.
Thanks
Yes I suggest creating a new config from scratch. The reason is there's changes in the code where if you load an older config it can throw off the settings.
-
Yes shareport still has it's issues and we're working on them on all router across the board. The only thing we can suggest right now is uninstall the drivers make sure you have the latest drivers for your printer and reinstall them. Temprarily disable any firewalls or AV's during this process and test it out.
-
Yes shareport still has it's issues and we're working on them on all router across the board. The only thing we can suggest right now is uninstall the drivers make sure you have the latest drivers for your printer and reinstall them. Temprarily disable any firewalls or AV's during this process and test it out.
If you care....Shareport is useless in its current form since only one client can connect at a time (and then must disconnect before another can connect). It reminds me of Lantastic from the mid 1990's!!! If Dlink can manage to allow multiple simultaneous connections, then Shareport will be a more viable and well received feature.
-
I installed version 1.12b5 the day it was released and it seemed to be working fine. Today the router disappeared from the network. This is the same "bug" I was seeing before after I installed v1.11.
The router sites remotely in my home and having to reset it every two-three days is difficult. I hope this gets resolved soon.
-
Upgraded to 1.12 a couple days ago and 2 days in a row it has disappeared/hung up and I have to pull the power cable and reinsert it. I have now disabled DNS Relay again which is what had worked on 1.11 for several months.
I hope at least with DNS relay off again it will continue to work as it did in 1.11.
Thanks,
Jeff
-
The 5ghz seems to be the one that disappears on me. It has very similar settings to my 2.4 ghz network. I stopped using it because it was flaky. I wonder if some of you are having problems because of that? The 2.4 network seems to work rather well. I'm annoyed though that I can't rely on the 5 ghz at the moment. But then again, this is so far a world better than 1.11 was.
-
Day 2 with 1.12b and so far stable and no locks ups. I have not activated port forwarding yet as when I do I lose my wireless status info. Also noticed the wireless connection is not restarting randomly as stated in the log with 1.11. Speeds are stable with better uploads for 450kbps to 2000kbps. I also did a fresh install and NOT a restore config file as mentioned earlier. Hope that helps others.
-
Is it better than the original 1.01?
What I mean is, is it worth updating? Or should I wait until this beta turns official?
-
Well it's too bad they didn't fix the 'wireless client info' bug. I will pass and stick to 1.01 on my replaced router. You guys are very brave. If I was on 1.11, I would try it. It's working great with 1.01 so I'm going to stay on the sidelines. Thanks for testing.
-
ru fi oh, you should probably put this firmware up and take down 1.11. I think this firmware is ready for prime time. Theirs probably a lot of people that are having issues that don't even go to the forum for help and they might just return the router and get a different brand
-
For gods sake, STICK with 1.01!! Don't upgrade unless you have issues and the beta is final and working fine for a few months. I was not having any issues with 1.01 and just upgraded to fix any potential bugs, what a mistake. Why in the hell would d-link make the firmware non-downgradable?? It was either go for 1.12 or else my router was facing an untimely accidental death for a warranty replacement as tech support on the phone was hopeless and worthless. At least we have a moderator who is addressing the issues and I think we all appreciate his/her work. I just wish there were more of them around to work on this issue.
-
WELL IT CRASHED!! >:( >:( Not only a few hours on my last post the router crashed again after 2 days. This time it did it while I was on. I noticed the web pages were getting slow to load. I tried to login to the router and no dice. Could still login into other intranet devices like Vonage Box. Then the router crashed with no internet pages loading but strangely enough my streaming Pandora was still playing! Rebooted and back to normal. Ru fi oh, this is not ready for prime time and this is unacceptable performance as I need a reliable router. Looks like this router is going to have to die for a replacement! Good luck to all that are in my shoes!!
-
I experienced the exact same thing as hogdoc.
It appears as if the router is doing a slow meltdown. Not everything stops working once you can no longer address the router directly but eventually it completely collapses.
I have the dlink network monitor widget up all the time and it loses the router before the, it seems, the degregation begins. It seems that applications already communicating with sites continue to work and the internet connection slows down.
I saw that applications such as pandora, netflix, news widgets, weather bugs and such continued to work as long as I didn't stop and restart the programs/device after web pages stopped loading.
When the router is working, it's great. However, this slow meltdown is unacceptable and must be fixed.
-
For gods sake, STICK with 1.01!! Don't upgrade unless you have issues and the beta is final and working fine for a few months. I was not having any issues with 1.01 and just upgraded to fix any potential bugs, what a mistake. Why in the hell would d-link make the firmware non-downgradable?? It was either go for 1.12 or else my router was facing an untimely accidental death for a warranty replacement as tech support on the phone was hopeless and worthless. At least we have a moderator who is addressing the issues and I think we all appreciate his/her work. I just wish there were more of them around to work on this issue.
My guess as to why firmware is not downgradable is due to Dlink probably changing the CPU (Ubicom) microcode along with the new firmware installation. The old firmware likely won't work with the modified microcode.
I think that Dlink's engineers are beginning to realize the shortcomings of the Ubicom CPU solution. While a great CPU from a performance perspective, I think they are experiencing issues programming to it. This may be part of the reason why Dlink chose to abandon it and go with the Atheros CPU for the B1 revision.
Can't say for sure, but since Dlink isn't forthcoming about the limitations, I just thought I'd share my experience. I formerly worked for a company that did software/hardware design using MIPS CPU's.
-
I experienced the exact same thing as hogdoc.
It appears as if the router is doing a slow meltdown. Not everything stops working once you can no longer address the router directly but eventually it completely collapses.
When the router is working, it's great. However, this slow meltdown is unacceptable and must be fixed.
Could be a memory leak where the kernel is losing needed RAM space and being forced to shutdown services to the point where the router becomes unusable. Dlink should be able to resolve this.
Maybe Ubicom's new Linux toolset will give Dlink the freedom their engineers need to manipulate this CPU properly.
-
I have an RMA ready to send in if this one doesn't fix it...
-
Four days of no issues, then the dreaded 1.11 firmware lockup symptom in 1.12b5, solution was to disable dns relay again. Maybe it's time to RMA.
-
Same here, 4 days and got up this morning and the router was locked out. Had to pull the plug and reboot. DNS relay was enabled. Guess I'll have to disable it again. Anyone know where I can order a B1 version? I'm reading that the B1 is working great with the 202 firmware.
W
-
I still have no issues with the 1.12 firmware its been about a week, kinda of weird sorry to hear some of you are still having problems
-
I still have no issues with the 1.12 firmware its been about a week, kinda of weird sorry to hear some of you are still having problems
Same here... I had the DNS relay-related problem with 1.11 but no problems with 1.12 so far.
-
I can no longer use Network Filter (MAC Filter).
I've always used the 825 as an access point only with no WAN connection.
Ever since FW 1.11 and this 1.12NA version Mac filtering breaks internet access for ALL wireless clients.
When MAC filter is on I can still see the wireless clients from all other wired and wireless clients as well as see all other clients both wired and wireless froma wireless client.
But, when MAC filter is on all wireless clients have NO internet access. They all connect to the 825 without any issues.
Some simple testing shows that when MAC filtering is on that ALL internet requests try to go out through the unused WAN port instead of routing over the LAN port like they did in FW 1.00 and 1.01.
Local subnet 192.168.xxx.xxx requests do route over the LAN port as they should.
My only option for now is to disable Network Filter or MAC filtering but I'd really love to be able to use it again. When it is disabled then everything works great.
-
Once again.. the people that did upgrade to 1.12Build05 did you reset the router to factory default after the firmware upgrade and build a config from scratch? Do not load a previously saved config!
-
I did a restore to default twice and rebuilt the config from scratch by hand but the mac filtering issue persists.
FW 1.11 was when I noticed this issue.
-
Yes, did a factory restore and fresh manual reconfig. It just crashed again after 2.5 days of up time! Opps, looks like this router had an unfortunate accident and is being RMAed! Good luck fixing this mess.
-
Once again.. the people that did upgrade to 1.12Build05 did you reset the router to factory default after the firmware upgrade and build a config from scratch? Do not load a previously saved config!
I didn't.
I had problems with 1.11 and did do a config reset, which didn't fix the problem.
I haven't had problems with 1.12 and did not do a config reset (I restored my 1.11 settings).
-
hmm, it seems that shareport doesn't work any more?
This is just great.
Well, let's hope that at least it will stop dropping connections, it'll always be something (and the reason I decided to leave 1.01, despite some helpful souls telling me to stick with it). So far so good. Haven't seen a big change in performance though, still mediocre at best when you get over 20 feet away.
I do expect shareport to work soon enough.
-
Finally, mine stopped working with 1.12... needed a manual reboot because I had no Internet access and couldn't access the router admin page. I guess I'll disable DNS relay again...
-
Once again.. the people that did upgrade to 1.12Build05 did you reset the router to factory default after the firmware upgrade and build a config from scratch? Do not load a previously saved config!
Ubicom development tool problem? Seems that users have an issue regardless of whether they default or not.
-
I was up and running on 1.12b5 for a few days and thought all was well, then hit massive amounts of latency/packetloss while in a game (wc3) this last Sunday night (same old issue I'd been having with 1.11), had to cold restart the router to correct. I have reset to factory and rebuilt the config (Wireless status bug is also still present), I have also tried various config settings (disabling wish, disabling QOS, etc) to try and unload the device. My home has a single pc, so priorities don't net anything other than slightly increased processing lag (not really noticeable but still not needed) though I have tried both enabled and disabled qos.
little background:
I had a lot of issues using the dwa-160 usb adapter. Seemed like bus throughput issues as I would get momentary drops (2-4 full sec) in layer 3, but the OS didn't report signal loss. I replaced this with the pcie card, dwa-556. I no longer had drops, online gameplay was smooth again. However the signal reception was significantly lower (not to mention the 556 adapter did not support 5ghz). After playing around with antenna position, router position I found and subsequently upgraded from 1.01 to 1.11 hoping it would improve my signaling issues. It did not, and I encountered all the problems people have noted with 1.11. I had tried various drivers, including the most up to date Atheros (non dlink) drivers for my 556 and nothing worked. However, reinstalling my os to a fresh copy of win7 increased my noise margins by nearly double, and I am now fairly satisfied with my wireless signal, even though the broadcom g chipset on my laptop gets a full -98db sitting on the desk next to my desktop. All I would like is stable throughput.
local network:
Router: dir-825
NIC: dwa-556
Inet provider: brighthouse/roadrunner turbo 20Mbit/2Mbit
wireless config: N and G only, 2.4ghz only on chan 1 and 5 (40hz bandwidth), all other wireless AP's in area are on chan 6. PC is about 30ft from AP, and separated by 1 interior wall.
OS: win7 build 7100
-
What's this? Now 1.12NA is now the official release? No longer a beta? But my router still locks up with beta 1.12NA with the DNS relay enabled.
I'm going to have to look for another brand router. This is just stupid.
-
What's this? Now 1.12NA is now the official release? No longer a beta? But my router still locks up with beta 1.12NA with the DNS relay enabled.
I'm going to have to look for another brand router. This is just stupid.
I'm in agreement, but I can't afford another router, I already spent over $100 on this one back in Feb and am not willing to spend more than that on a new one, the netgear equivalent is worse than this router, and the Linksys one is just too expensive.
This new firmware is stupid, it doesn't help that my idiot brother decided it would be a great idea to upgrade my RMA'd router to 1.11, idiot. So, now I'm using 1.12 with the same issues!
-
Am I missing something in these posts? I've been running for 5 days with no lockups with DNS relay disabled. I also rebuilt my config from scratch.
Does DNS relay provide much value anyway? I agree 1.11 was a nightmare, but if 1.12 with DNS relay is off works, then not sure why anyone would need to RMA this thing.
SharePort is another problem entirely. Maybe it doesn't work but I'd wager that most people would find it useless anyway given the design limitations.
-
Am I missing something in these posts? I've been running for 5 days with no lockups with DNS relay disabled. I also rebuilt my config from scratch.
Does DNS relay provide much value anyway? I agree 1.11 was a nightmare, but if 1.12 with DNS relay is off works, then not sure why anyone would need to RMA this thing.
SharePort is another problem entirely. Maybe it doesn't work but I'd wager that most people would find it useless anyway given the design limitations.
Could someone please explain how to turn DSN/Relay off in the router, I know that it's under the router settings but the checkmark is greyed out, how are you able to turn it off?
-
Could someone please explain how to turn DSN/Relay off in the router, I know that it's under the router settings but the checkmark is greyed out, how are you able to turn it off?
Go to setup/internet/manual internet connection setup/
un-check "Enable Advanced DNS Service"
Then you can uncheck DNS Relay.
-
after disabling graphical authentication, when i attempt to log in as admin with the correct password, it says invalid password, even though i know it's correct. after about the 3rd or 4th try entering the same password, it finally goes through. any way to fix this bug?
-
nevermind, its a problem i am having only with Safari.
-
Installed the Beta (I assume it's the same as NA). I disabled the DNS relay. But Shareport still doesn't work.
Oh well.
-
Been running on the Beta 1.12NA since it was available. With DNS Relay enabled, it would (as like 1.11) would go into a hang, requiring a power off/on to recover. Couldn't even log on to 192.168.0.1. After disabling DNS Relay, been no issues (fingers crossed).
ps: Performing Factory reset & then rebuilding config again (as like 1.11) makes no difference in preventing this hang situation.
| 11thAug09 Went 9x days without a lock-up, best I've ever achieved on this unit. What was different |about this lock up though, the logon panel via 192.168.0.1 could be displayed (others..wouldn't |display). As I was at work...had the wife recover via power off/on unit. Wish this unit has the reliability |of the previous DIR-655.
-
When I originally installed the beta I completely re-did the entire configuration. The router started to fail after just 2 days like it did with the previous version. I turned off the DNS Relay and reset the configuration again. It is now in it's fourth day with a single hiccup.
In my opinion, DNS relay serves no purpose at all so it should be turned off as a factory default or fixed so no one has to deal with it.
-
Okay, I'm officially fed up. I rebuilt my config from scratch and turned off DNS relay. It was exactly 2 days uptime and my wireless became unresponsive, I went to a wired machine and by the time I got to it and tried to log into the router, it had rebooted itself and was testing upstream. I have one question, how did you guys fix the lockup issue? Make the router restart after 2 days? I did not touch any of the settings nor do anything to cause it to reboot just now in the past two days. Disabling DNS relay is not helping me, and I will not pay for nothing again by RMA'ing my router.
I don't even use the SharePort, I was looking into it but decided not to bother after reading others' issues with it.
edit: Okay, 10 minutes after it rebooted itself, I had to go pull the power because connecting to wireless was impossible. I tried my Macbook Pro and a Gateway laptop, both had connection timeouts. Ugh...
-
I have dns relay off, I use the 2.4 ghz network because the 5 ghz doesn't work. Now the router will hang for about 20 second intervals every few minutes. This is extremely frustrating. I think you guys need to rewrite your firmware from scratch. Because this just isn't working. My $50 linksys router I bought 5 years ago works better than this router.
-
Using older firmware (1.01) I had been unable to get WOL over internet working. As soon as the computer went into standby, the router took the mac off its table and hence virtual server didnt work. Attempting to forward it to address servers (255 or 127) did not work either.
With new firmware (1.12NA), computer still seems to fall off table on standby but at least i am able to forward port 9 udp to the network address server (255). Thus, I am finally able to wake my computer from the net, allowing me to set up servers (try the new windows 7 media player streaming with the divx labs mkv splitter... I can stream all my hd movies to anywhere with decent quality!) without running my computer all day.
So I, for one, am happy with the new firmware (but I did disable DNS relay just to be safe!)
-
Just wanted to add my voice in. Coming from Firmware 1.01, 1.11, and 1.12 now
Shareport = Still not working correctly after less then 24 hours after reboot.
Router still locks up after 3 days....with DNS relay and Advanced DNS turned off... im running for about 5 days now.
-
Yes Shareport does have it's issues across the board of all routers that support shareport. We are currently working on a utility fix. we don't have an ETA but do have one in the works.
-
Well I did what I read here. I did a manual reset of the router. Installed the new non beta firmware v 1.12NA. I manually redid my configuration. I did this on Saturday morning the 1st. I left DNS relay enabled. The router locked up 20 minutes ago, the 5th. I got almost 5 days. I'm sorry Ru-Fi-Oh your new firmware fixed nothing for me. Any chance I can return this A1 for a B1? ;D
I didn't think so :'(
I disabled DNS relay again that seems to stop the lockup for now.
As I wait for the next firmware. ???
WF
-
Same problems for me. I reset to factory defaults, manually reconfigured, and left dns relay on. Had to reboot the router after about 2 days. Turned off dns relay. Had to reboot the router after about 2 days.
-
Using the 2.4 network (since it is the only one that seems to work reliably) wireless n works really well. However, I have older comps on the network that cant use n. The mixed mode n and g causes ssh connections to stall slightly a lot of the time, with an occasional hang up for up to about 30 seconds. Since I do more than just surf the web, this is extremely annoying. Any idea why the n and g network stalls? I've had this router too long to return to best buy. Since I spent $160 I'd like it to actually work.....
-
A little less than 4 days uptime, was using the net a few mins ago and realized that nothing loaded and my wireless disconnected. My router rebooted itself...again. And yes, DNS Relay is OFF. I think we're all still assuming that this thing is locking up because of some sort of memory leak or because some log or whatever is getting full, did dlink seriously just put an auto-reboot in there? That would be bs.
-
Sorry for my English...
After updating FW to 1.12NA my Mac's can't see home local network's NAS and Window's computer.
"Bonjour" doesn't work. Nothing in my Network Places.
Downgrading to 1.11 don't solve the problem, network still unaccesible.
I've reseting the router, restore factory default settings from router menu - no result.
Now I've a new trouble with dir-825 - on the some pages in router menu (port forwarding, virtual server ..) if I want to change the page I've see a note -
"There is unsaved data on this page.
Do you want to abandon it?If not, press Cancel and then click Save Settings.
If so, press Ok."
After I've pressed a "save" button I've see this note again.
-
Well the router ran for 14days without a problem with DNS Relay off. Today it locked up again.
Shutting off the DNS Relay seems to have made it last longer but the problem is still there.
-
Made it just over a week and the freakin thing rebooted itself again. This is ridiculous.
-
Why can't you guys make a 1.01 version that we can downgrade to? The only reason I updated the firmware was because I had a roommate (with a very old computer) who couldn't connect. Now that roommate is gone and I'm stuck with and extremely flaky router. This is ridiculous, I'm never buying a DLink router again. Mainly because it seems that you've given up on the HW A1 version that I happen to own. Why a 2.0 FW for the B series, but nothing for the A1 except this less than optimal FW?
-
Why can't you guys make a 1.01 version that we can downgrade to? The only reason I updated the firmware was because I had a roommate (with a very old computer) who couldn't connect. Now that roommate is gone and I'm stuck with and extremely flaky router. This is ridiculous, I'm never buying a DLink router again. Mainly because it seems that you've given up on the HW A1 version that I happen to own. Why a 2.0 FW for the B series, but nothing for the A1 except this less than optimal FW?
I grabbed this from another forum. It could explain why we can't go back.
DLINK problem is hardware not working with the firmware... Relay and DHCP Reserved/Revoked will always be an issue with their wireless N routers... I like DLINK but after spending over $100 for a plastic business/home router to only work up til 6 months then started to act up after updating firmware after firmware because the darn thing wasn't meeting FCC rules for operation.
http://www.dslreports.com/forum/r23046150-Rant-No-Longer-Running-DLink
I guess the question is, since the change by the FCC, can dlink fix the problem or did it break the dlink 825 Rev. A forever?
-
Is anyone using Guest Zone? I can't get that to work at all. I'd like to... Here's a post from earlier on this:
I have RevA and 1.12NA. Don't see much of a change from 1.11. I had a weekly or so problem where it would lock but just the other day found the "DNS relay" trick and that seems to work.
My problem is Guest Zone.... It does not work. I have no security set up on the router (guest or non-guest) but do filter on MAC address. I live 19 floors up so I doubt people will "hack" into the router.
To be friendly to the neighbors, I decided to turn on guest zones. However, I have found that unless a MAC address is entered (for the secure zone) in the MAC filtering table, there is no way you can connect that computer. It does shield correctly, in that if I use my laptop to use the guest account, I can't go anywhere but the internet.
Does anyone actually use the guest zone? I'd like to.
-
Thanks Shoey Peachew. Following that link inspired me to order a router that was suggested there from netgear. I found it on newegg.
Goodbye Dlink. I don't necessarily blame every product you make on this brick of a router, but it will take a lot of good reviews on a product to encourage me to come back.
Hopefully, my months of frustration with my home wireless will soon be over.
-
After suffering from sporadic lock ups of my DIR-825 I've picked up the LinkSys WRT54G2. The new router only does g not n protocol but I'm amazed at how much better the range is on the Linksys. I regularly stream video over about 100 ft indoors to a TV top Dlink DSM-750... the Linksys does a great job of this! Ahh sweet freedom... now.. I wonder if LinkSys has a better media router :P
-
I had lock ups like everyone else and turned off DNS Relay. No more lock ups, so that's good. I don't have any extraneous stuff attached except a DNS-323 as backup config in RAID 1. It all seems to work. Range seems quite good. My issue is the Guest Zones. They don't work unless your guests are in your MAC address list, which defeats the whole purpose. MAC address filtering is the only item I use for security (no WEP or anything, just MAC).
Any fix on the horizon for that for REV A units? For the rest this seems like a fine router.
-
Man, I sure wish I saw this before I upgraded the firmware. Went from a trouble free router, to nothing but trouble.
-
I'm glad I found this thread at last. I had no idea what was causing this expensive router to hang up every couple of days.
I have bought my last D-Link product.
I wish someone one would sue these companies that do this to people.