D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-825 => Topic started by: orgwizard on January 17, 2011, 12:39:56 PM
-
OMG...it's a miracle...2.05 was released a few days ago...
I've stuck with 2.02 cause of all the complaints about 2.03.
who's gonna be the first to man up and give it a spin?
I'm a little skiddish as I need mine for work
-
I installed it yesterday. Don't see any change from 2.03.
The 825 still only connects using wireless-n with other D-Link devices. All the other brands that I have will only connect using wireless-g.
-
sheesh, hadn't even heard about that one...
I'm using 2.02na still, and not having issues with any devices connecting to N
guess I'm holding off again for now.
-
DIR-825 (B1) F/W 2.05NA
===========================================
DIR-825 Revision B Release Notes:
Firmware: 2.05NA
Date: 01/13/11
1. Fixed BT issue.
2. Support IPv6 spec v1.13 (6rd DHCPv4 Option)
===========================================
NOTE:
Please read the following instructions for firmware upgrade. You must upgrade to firmware “DIR-825 B1_fw2.05_1” before proceeding to firmware “DIR-825 B1_fw2.05_2”
Step 1: a web-browser such as Internet Explorer and enter the IP address “192.168.0.1” to log in to your D-link DIR-825 router.
**NOTE: Before you upgrade the firmware, you should save your current configuration by going to the Tools → System tab. Click on the “Save configuration” button to save the current configuration.
Step 2: Go to the Tools → Firmware tab, click choose file to select the first firmware name “DIR-825 B1_fw2.05_1” to the firmware upgrade file, and click on the “Upload” button.
Please wait 180 seconds for this process to complete and log in to your DIR-825 router again.
Step 3: Go back to upgrade firmware the Tools → Firmware click and upload the second firmware name “DIR-825 B1_fw2.05_2”.
**NOTE: If you lose your Router’s setting configurations, you can load the previous settings if you saved it previously. Select the configuration file by going to the Tools → System screen. Select Browse under System Settings and select your configuration file. Then click “Restore Configuration from File” button.
-
What a disaster. Updated to 2.05 following d-link's own instructions. Flashed to DIR-825 B1_fw2.05_1 first, after that the router has a yellow light and I'm unable to get to the admin page. After 30 minutes of hand wringing, trying to reset the router nothing worked. Finally connected to the Internet with my iPhone, and found out I needed to change my Windows adapter IP setting to something like "192.168.0.5" and set the gateway to 192.168.0.1 and I was finally able to get to the router admin page. It was a basic white screen, I then flashed to DIR-825 B1_fw2.05_2 and got my router back up and running.
-
I flashed to the new firmware on the weekend and had no problems at all. So far all is working well. I was previously on 2.02NA. At least I can now reserve for MAC addresses that begin with anything other than 00. Time will tell if there are any negatives for me.
-
Just upgraded from F/W 2.03NA to F/W 2.05NA. Went as smooth as a
two stage flash can be expected.
None of the issues with F/W 2.02NA have been observed.
Copying the two .bin files to a Flash Drive made it a little easier to
work with the Configuration Utility dialog box.
Edited 01-19-11 7:27 EST
After closer inspection there is no doubt that F/W 2.05NA includes a
fix for the IPv6 settings. The changes appear to be working.
AFAICT, the results received from Jason Fesler's Page are different now
than with F/W 2.03NA.
http://test-ipv6.com/
Your milage may vary.
-
what about the wan speed issues everyone was complaining about with 2.03?
-
I am still confused about the performance reports from various DIR-825
users when changing from F/W 2.02NA to 2.03NA.
My observations from upgrading F/W 2.02NA to 2.03NA were:
1. The WAN Port Speed issue is fixed.
2. Based on GRC (Shields Up test) all ports are full stealth by default.
My observations from upgrading F/W 2.03NA to 2.05NA are:
1. None of the prior issues with F/W 2.02NA can be detected.
2. The only obvious change in the Config Utility is IPv6 6to4 now lists by default:
SLAAC (Stateless Address Auto Configuration) and
RDNSS (Recursive DNS Server). These two mods appear to have
altered the results I receive from using http://test-ipv6.com/
Hope this helps. Certainly hope I don't sound terse - just trying to be
precise - would rather help reduce confusion if possible.
-
no worries...any info is good info...
just held off on 2.03 cause of the long thread of complaints in this forum....
good to hear that it seems to be working for you...
might hold out for a few more days and see if anyone else pipes us
thanks again for the feedback.
-
Anyone else have a problem checking the 825 status after flashing the new firmware? The first status page (device info) loads fine, but the other pages like logs, routing, wireless etc give me a browser error. Tried IE8, IE9 beta and Chrome. I tried from both a desktop and a laptop. 2.03NA Firmware was/is fine.
If I disable WiFi or set no security or WEP security that status pages work ok. I usually use wpa2_psk security and that's when the status pages give me an error.
Is it me or is the firmware loader that comes up when you hold the reset for 45 seconds gone in 2.05? I was able to go back to 2.03 by using the firmware loaded in the tools/firmwar menu.
-
Sorry I cannot help with the status issue. Hopefully
someone elso knows and will speak up.
Browsers: I had some astonishing experiences trying to
config a Cisco RVS-4000 using IE8. The instruction manual
suggested IE so I used IE8. The interface would transistion
just like a save was being performed but after restarting
the gateway, a significant portion of my saves were not
maintained in the firmware. Switched to Firefox and *most*
of this behavior went away. Notice I said most - not all.
I have stuck with Firefox ever since and that goes for DIR-825
as well. Firefox only here.
This Browser issue (which one is best) constantly rears
it's head. I've often wished the network device builders
would have someone write a super clean and simple Browser
designed to do the Interface and Config Utility work. One
which gets rid off all the bloat code that makes some
browsers (like IE) unreliable for servicing a gateway/router.
I am a big fan of IE9 Beta but I would not ever try to run
the Config Utility with it.
The main thing about your post that thrilled me was the
fact you could downgrade the firmware. I have no use for
any F/W that cannot downgrade.
Again, sorry you had to back up the bus. On the up side,
F/W 2.03NA ran like a champ here.
-
HI, had 2.03NA installed since the first day I bought my dir-825, here's one speedtest, my advertised speed is 50Mbit/2Mbit
(http://www.speedtest.net/rank/2914178138.png) (http://www.speedtest.net)
This morning, after i Installed 2.05NA:
(http://www.speedtest.net/result/1121193182.png) (http://www.speedtest.net)
and after i reverted my firmware to 2.03NA:
(http://www.speedtest.net/result/1121219065.png) (http://www.speedtest.net)
So personnaly, I will not touch ever this 2.05NA.
-
I upgraded from the 2.03NA firmware to 2.05NA with no problems. In fact, the wireless signal strength from my DIR-825B1 seems to have improved a bit. My ISP is 20Mb/s download and 2Mb/s upload, and that's exactly what I'm getting on the speed tests I've tried. I use Firefox with the router's GUI without issues. IE works for me, but is extremely slow with 2.03 and 2.05.
-
My speed test results are same/same as grandforker's.
-
Anyone else have a problem checking the 825 status after flashing the new firmware? The first status page (device info) loads fine, but the other pages like logs, routing, wireless etc give me a browser error. Tried IE8, IE9 beta and Chrome. I tried from both a desktop and a laptop. 2.03NA Firmware was/is fine.
If I disable WiFi or set no security or WEP security that status pages work ok. I usually use wpa2_psk security and that's when the status pages give me an error.
I decided to try 2.05 again. I was able to duplicate my problem even with Firefox so it's not a browser issue. The problem seems to happen when security is set to WPA2 only ***AND*** the 825 is being used as a Wireless Access Point (WAP). So you need to disable DHCP server in Network Settings and disable UPnP under Advanced Network to duplicate this problem.
Is it me or is the firmware loader that comes up when you hold the reset for 45 seconds gone in 2.05? I was able to go back to 2.03 by using the firmware loaded in the tools/firmwar menu.
I was able to verify that the DIR-825 B1_fw2.05_1.bin file disables the native firmware loader that was in previous versions. So beware if you're trying DD-WRT or Openwrt you might have to flash back to 2.03 to get the native loader.
-
well I tried to update from 2.03 and did not get past the first part. I let it sit for quite a while and never was able to get past the first screen. I've been on the phone with dlink tec support for about 2 hrs. Got to the second level support. Tried everything and it looks like the router is borked. I have to RMA it. I really can't be w/o wireless so I'm going to have to get something else today to get up and running. Nothing but issues with this router anyway. Bummer
-
well I tried to update from 2.03 and did not get past the first part. I let it sit for quite a while and never was able to get past the first screen. I've been on the phone with dlink tec support for about 2 hrs. Got to the second level support. Tried everything and it looks like the router is borked. I have to RMA it. I really can't be w/o wireless so I'm going to have to get something else today to get up and running. Nothing but issues with this router anyway. Bummer
before sending in
try
http://wiki.openwrt.org/toh/d-link/dir-825
Step 1 of Installation using firmware recovery mode
Get into the D-Link recovery console with the steps below:
While powering up the router, press and hold the reset button until the power LED starts blinking orange (usually takes around 45 seconds)
Set a static IP on your PC to 192.168.0.100 / 255.255.255.0
Go to http://192.168.0.1 using your MS Internet Explorer (other browsers don't work and also a Windows running on a VM, like VMware, doesn't work!)
and flash to 2.05 1st file then use IE to flash to 2nd that's how I got mine to work
-
I will give it a shot and report back thank you very much for replying.
-
You my friend are a genius :) I spent about two hours on the phone with the bonehead tec support. What pinheads, even got to the second level help. That worked, I'm very grateful :D
Thanks,
Peat
-
well..bit the bullet tonight and did the upgrade...here are the results...
first off...big thank you to dhlee528 for the recovery info...mine too failed on the update to the first file...and your fix got me up and running again...
my big concern was speed, so I tested before and after and must say...folks were right...
was over 4mbps up before the upgrade, and 15-20 down.
after the upgrade..I actually saw a bump in my download speed...testing the same two sites over and over consistently got me above the 20mbps range...and ever subsequent test (while playing with the router settings) made the number go a bit higher...
will say, makes me wonder if that stuff is being manipulated by companies like comcast to make themselves look good.
I also used the FCC test site as well, though not sure if it randomly picks it's test servers, but also was over 4 mbps up.
sure enough, after the test...down was crap..wouldn't go over 1mbps...
looking around, and playing with a few settings, ended up at the QOS upload speed setting...
normally is always set to auto...and getting the crappy upload speed on both test sites, that auto showed either 1024 or some message about not being able to measure.
so..started going up by 1024...and sure enough...it was the magic fix...
ended up setting mine to 5120, and that got me my continued nice download numbers, and above the 4mbps range again..so left it there...may test higher later...but at least I'm back to where it was before the upgrade and then some on the download.
I even turned on advanced dns for the first time just for fun..and the improved speeds held...
I think dlink intentionally or unintentionally changed that detect for the worse...not sure exactly how it does it's measurement, or what the real impact may be on QOS capabilities..but that seems to be at the heart of the slow upload speed.
other than that, so far so good..
will report back in a few days with how some longer term testing is going and I've had a chance to look around to see if there's anything interestingly new and can see how my wireless network is doing.
-
Took the plunge and upgraded to 2.05 from 2.03. No problems if you follow the directions. Noticed that using WEP security does not work in the guest network so went to WPA and no problems. I guess it does not like WPA on the main wireless and a WEP on the guest. So far stable but the wireless signal strength is very over inflated. At least now it is listing the wireless clients with the IP address!
-
Will there be new firmware for Rev A of the 825? I hope we 'early adopters' are not left out!
-
you know you bought a dlink right?
it's a miracle that we got one...and as is the norm for them...
as soon as they release a new model...the old one is left in the dust...
I too had one of the early mimo, high priced routers when it was pretty early in the 802.11 stuff..and they bailed on that quickly...leaving many bugs behind...
just just bumped the model number a little and could then call mine obsolete.
I feel for ya.
-
What a disaster. Updated to 2.05 following d-link's own instructions. Flashed to DIR-825 B1_fw2.05_1 first, after that the router has a yellow light and I'm unable to get to the admin page. After 30 minutes of hand wringing, trying to reset the router nothing worked. Finally connected to the Internet with my iPhone, and found out I needed to change my Windows adapter IP setting to something like "192.168.0.5" and set the gateway to 192.168.0.1 and I was finally able to get to the router admin page. It was a basic white screen, I then flashed to DIR-825 B1_fw2.05_2 and got my router back up and running.
I too ended up with a router stuck flashing an orange power light. I was upgrading from 2.03NA to DIR-825 B1_fw2.05_1.bin and with about 100 seconds left on the countdown IE8 went to a connection failed page. I recovered my router by putting it into recovery mode as described on the OpenWRT Wiki (http://wiki.openwrt.org/toh/d-link/dir-825#installation.using.firmware.recovery.mode). I had to give my computer a static IP and then flashed straight to DIR-825 B1_fw2.05_2.bin
I also find it silly that if you check for updates from your router's Firmware Information page, you are given a link to 2.05, but it is only a single .bin file which my router with the 2.03 firmware refused to flash.
-
Where do you all grab the 2 files, DIR-825 B1_fw2.05_1.bin and DIR-825 B1_fw2.05_2.bin
?
The download from the router only grabs one and it refuses to flash.
-
Where do you all grab the 2 files, DIR-825 B1_fw2.05_1.bin and DIR-825 B1_fw2.05_2.bin
?
The download from the router only grabs one and it refuses to flash.
ftp://ftp.dlink.com/Gateway/dir825_revB/Firmware/dir825_revB_FW_205NA.zip
-
Thanks for the link, much obliged. Firmware successfully upgraded. Download speeds at 44Mbps, much improved. Upload looks throttled back at 1Mbps, may follow the instructions in the earlier post to see if it can be improved.
-
hopefully my trick helped....
if not, look around in the forum for 2.03na, as there's also a lot of folks and possible solutions for the upload issues that started with that version....
I skipeed and went from 2.02 to 2.05 and so far, after fixing the upload thing...all is working well...
even have my cell phones running stable at 802.11n finally.
pretty happy with the router thus far...
-
looking around, and playing with a few settings, ended up at the QOS upload speed setting...
normally is always set to auto...and getting the ****py upload speed on both test sites, that auto showed either 1024 or some message about not being able to measure.
so..started going up by 1024...and sure enough...it was the magic fix...
ended up setting mine to 5120, and that got me my continued nice download numbers, and above the 4mbps range again..so left it there...may test higher later...but at least I'm back to where it was before the upgrade and then some on the download.
The QOS problem was there already in 2.01EU here !
If the 'upload speed' is too low entered in the QOS engine, the download will be limited. This is normal, the only problem is that the automatic upload speed testing is not reliable, causing a too low upload speed entered in the settings.
Probably because the test-server Dlink is using, is not very close to your location. If there is a network problem between you and the upload test server, the speed is measured too low. My upload speed is 10Mbit and download 120Mbit, but when I do the automatic speedtest, the upload is set to about 1Mbit and the QOS limits my download to a very low speed.
I always put my upload speed to a little bit lower than my real upload speed, and then the QOS works fine and download speed is 120Mbit.
On the moment I am still using 2.02EU as it works good for me (I don't use Wireless al lot)
-
:'(
I just upgraded from Firmware 2.03NA 4/27/2010 to Firmware 2.05NA 1/13/2011 (B1 Hardware). I have been having a problem trying to setup a VPN to work across this router and have never been able to get it working. I have tried everything from port forwarding to setting my laptop to an address outside it's firewall to no avail. Every few weeks I keep searching the internet for more answers but have not found anything that has worked. I have also found lots of comments about the DIR-825 dropping connections, losing power, poor signal strength and others issues. Since the upgrade the router is completely locked up. I followed the directions as directed by D-Link for the upgrade and have tried to reset to factory defaults and nothing works. I get the power light and a wired connection but that is it. I finally gave up a bought a Linksys E3000 and everything works!!!!! I have a PS3, 2 laptops, iphone, blackberry, ipod, psp, wii, desktop and a PS/2. I have not found anything that has failed yet. So my advice is if your problems are not too bad do not run the upgrade. If you have problems just buy a new router. Give up now and before you by another d-link product do your research and always check customer comments. I have spent way too may hours trying to tweak my DIR-825 to get better response but I never expected to see so may negative comments about the DIR-825.
-
Was the 825 router working well before you upgraded it?
What was the reason for upgrading?
Did the router work on VPN before upgrading?
-
Many thanks to dhlee528 for the advice on how to use firmware recovery mode. Otherwise, I would not have know what to do!
-
I am getting the error message
UPLOAD FAILED
The uploaded firmware file may not be correct. You may have uploaded a file that is not intended for this Gateway, or the uploaded file may be corrupted.
If the uploaded file is correct, it is possible that the gateway may be too busy to properly receive it right now. In this case, please try the upload again. It is also possible that you are logged in as a "user" instead of an "admin" - only administrators can upload new firmware.
The Gateway will not be reprogrammed.
I have tried wireless/wired. Also tried Rev B and Rev B1. Does anyone has any idea whats going on?
btw,what is the diff. b/w RevB 2.05 and RevB1 2.05 firmware. I did notice B1 was a bin and Rev B was a zip file but dont knwo the difference :-).
Thanks
-
I am getting the error message
UPLOAD FAILED
The uploaded firmware file may not be correct. You may have uploaded a file that is not intended for this Gateway, or the uploaded file may be corrupted.
If the uploaded file is correct, it is possible that the gateway may be too busy to properly receive it right now. In this case, please try the upload again. It is also possible that you are logged in as a "user" instead of an "admin" - only administrators can upload new firmware.
The Gateway will not be reprogrammed.
I have tried wireless/wired. Also tried Rev B and Rev B1. Does anyone has any idea whats going on?
btw,what is the diff. b/w RevB 2.05 and RevB1 2.05 firmware. I did notice B1 was a bin and Rev B was a zip file but dont know the difference :-).
Thanks
Only update firmware with a wired connection. Download the zip file because there should be 2 bin files and instructions. One file needs to be loaded before you can load the other one.
Reset the router to it's default state(Push in and hold reset for 30 seconds). Make sure you're using Microsoft IE because some people have had problems with other browsers.
If you still have problems try the native firmware loader. Push in and hold the reset for 45+ seconds until the power LED blinks orange. If that doesn't bring up the firmware loading screen try... unplug power adapter... push in and hold reset... continue to hold reset in while plugging back in power adapter...keep holding reset till power LED blinks orange... should be about 20 or so seconds. Load the first bin file and repeat above to bring up native firmware loader and load the second bin file.
-
Anyone else have a problem checking the 825 status after flashing the new firmware? The first status page (device info) loads fine, but the other pages like logs, routing, wireless etc give me a browser error. Tried IE8, IE9 beta and Chrome. I tried from both a desktop and a laptop. 2.03NA Firmware was/is fine.
If I disable WiFi or set no security or WEP security that status pages work ok. I usually use wpa2_psk security and that's when the status pages give me an error.
Is it me or is the firmware loader that comes up when you hold the reset for 45 seconds gone in 2.05? I was able to go back to 2.03 by using the firmware loaded in the tools/firmwar menu.
Same problem here, DHCP disabled, WPA2, status page is messed up, clicking on wireless status either fails or takes me back to login page.
P.
-
I upgraded 4 devices from 2.03 to 2.05.
3 devices upgraded ok (except for the status page not working), 1 device never came back to life after flashing the first bin file.
On power on the switch would work, but device light stayed orange.
P.
-
I upgraded 4 devices from 2.03 to 2.05.
3 devices upgraded ok (except for the status page not working), 1 device never came back to life after flashing the first bin file.
On power on the switch would work, but device light stayed orange.
P.
Read my comment on 2nd page about how to use recovery
-
Read my comment on 2nd page about how to use recovery
Ok, I'll go fish the box from the trash and try it out.
Thx for the suggestion.
-
A little OT are hardware the same (DIR-825)between EU and NA?I mean can I use the NA firmware on my EU router?Whitout dammage.
-
I believe WiFi channeling is different between NA and EU thus why there are 2 separate versions for each unit. I would also presume that the power adapter unit is different as well.
-
Tried the NA firmware on my EU router..the router would not accept in so it was a no go.
-
OK, "bit the bullet" and went from 2.02NA to 2.05NA. Used the Zip file from the dlink web-site (support area). The MS Word files describes first saving your configuration, then doing the two firmware upgrades. Firmware upgrades went fine (both, in-order). No need to futz with hard-coding IP address on PC: "it just worked".
Minor issues:
* Firmware upgrades killed my config. Having saved per instructions (MS Word in Zip), I simply restored the config; all was well.
* Upload speed went from 4Mbps (2.02NA) to 1Mbps (2.05NA). I went into QoS and disabled automatic speed detection, set speed to 4096, and got my speed back.
In summary:
* Upgrade seems to be a "good thing".
* Watch that QoS (upload speed); any and all tips re: QoS optimization much appreciated!
-
Glad the updgrade went well.
Minor issues you saw:
FW upgraded always kill configs. The reason is that the roms and memory are fully erased and re-written to. Just the way it is.
Notice that QoS always is ON by default and is really not set up for this unless you go in and set up a Static Reserved IP address, then put that into the QoS as a rule, like for gaming and game consoles or say if you want to stream on a PC and yes someone else is hogging the bandwidth, then you might want to put the PC and the other PC in to the QoS rule to help balance them out when you have them on line at the same time. Thats what QoS is generally for. Make sure all devices get good bandwidth with out hogging other out.
If your not seeing this or have alot of devices online at the same time then it's preferred to turn QoS off and just run normally.
-
Was curious if your seeing the same thing on v2.06?
HI, had 2.03NA installed since the first day I bought my dir-825, here's one speedtest, my advertised speed is 50Mbit/2Mbit
(http://www.speedtest.net/rank/2914178138.png) (http://www.speedtest.net)
This morning, after i Installed 2.05NA:
(http://www.speedtest.net/result/1121193182.png) (http://www.speedtest.net)
and after i reverted my firmware to 2.03NA:
(http://www.speedtest.net/result/1121219065.png) (http://www.speedtest.net)
So personnaly, I will not touch ever this 2.05NA.
-
with 2.06, 60Mbit/3Mbit advertised
(http://www.speedtest.net/result/1432515346.png) (http://www.speedtest.net)
and I'm downloading with utorrent right now.
-
Good to hear. Enjoy.