D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => WBR-2310 => Topic started by: mnewcomb on September 13, 2008, 08:38:42 AM
-
Um, over a year since 1.04 and this is all the information you can tell us about the 1.05 firmware?
"Fix LAN/DHCP server IP reservation range mis-judge issue."
/fail
Guys, the WBR has some serious stability problems. If you could just admit it, we would feel much better...
I'm very nervous about trying 1.05 AGAIN. Especially since I had to time my reflash from the first 1.05 between the 5 minute reboots so it wouldn't brick...
Can some adventurous individual try it and let me know how it is?
-
I`ll try it now...
I`m too desperate to get stability with this router to wait any longer... ::)
-
Firmware look good so far...
No reboot even if I`m doing some torrent.
Will try to let some wireless clients connected and check how it goes...
I think they nailed it this time :P will add some more comments soon...
-
The device did not reboot yet... keeping my ;D
-
The device did not reboot yet... keeping my ;D
HAHAHA... Could this one do the trick?
-
As soon as I upgraded to v1.05, I tried the automatic port-forwarding feature(app. rulz), which was the main cause of my disconnection problem. And guess what, the router hasn't been disconnected since!
:D This is it. ;D
-
Ok... I'll grab it and do the U/G over the weekend on my home router.
If I'm "Mr. Angry" on Monday, you'll know how it went...
;)
-
'Application Rules' works fine. However, keep in mind that it seems the router still disconnects on 'Universal Plug and Play (UPnP)' protocols. I hope it to be fixed on v1.06.
-
'Application Rules' works fine. However, keep in mind that it seems the router still disconnects on 'Universal Plug and Play (UPnP)' protocols. I hope it to be fixed on v1.06.
Just updated to 1.05 - I have UPnP enabled!
Been about 15 minutes since I finished configuring it.
DLINK - can you make sure that a firmware upgrade has an option link to a "restore saved setting" option?
This would be a real fantastic feature... the button on the upgrade firmware option does nothing except to start the load of the new bin file... the saved settings file is not loadable in the new release of firmware!
We'll see how long it takes to reset itself....
-
Its been a couple of days now... no reboots. :o
By the way, my log file is up to 10 pages.... it never got beyond 4 pages before a reboot before with 1.04, so this is better.
Looks like with 1.05 this is fixed!!!!
Thanks guys.
;D
-
I installed firmware 1.05, but just like last time it was released I was unable to load my config file (.BIN) from the 1.04 version to the 1.05 version. I get the error message "CFG checksum error" with only option to continue. >:(
I went back to 1.04 for now as I didn't have the time to write down and manually enter all the settings (wireless, DHCP reservations, port forwarding, DDNS, etc). Previous firmware upgrades have been able to upload config files from older firmwares. Any chance of having v1.05 being able to upload v1.04 config files or do I need to do it manually? :-\
-
Any chance of having v1.05 being able to upload v1.04 config files or do I need to do it manually? :-\
fusch: I agree 100%.
This is such an obvious feature that is missing...
DLINK: Any chance of this getting attended to? ;)
-
As soon as I upgraded to v1.05, I tried the automatic port-forwarding feature(app. rulz), which was the main cause of my disconnection problem. And guess what, the router hasn't been disconnected since!
:D This is it. ;D
If the firmware of your router is lower than 1.04, you cannot upgrade straight to 1.05 or 1.05b15 based on my experience troubleshooting this router. If there's case that it accept it, that's fine. But most of the time it doesn't really work properly. Unless the router is already using 1.04, then it can be upgraded to higher version .
-
In other nearby threads you will see that I reverted back from 1.05 to 1.04. All things being equal, the wireless disconnected faster on 1.05 than 1.04.
Using designated IP addresses on the router set up, we are "enjoying" blocks of 12-days uninterrupted wireless using 1.04. My next steps, once confirmed that it is indeed a 12-day cycle to quit (not really a quit; just that the remote PCs are unable to find the IP; wireless signal is still on) will be to designate a static IP address on one of the two PCs to see it that makes a difference; after that, fooling with the UPnP setup.
After that, MAYBE the Russian firmware or 1.05 again with the same settings that do it for 12 days now under 1.04. I remain very leery of the Russian firmware - reinforced now in this thread by issues being experienced in flipping between firmware versions.
Isn't this fun .........................