D-Link Forums
The Graveyard - Products No Longer Supported => DGL-4500 => Routers / COVR => Beta code for the 4500 => Topic started by: arod on July 09, 2009, 03:36:48 PM
-
Post your thoughts here please.. Push the router to the limit or normal use and we will see what happens after the 3-4 day mark.
**Correction/modified: users that are willing to upgrade, go ahead and upgrade. Users receiving A2's that have A1's don't upgrade so we can get those units in for testing. We need them at there current failing state.
Please backup config, reset the unit to factory default (you don't need to do the 30, 30, 30 that doesn't work) then upgrade the firmware.
-
I'll wait to see what Reinvented and some others have to say before I decide to update to this new firmware.
Currently running the last Beta of 1.20 and I have no incentive to upgrade until I hear some positive reviews of this (or newer) firmware.
-
yeah Reinvented is very detailed with his testing and feedback. Much appreciated from a user outside of D-Link. I will load as soon as I get home tonight.
Assuming this firmware goes well, Tuesday July 14th will be the 5 day mark for users that upgrade today. Based on results from now until then will depend if we can make this official. So for those that are going to be upgrading please be detailed with your feedback.
-
Thanks for the email Ru-Fi-Oh. Already loaded it up, so I'm going to start my testing right now.
Now, keep in mind I just moved and now have a different ISP. I'm using Verizon FiOS, which is on the 25 Mbps symmetrical.
Will report back in a few hours to see how it's holding up.
-
Thanks for the email Ru-Fi-Oh. Already loaded it up, so I'm going to start my testing right now.
Now, keep in mind I just moved and now have a different ISP. I'm using Verizon FiOS, which is on the 25 Mbps symmetrical.
Will report back in a few hours to see how it's holding up.
I thought they had you use one of their routers? Though I haven't been keeping up with them so I could be wrong. I gave up after they kept saying "soon available in your area"... been a while now.
-
I thought they had you use one of their routers? Though I haven't been keeping up with them so I could be wrong. I gave up after they kept saying "soon available in your area"... been a while now.
What...?
I have been using their router. It's an A1 they replaced with an A2. Still showed same symptoms. It's looking okay for right now. Lots and lots of LAN errors.
Edit: Okay, now I understand what you meant. Yes, I am using their router. However, it is BEHIND the DGL-4500.
-
Loaded it up a couple of hours ago. Just general use so far and all seems ok except that my uplload speed seems to have been cut in half. I'm using Comcast DOCSIS and was getting 50-52 Mbs down and 9-10 Mbs up with v1.20. Now I'm getting 50-52 Mbs down and 4-5 Mbs up. Hopefully just a settings issue as I configured from scratch and maybe I missed something. Let you know in a few days if their is any effect on the power recycle issue.
-
Update 1:
Router is definitely more responsive. I tested it during gaming, and it seems better for sure. I still get a few latency spikes, but it's not as bad.
Lots of LAN errors, and wireless errors - ONLY after a few hours.
There is still some problems with using WPA/WPA2, and TKIP and AES while using N/G and G only in 2.4 GHz. This is a problem since there are still people who use legacy devices.
I had an error when setting up GameFuel rules, where I needed to edit one after saving (and not rebooting), and it brought me to a blank page, and then kicked me out of the GUI.
No lock ups yet - but then again, I never experienced one. Only a slow down, and that was it.
-
I loaded fw last night and played Red faction on the 360 with Lycan. So far so good. Like you Reinvented, I never saw the 3-4 day lock up, just a slow down as well. So far I haven't seen any LAN errors on my end. Are you getting a lot of LAN errors?
-
Sorry, WLAN errors, not LAN. However, I do have some abnormally large amounts of dropped packets.
LAN Statistics
Sent :35341
TX Packets Dropped :34
Collisions :0
Received :35425
RX Packets Dropped :0
Errors :0
WAN Statistics
Sent :123474
TX Packets Dropped :0
Collisions :0
Received :137976
RX Packets Dropped :0
Errors :0
Wireless Statistics
Sent :2684783
TX Packets Dropped :1309
Received :2580323
RX Packets Dropped :2913
Errors :2691
-
I'll give this firmware a shot on my A1. Been having some trouble with the 1.20 ever since I downloaded it, so hopefully this one works out better than the previous beta.
-
Update #2:
I had a very very bad slow down over wireless. Pings shot up really really high. Nothing else was running...just my game. It's only been up about 18 hours so far. Wired still works fine.
Will report back later after I stress it a bit more.
-
I might as well try it too. My router has pretty much been a brick ever since I upgraded. DLink support ran me in circles. It stalls every 2-3 days. I found it's more ****e to occur when using wireless from Mac OS X. GO figure...
-
I might as well try it two. My router has pretty much been a brick ever since I upgraded. DLink support ran me in circles. It stalls every 2-3 days. I found it's more ****e to occur when using wireless from Mac OS X. GO figure...
That is interesting, it would explain the lockups I've been having. Will know in a few days if the beta is no different than the past.
-
Reinvented,
What wireless client are you noticing the slow down?
What exactly are you doing when you notice the slow down? is it just gaming?
What are you gaming on?
What are you pinging when you see the slow down?
-
Reinvented,
What wireless client are you noticing the slow down?
What exactly are you doing when you notice the slow down? is it just gaming?
What are you gaming on?
What are you pinging when you see the slow down?
My laptop and desktop.
Just gaming only. Other people around are just browsing, and that's it.
I'm gaming on my laptop and desktop. Works fine when plugged in. Less than 5 feet away wireless, and it hits some huge spikes.
The pings shoot up from 9ms, all the way up to 380+, and then to 4k.
Not sure what caused it though. Was still running the WPA2/AES only.
No lock ups, still. No GUI slow downs. Just high latency at random times. Dropped packets are still huge though.
-
Just updated myself July 10th 6pm pst
Will keep you posted
-
I've upgraded with this v1.21b02, but the Shareport issue STILL EXISTS. I still can not use my printer via the Shareport after 3~4 hours until I reboot the router. Then I can use my printer for around 3~4 again. Please note that I didn't have this problem with firmware v1.15 & 1.13 which my router can keep up & running for weeks & months and I could print via Shareport.
-
Updated the firmware on an A1 system.
I noticed Enable Advanced DNS Service is now unchecked. Is it recommended that I also disable Enable DNS Relay, as that option is still enabled?
-
Last night when I went to sleep everything was up and running just fine. When I got up this morning all internet traffic had stopped. Had to do a hard reset on the router.
-
I've upgraded with this v1.21b02, but the Shareport issue STILL EXISTS. I still can not use my printer via the Shareport after 3~4 hours until I reboot the router. Then I can use my printer for around 3~4 again. Please note that I didn't have this problem with firmware v1.15 & 1.13 which my router can keep up & running for weeks & months and I could print via Shareport.
I have the exact same issue.
-
Just out of curiosity now...how many of you have Cable internet or DSL?
Just reply with what you have...
Mine's still working okay. I still have latency spikes over wireless, which I guess is to be expected...but at 5 feet away? Wired still seems to be perfectly fine for everyday general use. Hasn't locked up yet, and hasn't killed the WAN or LAN.
I'll still continue testing to see how gaming holds up, especially during multiplayer. XBox doesn't count. :P
Also, for those of you who are wondering - I do NOT use the Advanced DNS features, but instead I decided to use the OpenDNS servers instead. They seem to be working better with DNS relay.
-
Cable modem here.
Advanced DNS is off. DNS relay is on.
-
Ok, this is wierd.
The OLED lights up randomy and STAYS on. This would be cool if it displayed the clock, but it only stays on for showing me the WiFi Pin.
Anyone else having this?
-
Ok, this is wierd.
The OLED lights up randomy and STAYS on. This would be cool if it displayed the clock, but it only stays on for showing me the WiFi Pin.
Anyone else having this?
I did have that happen. But I had to do a restart and it did not come up again.
-
On cable here and been running fine for me i have an A1. and the 1.20 firmware for me locked up after every 10 days or soo. this seems to be working good so far.
-
I have cable internet.
I had to do a hard reboot today again. It seems mine needs a reboot every 24 hours.
-
Running Verizon DSL 3.0 MBps with Windows 7 on both my main system and my laptop.
Since I installed Windows 7 on my laptop which is connected directly to my TV and I've been actively using Wireless for streaming videos. The TV is used as a 32" Monitor. :)
Both the LAN & WAN seems to work OK, but the wLAN is another story. Watching videos on my TV, it's very annoying to have the video breakup or to loose it entirely.
When I had my laptop connected directly using the LAN instead of the wLAN, I didn't have any problems with Video breakup.
-
Cable. I just upgraded to 1.21b yesterday after much looking around at these forums from 1.20.
After I upgraded , it would not let me access the internet from my computer which is wired to the router. I had to go to my sons, which is wireless. After about 30 minutes of getting aggrivated, I rebooted the router very fast 10 times. Whoo hoo, I could get on. But alas, it killed my wireless. i have had no luck getting it to work. So now I'm off to a store to go buy another router. Good Luck D-link getting the firmware fixed for the DGL-4500.
P/N BGL4500ANA...A1
S/N F30B179000744
-
I loaded 1.21 on my router.
I've disabled INFO logging, even though I now have it all being sent to a syslog-ng server on the local lan, I noticed the router was still keeping in memory its log entries. Having the logging reduced kept my router running longer, 8-10 days at a time, versus having it lockup within 3-4 days with out of memory issues.
I reenabled the NTP update to see whether that'll work or not. I had issues with 1.20. It seems the router has issues doing DNS queries to LAN side DNS server.
The router itself feels less responsive than 1.20. It's slower in displaying the login screen and the various pages. I've been noticing pauses in viewing youtube videos, although I'm not sure whether that can be attributed to the router or not.
Haven't seen too many issues with either Xbox or VOIP/UMS traffic, but it's only been a couple of days since I've loaded it on.
EDIT: Nope, NTP updates still fails.
(double timestamp due to router not being able to update its own time correctly)
Jul 12 16:35:58 192.168.0.1 Sun: Jul 12 08:07:31 2009 Sanity System Log: Unable to find DNS record for time server time-a.nist.gov
And yes, the named can be queried from anywhere, including the router IP address. If the port was open on the router, you could query the named from the internet. I'm not even seeing the query within the named log in debug mode so the internal routing isn't working.
I check the Routing and I see the following:
192.168.0.0 255.255.255.0 0.0.0.0 1 LAN System
So it should be routing the DNS queries correctly to 192.168.0.101
Local query of the DNS I'm running locally shows:
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1729
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;time-a.nist.gov. IN A
;; ANSWER SECTION:
time-a.nist.gov. 1765 IN A 129.6.15.28
;; Query time: 0 msec
;; SERVER: 192.168.0.101#53(192.168.0.101)
;; WHEN: Sun Jul 12 16:42:24 2009
;; MSG SIZE rcvd: 49
I tried setting it to the dlink NTP servers, and no dice.
-
What wireless client are you noticing the slow down?
MacMini with Mac OS X 10.4 Wireless
HP Laptop with Windows XP Wireless
Desktop with Windows XP 64bit Wired
What exactly are you doing when you notice the slow down? is it just gaming?
- Turning on the MacMini for the first time after it's DHCP address has expired.
- Upon new request the router locks up and refuses to provide my mini a new addy.
- I try to access the router web-client from another machine to check logs and the web interface doesn't respond.
- THe entire LAN performance begins to degrade and neither wired or wireless have internet access
- All internet access freezes until I reboot the router
After reboot:
- My MacMini expired address finally renews and obtains an address
- Internet access is restored to all machines wired/wireless
- Router web interface is accessible
In addition to this instance, I've also caught the router freeze while copying files from my linux samba file server to my MacMini. I occasionally stream video from my samba server to my macmini. During transfer the router will lock up just as previously mentioned and I have to perform a hard reset on the router.
What are you gaming on?
I don't game that much. I've never experienced issues while gaming.
What are you pinging when you see the slow down?
I ping the router to see if it's responsive when the network stalls. I can tell immediately there is an issue as it times out or responds with a huge delay.
-
Okay...
Update #3:
Wired is still okay. I'm noticing that UPnP is STILL broken, and causes entries to be added, renewed, and deleted immediately.
DD-WRT has a nice UPnP section, where it will name the program/application and ports and protocol. And it also has a delete button. As I've mentioned before, it would be nice if you could do the same thing, and have it close when it's told to, or open...or heck...not delete entries upon rebooting of the router.
I ended up gaming a bit more early this morning. Wired started to see a slow down. And so did wireless. I got a spike to a Los Angeles server of 1439...over wireless. And wired shot up from 7ms, to 41. GameFuel was left at default, as it SHOULD work out of the box.
-
well.. I noticed the delays over wireless myself :-[ All the feedback here will be forwarded to PM. Thank you for posting.
-
The new firmware released last week does not solve the 3 day lockup. 3 days on the nose it just locked up again. I've talked to a couple of others who also have the same problem.
-
3rd day in a row that I have to reboot it have 24 hours because all Internet traffic stops.
-
While I've never experienced the lockup problem, my WLAN performance is MUCH MUCH worse since upgrading to v1.20 and the problem continues with 1.21b02 Beta 1. Wireless N range seems to be drastically reduced, as well as throughput. Errors are sky high. I've been forced to move my DAP-1555 that my home theater uses closer to my DGL-4500 because of this. At least with 1.21b02 Beta 1 the connection doesn't seem to totally die like it did with 1.20, but it still isn't very good. I am glad that almost everything is connected via the wired LAN otherwise I would probably be buying a new router at this point.
I am using the AT&T U-Verse DSL service for my connection.
-
I'm considering just removing this router all together. It's plagued with problems and in addition to the issues mentioned in my previous post, it still stalls every few days. It's unfortunate as this router has really cool hardware and features, but the firmware bugs far outweigh the benefits. I wouldn't consider moving my entertainment system just for the sake of keeping a sub-par router. All I want now is a gigabit router that supports DDWRT.
-
Just to make sure we're clear on what some of you have tried.. For those that did upgrade to 1.21b02 beta 1 What HW version is your unit?
Did you upgrade the firmware and then reset the router to factory?
Did you build config from scratch?
-
This morning the router needed to be unplugged, due to the same issue as with beta 1 (no Internet access/cannot access router interface through web). The router was fine, with the exception of some slowdowns, since 7/11.
A1 version. Reset router to factory default prior to updating from beta 1 to 2. Loaded beta 1 config file afterwards. I'll try resetting to factory default and create the config from scratch.
-
I am on the 4th day of having to reboot it in the morning.
Mine is a A1,
I upgraded to the 121b02 but did not reset to factory default. When I upgraded I loaded a saved config.
I will reload the newest FW and reset to the factory and then build my config from scratch when I get home tonight and see what happens
-
I have an A1 and I resetted to factory settings
-
My router reboots multiple times an hour.
This is really frustrating.
It had uptimes of MONTHS with 1.15. 1.20+... not so much, unfortunately.
I need to get this resolved. I have a Samsung UN55B8000 television which will soon support BlockBuster movie streaming, and a Playstation 3 that I would like to use online.
This needs fixed. In the interim, I am looking for a good router to run DD-WRT on. :)
I appreciate the efforts in resolving our issues. Please, keep it up!
-
don't know but for me its working fine no drops yet except for wireless
LAN Statistics
Sent :12330443
TX Packets Dropped :8
Collisions :0
Received :15627152
RX Packets Dropped :0
Errors :0
WAN Statistics
Sent :15589888
TX Packets Dropped :0
Collisions :0
Received :16137279
RX Packets Dropped :0
Errors :0
Wireless Statistics
Sent :14699
TX Packets Dropped :1
Received :4014
RX Packets Dropped :0
Errors :1564
-
I installed 1.21b02 on 7/9 soon after if was made available. Running for over 5 days now with no issues.
The previous v1.20 would require reboot every 3-4 days for me. There has been no need to reboot, and the router seems to be more responsive during general use (browsing, gaming, etc.). Stats show 0 WAN and Wireless errors, with 3 dropped packets on LAN.
To be fair, most of my computers are hardwired with 1GB network, including the PS3s. Only wireless use is when I'm wandering about with one of the notebooks and I generally connect through a DAP-2553 access point instead of the DGL-4500. The DAP-2553 is physically positioned to provide a little better signal strength (5 verses 4 bars) in most areas I use wireless. Both the 2553 and 4500 Connect at 270Mbs by the way.
I thought I had an issue with the upload speed being half what it was with 1.20, but that soon fixed itself....must have been a coincidental ISP problem.
So far, I'm happy.
-
Well.. that makes 2 users that are happy so far.. Please keep us posted if anything comes up. What ISP do you guys have?
Wireless will always have dropped packets because, well.. its wireless.
Still trying to hammer out the 3-4 day issue that some of you are still seeing. Please let me know how it goes after you reset the router to factory and build the config from scratch.
-
Using Comcast DOCSIS, 50mbs down, 10mbs up.
-
Wireless Statistics
Sent : 3942640 .
TX Packets Dropped : 17459
Received : 2296862 .
RX Packets Dropped : 0 .
Errors : 27364 .
-
Time Warner Cable - RoadRunner Turbo with SpeedBoost (28Mbps burst down, 1Mbps up).
Ambient temperature: 85 degrees Fahrenheit (since some people mentioned overheating).
-
well i have optimum online boost 30mbps down 5mbps up
-
Just reinstalled the latest firmware. Restored to Factory, Then rebuilt the config from scratch.
I will report if I have to reboot in 24 hours.
I am with Mediacom in Des Moines, IA. I have their online max. 20 mbps up, 2 mbps down
One thing I did notice is I no longer have the Captcha security login.
-
I just replaced this router with a competitor's "N+" router for the time being. It has comparable features (for what I use).
I'll be keeping an eye out here for progress! Please let me know if there is anything I can do to help development of this fix.
-
One thing I did notice is I no longer have the Captcha security login.
Kneo, Captcha is off by default when resetting. You might have already found the option but, if not, you can enable Captcha by going into Tools/Admin and checking Enable Graphical Authentication.
-
Router just spontaneously rebooted.
Nice thing about syslog, it records it without having to rely upon the router's memory or sense of time to be correct. I found it interesting that the secondary reboot caused the router to have the EXACT SAME timestamp within the router from the previous reboot. The memory is corrupt or not saving correctly.
Jul 14 10:21:48 192.168.0.1 Tue: Jul 14 10:21:46 2009 Sanity System Log: LAN interface is up
Jul 14 22:13:07 192.168.0.1 Tue: Jul 14 10:21:46 2009 Sanity System Log: LAN interface is up
The timestamp on the left is the syslog-ng timestamp, the timestamp on the right is what the d-link router thinks it is. The left is correct since it can actually talk to NTP servers, the one on the right shows the dlink has alzheimer's.
I guess this is an improvement over having it lockup and forcing a powercycle...
Hardware is HW Ver: A1. I always factory reset on firmware upgrades, including disconnecting everything from the router except 1 computer which inputs the config from stratch. I've had too many issues with firmwares past 1.02 to take any chances.
-
I've noticed that every 5days??hrs I see a ton of IP protocol 6 and IP protocol 17 coming from the dap-1522 that is in bridge mode (5GHz).
Could this be a dap-1522 problem?
-
Even after resetting to default and building the config from scratch, we still ran into the issue (internet not being accessed/no web access to router interface) late this afternoon.
-
Had to reboot after less then 48 hours running. Same as before all internet traffic stopped.
I have tried to have patience and wait for a fix, but it has been almost a month now. If a fix does not come soon I will be looking for a non dlink router.
I implore you to please find a fix for this.
-
Keno are you a a1 user?
-
Yes. I am a A1 user.
-
Well, ran for a little over 7 days with no issues when the router automonously rebooted itself. I guess thats better than having a hard lockup requiring a manual power cycle every 3-4 days that I was experienceing with 1.20.
Only issue was that the wife was online at the time it rebooted and she came outside and chased me around the yard (with a stick) for a bit screaming THE INTERNET IS OUT ... THE INTERNET IS OUT. I just told her it would come back soon and she went off to sulk...going to be lonely tonight.
I did notice that after the automatic reboot the router did not come up with an uplink speed measurement (under gamefuel). I set a manual uplink speed to prevent that from becoming an issue if the router auto reboots again.
Other than that, router has been working great with 1.21B02.
-
I have an a1 router and mine has worked pretty well with this latest build. I did have some slowdown with wireless after the router had between 3-4 days uptime after loading the firmware. I rebooted and everything has been fine. I'm currently at 3+ days again so I'll see if I get the slowdown once again. I haven't noticed any random reboots (yet). One thing I did notice (and I've since hooked my printer up another way) is that when using shareport I'd have to reboot every few hours in order to switch use on different pcs. It was a major pain and I hooked my printer up another way because I got tired of constantly rebooting.
-
For those who are stable with the latest beta, and have an A1 version, are you running either Advanced DNS or DNS Relay, or are both options disabled?
-
I upgraded to this firmware (from 1.20) last night, by 9 this morning when I woke up the internet was out on it, and could not access the router page. On the OLED I can now scroll through all of the options without it crashing (with 1.20 it will reboot when you scroll past the clock to the log section). In the log section there were many similar messages to "Could not open session from 192.168.1.1 (router ip) to 192.168.1.X" or something to that effect. Hope this helps. Version A1.
-
For those who are stable with the latest beta, and have an A1 version, are you running either Advanced DNS or DNS Relay, or are both options disabled?
Advanced dns off, dns relay on for me.
-
Well I hit over 4 days uptime, and started experiencing major slowdowns and I now cannot access the user interface for the router. I'm going to have to unplug it to reboot it now.
**edit**
I tried one more time to access the user interface and it came up (I noticed the past few hours that sometimes it would and sometimes it wouldn't). I did a reboot from the system tab and it is now running quick as ever again. Very strange.
-
Still rebooting about every 8 hours with the new 1.21b02 :-\
-
I've already reported complete internet issues, but this will give you an idea of the timeframe between lockups (last reboot on 7/15). Logs entries kept referring to Internet Protocol 6 again, and the unit needed rebooting just a few minutes ago.
Just an FYI on what's accessing the router: PC wired to LAN, laptop accessing wirelessly along with two iPhones. Internet provider is Comcast.
-
I was using 1.15 before today, I decided to upgrade the firmware because for some odd reason when I do uploads, my lag is just insane (when the upload is maxed).
Bad idea. I upgraded to 1.20 (release) and my wireless kept getting disconnected.
So now I am trying 1.21b02 and I loaded my old configuration and disabled "CAPTCHA" and guess what-- when I try to log in now, even though there is no field for the captcha or captcha image, it keeps saying 'I have not entered the graphical authentication code' (doing this on LAN)
As well my speeds seem to have dropped by 2Mbps (16Mbps max which is what I used to get in 1.15-1.20))
What the hell is going on and how do I fix this?
P.S. What is the "A1" version and how do I check what version I have?
-
Just look on the router body and you'll see a white label with sn and hardware version. This will tell you what you have.
-
Okay, it looks like I have the hardware version: A1.
And I reset the router, loaded my config (with CAPTCHA enabled) and it seems fine, however I go major issues with my wireless.
My wireless connections keep getting dropped - this only started with the 1.20+ upgrade.
Please tell me this is fixable because its getting insane.
-
I as well have an A1 but with this beta fw that i put in this morning with a factory reset ... the damned router wont' stay on for longer than 5 mintues.
It is also extremely hot to the touch. I placed it in the fridge for about an hour then I was able to use it for 10 min before it locked up again ... :'(
There's got to be an answer to this ... and i think we all might know what it is.... >:(
-
I as well have an A1 but with this beta fw that i put in this morning with a factory reset ... the damned router wont' stay on for longer than 5 mintues.
It is also extremely hot to the touch. I placed it in the fridge for about an hour then I was able to use it for 10 min before it locked up again ... :'(
There's got to be an answer to this ... and i think we all might know what it is.... >:(
That is not a very good thing to do to electronic items.
-
I am still rebooting every 24 hours. I even reinstalled the latest F/W and rebuilt my config from scratch for a second time.
-
Okay, it looks like I have the hardware version: A1.
And I reset the router, loaded my config (with CAPTCHA enabled) and it seems fine, however I go major issues with my wireless.
My wireless connections keep getting dropped - this only started with the 1.20+ upgrade.
Please tell me this is fixable because its getting insane.
That's why you shouldn't load your config. Binary mismatches between different versions can cause problems. That was your own fault.
-
well this is definitely working better for me :)
no slowdowns at the moment, the only things i noticed are:
1) dns relay has (!) to be activated for me or else Browsers won't work (ICQ, MSN etc. still do)
2) Gamefuel says "measuring" at booting but "unestimated" on Advanced Page ... (setting up manual now)
-
That's why you shouldn't load your config. Binary mismatches between different versions can cause problems. That was your own fault.
Hello,
Is this in regards of the CAPTCHA or the wireless disconnects?
Even if it was regarding the CAPTCHA, D-Link could add a simple line of code that "prevents" people from loading "incompatible" configs - if it truly can cause such problems. Even if you are changing the "base" code you can still make a config file compatible with the new code, unless they are storing it in a fashion that prevents this - which then the question should be asked, why? Why store it in this manner.
Thanks,
Aaron
-
1.20 HAS CAPTCHA enabled by default. NEWEST Beta has it DISABLED by default. There's your code change right there.
Again, that was user error on YOUR part. Not D-Link.
As for the Beta. I finally got it to lock up at 4 days. It completely killed the WAN and caused it to show a default IP address of 192.168.0.1 in the status. Connection has been mostly idle. It's not hardware specific at all. ;)
-
If your browsers are not working without DNS relay reboot your computer after changing the setting and I bet they will.
-
Fatman's post reminded me to try turning off DNS Relay. I'll see how the router runs with this option off.
-
I had to do a hard reset of my router this morning when I woke up. Worked fine when I went to bed. Couldn't get on the net when I woke up. Tried rebooting the router and the modem and it still wouldn't work. Noticed the date and time on the router was stuck on Friday for some reason. Finally got it to work after the reset, but I had never experienced that before. I'm not one to complain, but these constant reboots and problems are really getting old. I hope a good, solid fix is in the works.
-
Still rebooting about every 8 hours with the new 1.21b02 :-\
me too >:( on A1 but the reboot doesn't always work for me... I have to power it off for a few hours then it'll relink when it comes back up.
-
Is there any head way on this?
I have rebooted quite a few times since upgrading to this version on the 10th july
My results are the same as before.
Situations are still the same.
Un update built new con-fig
I have tested with advanced dns on and off.
It is an A1 model like stated before.
I will add my downloads via wireless has 25% of what it used to be.
Not that i see a diffrence on normal use but downloading large files to my laptop is at quater of what it was with the last firmware.
Sorry i can not sit around testing all day that is not my job.
I don't thing paying $200 for a router then having to troubleshoot for months is right.
You should realy should offer replacements for people to at least go back to a stable version this it becoming to much and staining the Dlink name.
There should be a mind set on how can we make our coustmers continue to talk about us in a possitive way rather then negitive spin we have been getting.
Give us somthing good to talkabout inspire some hope.
I'v been dealing with this since the firmware became an offical release like others here its not been a good run.
-
If your browsers are not working without DNS relay reboot your computer after changing the setting and I bet they will.
Well ...
I had it disabled using 1.21b01 and disabled it again after upgrading to b02 ....
When I disabled it the first time under b01 there was absolutely no reboot neccessary (only a simple ipconfig /release -- /renew ...)
---------------------------------------------------------
But still .... new fw. is working great for me
-
Ran for 5 days this time, then router automatically rebooted. I have not had to do any manual power cycles, but the router has automatically rebooted twice, once after 7 days, then again after 5 more days.
Not really a problem since the router is working fine otherwise. To be fair, I don't use the 4500 wireless much since I wirelessly access via a DAP-2553 access point which shows up as a LAN connection in the 4500....do have a lot of stuff on the wired LAN though.
1.21b02 is still the best for me after losing 1.02
-
After 4 days of uptime (with the constant disconnects of my wireless net) the router suddenly locked up today.
I've never had this issue in 1.15 (I had it in previous firmware versions, but not in 1.15), it seems to be a 1.20+ related issue.
Rebooting seems to bring things "back to normal" however I am going to see how long it takes for the router to lock up again.
-
This is ridiculous perhaps its time to clean house and get programmers that can actually solve this problem. Long time with no solutions in sight. Sad to pay 200 dollars for something that is nothing but rubbish.
-
Well finally had to do a manual power cycle with 1.21b02.
Went for 7 days then automatic router reboot, another 5 days, another automatic reboot, then 3 days and had a hard lockup (no connection available, including router gui) requiring manual power cycle.
A little better than the required manual power cycle every 3-4 days I was experiencing with 1.20, but still needs work.....
-
I noticing worsening conditions with my router. Each power cycle is causing degraded performance. Right now any file copy between any 2 LAN computers causes the router port to lock up. Windows file sharing is all but useless right now. I'm not even stressing it at GB speed, this is at 100MB speeds.
I had more success with 1.20 versus 1.21b02. You've returned me to 1.15 levels of instability, in which the LAN ports lock up after a while under heavy use.
I have DNS relay disabled and wireless disabled, and the router can't even handle LAN connections. This isn't even under heavy load. I've resorted to copying files through my actiontec router an alternate subnet.
-
From 4 days, to 3 days and now just below 3 days of up time, my router keeps locking up. Cannot access the router page at all and I have to reboot it constantly.
-
Same here getting about 3 days before needing to hard reboot.
almost 2 days up and my statistics look like this (note the wiress drops)
LAN Statistics
Sent :2531576
TX Packets Dropped :13
Collisions :0
Received :1842773
RX Packets Dropped :0
Errors :0
WAN Statistics
Sent :1291197
TX Packets Dropped :0
Collisions :0
Received :3862980
RX Packets Dropped :0
Errors :0
Wireless Statistics
Sent :689668
TX Packets Dropped :191
Received :428643
RX Packets Dropped :8871
Errors :25359
-
Before 1.20, Zero, none, nada, absolutely no wireless problems.
Now:
LAN STATISTICS
Sent :664786
TX Packets Dropped :4
Collisions :0
Received :782349
RX Packets Dropped :0
Errors :0
WAN STATISTICS
Sent :1915662
TX Packets Dropped :0
Collisions :0
Received :2521558
RX Packets Dropped :0
Errors :0
WIRELESS STATISTICS
Sent :1888443
TX Packets Dropped :13709
Received :1137766
RX Packets Dropped :0
Errors :42
Wifi drops like every 10 minutes, then instantly reconnects.
DGL-4500 A1.
-
any update from D-Link officials? I've had problem with 1.20+ firmware for quite a few weeks now. Is it impossible for them to release a downgrader to 1.15? Sounds like some people who have gotten A2 unit from moderator stopped aggressively pursuing this issue, does that mean we should do the same?
-
Well yeah because the a2 unit works. Mine came with 1.12 but I flashed to 1.16b3 and guess what? No lockups, no reboots and no downtime because of the router. I can load any page I want and it works everytime unlike my a1. If you're having trouble with your a1 you should contact d-link customer support and explain your situation to them. They may or may not help you but you'll never know unless you pick up the phone and call them.
-
Well yeah because the a2 unit works. Mine came with 1.12 but I flashed to 1.16b3 and guess what? No lockups, no reboots and no downtime because of the router. I can load any page I want and it works everytime unlike my a1. If you're having trouble with your a1 you should contact d-link customer support and explain your situation to them. They may or may not help you but you'll never know unless you pick up the phone and call them.
I've been using the A2 unit as well, and it's been working flawlessly I flashed to 1.15 soon after receiving the unit. here are some stats after nearly running continuously for nearly 4 days.
TRAFFIC STATISTICS
Traffic Statistics display receive and transmit packets passing through your router.
LAN STATISTICS
Sent :412727
TX Packets Dropped :5
Collisions :0
Received :4791
RX Packets Dropped :0
Errors :0
WAN STATISTICS
Sent :1141613
TX Packets Dropped :0
Collisions :0
Received :12263841
RX Packets Dropped :0
Errors :0
WIRELESS STATISTICS
Sent :8543563
TX Packets Dropped :94
Received :7791407
RX Packets Dropped :204
Errors :14142
Copyright © 2004-2008 D-Link Systems, Inc.
-
If you are an owner of a D-link product with hardware/firmware problems that are still unresolved despite all your efforts to have them resolve them or if you have recently upgraded your firmware only to have your router become useless or not perform as advertised. Immediately follow the instructions below and wait for more details on a website that is being developed now to assist you with these problems.
In the meantime...you need to do the following immediately.
1). File a complaint with the Better Business Bureau at www.bbb.org (this will get an immediate response from Dlink and replacement of your router - at least for now)
2). File a complaint with the California Department of Consumer Affairs at http://www.dca.ca.gov/online_services/complaints/consumer_complaint.shtml
3). File a complaint with YOUR state's consumer affairs.
4.) File a complaint with the Federal Trade Commission at https://www.ftccomplaintassistant.gov/FTC_Wizard.aspx?Lang=en
5.) File a complaint with Rippoffreport.com at http://www.ripoffreport.com/login.asp
You may use the complaint text for each one (that way it saves you loads of time). Also save your paperwork and all emails, conversations, phone records...everything! Do NOT dispose of, sell, trade or otherwise let the hardware go as this may become valuable evidence for authorities. If you need help filling out the paperwork you can ask at the sites listed below and someone will help you.
Your warranty status does NOT matter. Facts are if the firmware update that D-Link provided caused the damage they are liable to fix and/or repair the damage in a reasonable period of time. Almost 3 months is not reasonable.
More on the self help website will be announced shortly. In the meantime you need to immediately file the complaints above and SAVE EVERYTHING including all emails to and from D-Link!
You can also find more information at Broadband reports in the following thread:
http://www.dslreports.com/forum/r22572439-DLink-Banning-Users-and-Deleting-Posts-Critical-Of-DLink
Or at ISPgeeks.com at:
http://www.ispgeeks.com/wild/modules.php?name=Forums&file=viewtopic&t=2888#10001
-
Wonder when those with the A2 units will tell us how great it works when you flash it to f/w 1.20+
May come as a shocker but many A1 units also didn't lock up with 1.12-1.16b.
-
Wonder when those with the A2 units will tell us how great it works when you flash it to f/w 1.20+
May come as a shocker but many A1 units also didn't lock up with 1.12-1.16b.
There will be NO flashing beyond the 1.15 for me, at least in the interim
-
Well my a1 with 1.16b3 worked pretty good but the throughput was sluggish compared to 1.02 or 1.2x but it did not require a reboot. Now it did crash loading rtsp pages with 1.02 and 1.12 seemed to fix that but brought other problems that did not lockup or spontaneously reboot the router until 1.2x. I refuse to flash any higher than 1.16b3 on my a2 as it works fine for what I do however I don't use wireless so I cannot comment on the performance of it. I can only hope that d-link is able to resolve the issues with the dgl-4500 and return it to a continuously functional device for the sake of all who've bought it.
-
I am giving it one more week, if there is not a fix by then I will be purchasing a new non-D-link router. I will also be telling all my friends and family not to ever buy D-link products.
I hate to do this because I have always been a D-link fan, I have been using only D-Link products for years but unfortunately in this world one mistake can ruin a good name. It is been over two months since this problem began and the only two fixes that were suppose to work, didn't.
-
After a few days of uptime, I finally got my router to kill the WAN. It did not however reset, and go through the boot sequence. Just disconnected, and reconnected. GameFuel problems, and filling of statetable.
-
After a few days of uptime, I finally got my router to kill the WAN. It did not however reset, and go through the boot sequence. Just disconnected, and reconnected. GameFuel problems, and filling of statetable.
Do you know how many days exactly the router has been up? Was there anything you noticed when WAN died? What type of activity were you doing on you network when you noticed it?
-
For me, the reason I notice the WAN disconnects so easily is because it usually happens while gaming, or when I'm using PuTTY or something that requires constant communication.
However lately I have no idea whats been causing the router lockups, its gotten to a point where just after 24 hours or just a bit above, the router locks up. All connectivity to the router is killed and I need to hardboot it.
-
Do you know how many days exactly the router has been up? Was there anything you noticed when WAN died? What type of activity were you doing on you network when you noticed it?
i've left it plugged in for over 6 days. That's the only constant. I noticed toward the time when it was locking up and disconnecting that it partially killed my WLAN as well, and I was unable to reach the gateway. I could be doing simple streaming, or else just playing a game, or even idle. Statetables still fill up too quickly. UPnP is still broken, and causes a flood of entries when not closed properly.
-
As mentioned earlier, disabling all logging extends uptime by 2-3 days. Previously was performing hard resets every 8 hours, unchecked all logging and now it stayed up over 3 days.
-
I have an A1 with 1.15 firmware and it's worked fine except I can no longer get video to stream to my Wii. I can remote into my home pc from work without any trouble except sometimes it does take a minute to get a response from the router at first. The router has been up for 11 days and 19 hours without a reboot and I play City Of Heroes on my pc all the time with normal operations and my wife is on her laptop working without any noticeable issues. Here are my stats:
LAN Statistics
Sent :16186398
TX Packets Dropped :5
Collisions :0
Received :13828518
RX Packets Dropped :0
Errors :0
WAN Statistics
Sent :13733949
TX Packets Dropped :0
Collisions :0
Received :19570346
RX Packets Dropped :0
Errors :0
Wireless Statistics
Sent :2789303
TX Packets Dropped :0
Received :1869356
RX Packets Dropped :0
Errors :34621
-
As mentioned earlier, disabling all logging extends uptime by 2-3 days. Previously was performing hard resets every 8 hours, unchecked all logging and now it stayed up over 3 days.
My logging has stayed enabled by default because most routers should be able to work at default. (These however aren't with latest firmware)
-
Well, I have an A1 and have been suffering from frequent slowdowns and disconnects. I've done the 30/30/30 reset with no improvement. When I try to log into the router, I have to enter my password 3 times before it's accepted. I'm running Mac OS X and the latest version of Safari, 4.0.2.
I'm thinking about installing ver 1.21b02
-
Well, I have an A1 and have been suffering from frequent slowdowns and disconnects. I've done the 30/30/30 reset with no improvement. When I try to log into the router, I have to enter my password 3 times before it's accepted. I'm running Mac OS X and the latest version of Safari, 4.0.2.
I'm thinking about installing ver 1.21b02
Yeah, I've mentioned that bug in Safari as well. Still seems to occur with or without CAPTCHA.
I've gotten the router to reboot using Safari too. When making a change to the router where it pops up saying clients will get disconnected or that it doesn't require a reboot your router will reboot.
-
My logging has stayed enabled by default because most routers should be able to work at default. (These however aren't with latest firmware)
Don't get me wrong, I completely agree with you on that but at this point I'm willing to sacrifice a bit to keep the router up!
-
And we care about this why? You are in the wrong thread pal, flash your device to 1.21b02, then we'll talk.
I have an A1 with 1.15 firmware and it's worked fine except I can no longer get video to stream to my Wii. I can remote into my home pc from work without any trouble except sometimes it does take a minute to get a response from the router at first. The router has been up for 11 days and 19 hours without a reboot and I play City Of Heroes on my pc all the time with normal operations and my wife is on her laptop working without any noticeable issues. Here are my stats:
LAN Statistics
Sent :16186398
TX Packets Dropped :5
Collisions :0
Received :13828518
RX Packets Dropped :0
Errors :0
WAN Statistics
Sent :13733949
TX Packets Dropped :0
Collisions :0
Received :19570346
RX Packets Dropped :0
Errors :0
Wireless Statistics
Sent :2789303
TX Packets Dropped :0
Received :1869356
RX Packets Dropped :0
Errors :34621
-
Well being that 1.20 is an official firmware and is buggy like no other.. We're going to make this code (1.21)official for the users whom aren't aware of forums and don't know where to get this code. Yes we're still working on a fixing the issues you guys are experiencing. 1.21 addresses other issues in 1.20 which is why we're releasing this code along with in house testing and a couple users that have had no problems with this firmware.
Please do not worry.. we're not stopping on making firmware and we hear everything you guys are saying. We keep a close eye on this thread to see what we can find and we will ask you when we need more info.
So far I have an A1 in house and an A2 at my desk. I'm constantly checking to see if and when it will crash and have yet to see it.
Here are screen shots of my unit from home:
(http://i24.photobucket.com/albums/c43/isoh/status-1.jpg)
(http://i24.photobucket.com/albums/c43/isoh/statistics.jpg)
(http://i24.photobucket.com/albums/c43/isoh/wireless-1.jpg)
The only time I noticed a hardware lock up when the router was not responsive at all was in 1.20 code.
-
Update since turning off DNS Relay: The router has now been running for 8 days 45 min. We still experience slight slowdowns while online, but nothing to the point of complete lockup as before. I'm hoping this isn't a fluke, but I'll see how long the router can stay operating without a need for a reboot.
LAN STATISTICS
Sent :3624123
TX Packets Dropped :3
Collisions :0
Received :1952279
RX Packets Dropped :0
Errors :0
WAN STATISTICS
Sent :6026667
TX Packets Dropped :0
Collisions :0
Received :67911392
RX Packets Dropped :0
Errors :0
WIRELESS STATISTICS
Sent :6437217
TX Packets Dropped :4338
Received :4126301
RX Packets Dropped :6470
Errors :12711
-
So far I have an A1 in house and an A2 at my desk. I'm constantly checking to see if and when it will crash and have yet to see it.
Do you have many of the router "features" turned on/ in use on your A1? DNS relay off?
[joke] Your uptime is 12 day? I smell a photoshopping of what was "1 Day". More than one would be... days (plural). ;) [/joke]
-
EJeanmaire,
I have DNS Relay Enabled, Advanced DNS is off, SPI Disabled and NAT Endpoint Independent for both UDP and TCP... That's all.. To My surprise I thought I had DNS Relay disabled but ah well so far it's been stable for me..
Haha and no I wouldn't do such a thing and photoshop the uptime. I knew someone would say something like that. I'm almost willing to give someone here remote access to my router so they can vouch for me ;)
I wouldn't play you guys like that.. There's no point to it. Bottom line is I would like everyone's router to be fix. Keeping fingers crossed we will find some kind of resolution soon!
-
Ru-Fi-Oh, when do you think the the 1.21 code will be official? I am tempted to update from the 1.20 but the beta download page uses fairly strong language with regard to "use at own risk."
-
Should be up any time soon not sure when exactly.
-
This code just became official..
http://www.dlink.com/products/?tab=3.firmware&pid=DIR-825&rev=DIR-825
http://www.dlink.com/products/?pid=DGL-4500&tab=3.firmware
**Correction! Thanks Reinvented
-
This code just became official..
http://www.dlink.com/products/?tab=3.firmware&pid=DIR-825&rev=DIR-825
Ru-Fi-Oh, that's for the 825. ;) Fix it please!
Otherwise, i'm going to start thinking that all the codes for the routers are the same like what I've seen in the change logs.
-
1.21 can be had from
ftp://ftp.dlink.com/Gateway/dgl4500/firmware/
-
Already I ran into some problems with " Firmware Version : 1.21NA, 2009/07/09 ". Granted I kind of expected this, but the upgrade will of course wipe your settings. Luckily I made a backup. However, I went to try to restore my config settings and I get this ****:
Restore Out of Valid Range
The restored configuration file is not correct. You may have restored a settings file that contains one or more values that are out of the valid range permitted for this release.
Try the restore again with a valid restore configuration file.
Please press the button below to continue configuring the router.
This suxs, I had a ton of reserved IPs and Rules.
-
congratulations on the release, but theres still bugs so don't give up, I know your working on it and am happy it is being resolved, i will be removing my (slow) airport and putting my router back up, huge speed difference which is why i love my dgl4500 :)
Update: set up working wonderfully before was dl 8mbps ul 2mbps, now i can see the difference :)
(http://www.speedtest.net/result/528447021.png) (http://www.speedtest.net)
-
Already I ran into some problems with " Firmware Version : 1.21NA, 2009/07/09 ". Granted I kind of expected this, but the upgrade will of course wipe your settings. Luckily I made a backup. However, I went to try to restore my config settings and I get this ****:
This suxs, I had a ton of reserved IPs and Rules.
That's why you don't restore config files. Binary mismatch from different versions.
-
No Luck for me and I am using an A1 DGL-4500 and this up time sucks bad. I really use my connection a lot and I get 26 mb down and about 30 mb up so when I go nuts it really puts it to work and mine dies in about a day if I really use it. If there is a difference in this firmware I have and the official 1.21 then I will give it a shot but if there is no difference whats the point. I am gonna try and get a new router from D-Link cause I cant use it.
It wont let me post my pictures because I get an error
Here is my routers stats =(
http://eebobb.net/pictures/1.jpg
http://eebobb.net/pictures/2.jpg
-
That's why you don't restore config files. Binary mismatch from different versions.
That's no excuse. My Netgear FM114 and Snapgear SG300 restored configuration files fine in between firmware upgrades.
-
That's no excuse. My Netgear FM114 and Snapgear SG300 restored configuration files fine in between firmware upgrades.
The changes between some of the firmware versions are VERY drastic. It DOES cause a mismatch. And if you write down the settings, it doesn't take long to set it back up. That's fine that your other routers are able to do it, but that's probably because they aren't actively being updated with HUGE changes.
-
The changes between some of the firmware versions are VERY drastic. It DOES cause a mismatch. And if you write down the settings, it doesn't take long to set it back up. That's fine that your other routers are able to do it, but that's probably because they aren't actively being updated with HUGE changes.
You're basically telling me a router shouldn't be able to restore backups?! Or even parse a simple config file and restore previous settings. Most Netgear routers do it, CISCO routers do it, Snapgear routers do it, and any given supported DDWRT routers. My Netgear router firmware upgrades wiped settings all the time, but I could always restore with the original config. What's the purpose of having a 'backup' feature if you can't restore. And yes, if you're somebody that actually uses a router for more than 'gaming', then you will have many settings that require time and several reboots to restore. Original password, DNS settings, time server, SSH, HTTP, HTTPS, Teamspeak, not to mention all the additional port fowarding, filtering, IP reservations, WIFI hostname, WIFI WEP password, syslogging, etc. You may have bought this router for the pretty lights on top, but I bought it to use for work at home. I have several machines I use for development and testing. It's a pain dealing with all the reboots and restoring settings after upgrades.
-
You're basically telling me a router shouldn't be able to restore backups?! Or even parse a simple config file and restore previous settings. Most Netgear routers do it, CISCO routers do it, Snapgear routers do it, and any given supported DDWRT routers. My Netgear router firmware upgrades wiped settings all the time, but I could always restore with the original config. What's the purpose of having a 'backup' feature if you can't restore. And yes, if you're somebody that actually uses a router for more than 'gaming', then you will have many settings that require time and several reboots to restore. Original password, DNS settings, time server, SSH, HTTP, HTTPS, Teamspeak, not to mention all the additional port fowarding, filtering, IP reservations, WIFI hostname, WIFI WEP password, syslogging, etc. You may have bought this router for the pretty lights on top, but I bought it to use for work at home. I have several machines I use for development and testing. It's a pain dealing with all the reboots and restoring settings after upgrades.
Are you that stupid that you can't read? I said that it cannot restore changes that differ GREATLY. The router firmware versions had some huge changes, so it makes sense that you cannot restore settings that weren't in place there previously. It would EQUAL a BINARY MISMATCH. Go look up mismatch or something and figure out what it means. It's obviously not sinking in. Yes, I do work from home also. I'm an accountant. On top of that, if and when I do my testing, I have everything the way I want it. I have over 19 DHCP reservations, and WiFi settings, WPA passwords, etc. Even GameFuel rules.
The reason we EVEN tell you to start from scratch is to alleviate any problems that may arise. What you are essentially doing in your testing is starting from a basic start point, and then configuring to see where there are flaws afterwards. Afterall, this is a BETA and should be TREATED as such.
However, what it comes down to is that you cannot expect it to restore an older configuration file which contained settings that are no longer enabled by default, or that have significant changes to them. None of those other routers you mentioned probably do it either. If they do, I'm sure they are messed up in some way.
-
In all honesty the config backups should work. Even across the firmware versions. We've encoded the firmware so that the newer features are added at the end of the config list. However as a precaution, Reinvented's method ensures that a badly written config file isn't to blame for poor/unwanted router performance.
-
Are you that stupid that you can't read?
Why the hostility? I'm simply responding to your post, without the need to type in caps.
I'm an accountant
Err? Why are you even responding to the posts here? You're not even a DLink developer? I have legitimate concerns here as a DLink customer.
The router firmware versions had some huge changes, so it makes sense that you cannot restore settings that weren't in place there previously
Rather than dazzle me with your divine intellect, why don't you let the techs do their jobs and take the flaming elsewhere.
-
The offical 1.21 firmware on the dlink site, is it the same code at the 1.21 beta? Or is it newer?
Thanks
-
Hello everyone, I am a new member but I have been following these threads for quite some time, I have an A1 version of the router and have experienced all of the problems that have occurred, the slowdowns and lockups. I bought this router last October, so I still within the warranty period right? I have read that they sent out A2 versions of the router to some, does anyone know if those A2 versions are working any better than the A1's? If so, what do I have to do to get one? I have been updating with the newest firmware's as they have come available, and have the 1.21 right now. I have very basic settings, just wanted something with gigabit for the ps3 as well as voip with 2 blackberries, and 2 laptops. Calls get dropped constantly and the on the laptops, some pages load really slowly, or I have to reload. Any ideas?
-
Well regardless of version if you run fw 1.2x you'll have problems. My a1 worked ok until i made the mistake of flashing to 1.2x. I will not ruin my a2 by doing the same thing.
-
Reinvented, is the official 1.21 working better than the beta?
-
don't see adifference other its 1.21NA to be honest
also clock time is right on router webpage but on the device itself its a day behind lol
but that has been issue since 1.2
running the A1 version i can honestly say i have not ahd any major issues other than the shareport issue and router reboots every few days
between 6-12 days that i have noticed in the past 2 months going form official 1.2 and now running 1.21
will give more feedback as time goes on
-
Reinvented, is the official 1.21 working better than the beta?
It's the exact same.
-
Well being that 1.20 is an official firmware and is buggy like no other.. We're going to make this code (1.21)official for the users whom aren't aware of forums and don't know where to get this code. Yes we're still working on a fixing the issues you guys are experiencing. 1.21 addresses other issues in 1.20 which is why we're releasing this code along with in house testing and a couple users that have had no problems with this firmware.
Please do not worry.. we're not stopping on making firmware and we hear everything you guys are saying. We keep a close eye on this thread to see what we can find and we will ask you when we need more info.
Seems it is the same as the beta just "official" now.
-
Yeah that is correct. We won't release official code unless it's been tried out here on the forums then we just make that official. Even though this firmware is not 100% stable it is better than 1.20 and we all know how terrible 1.20 is :'(
-
Have the devs found any reason as to why the 1.20 firmware caused such problems? (and they actually continued to 1.21 for the HW A1 units)
-
I do feel as if the developers are getting extremely lazy. I own several D-Link Routers, all with the same problems. And the firmwares change logs are exactly the same across all of them. Maybe a few changes here and there, but mostly the same. It's disappointing to see it like this, because if you notice, they ALL exhibit the same problems.
-
Lazy i will agree with you -_-. they have over 10 firmware release and yet no fix -_- d link you should really stop trying to fix something that is broken start from scratch and remake the while firmware -_- wasting my time! i don't have much time before my limited warranty runs out and i am left with a junk i am at 1.02 and i get problems not as bad as the people on the forums but bad enough to make me come here into these forums and waste my time that i could be fragging some noobs on call of duty i can't do pros no more they lough at my lag! lol i lough at my lag :'( I am running a a1 unit longest time its been up is 24 days. people recommend me to slam it a bit maybe that will solve all my issues. Lag is no longer an excuse what! it sure is an excuse my isp is optimum its decent enough to frag you Ru-Fi-Oh and lycan! ;D
-
I would guess Dlink had some kind of a licensing issue with the Ubicom part of their firmware (why we can't go back...no longer licensed) and/or an unexpected turnover in their software development staff.
Net result is trying to reinvent the wheel with an associated learning curve.
They are making progress, just wish it could be a little faster. They have been working at it for over a year now, but I believe they will eventually solve the remaining problems.
-
I would guess Dlink had some kind of a licensing issue with the Ubicom part of their firmware (why we can't go back...no longer licensed) and/or an unexpected turnover in their software development staff.
Net result is trying to reinvent the wheel with an associated learning curve.
They are making progress, just wish it could be a little faster. They have been working at it for over a year now, but I believe they will eventually solve the remaining problems.
I wish some people knew what they were talking about before they posted. It's not a licensing issue, period. We simply cannot get the firmware rolled back due to the significant change in the code. HUGE fixes, and even an updated OS for the firmware. That's why. It has absolutely NOTHING to do with licensing.
-
Sorry to disapoint you reinvented, but it doesnt matter how many changes were made in the new firmware there is no technical reason you cannot roll it back. The reloaded firmware (older or newer) will simply overwrite all those massive changes.
It is not a technical reason they prevent it, its a business decision.l
-
Sorry to disapoint you reinvented, but it doesnt matter how many changes were made in the new firmware there is no technical reason you cannot roll it back. The reloaded firmware (older or newer) will simply overwrite all those massive changes.
It is not a technical reason they prevent it, its a business decision.l
Wow man, please just stop talking out of your ass. It wasn't even a business decision either. Get your facts straight. There were so many more vulnerabilities with the older firmware. This whole firmware debacle STARTED with 1.10. But since you seem to know so much about coding how about YOU give it a shot then, and tell them how they should be able to just roll it right back to previous decisions.
-
Wow man, please just stop talking out of your ass. It wasn't even a business decision either. Get your facts straight. There were so many more vulnerabilities with the older firmware. This whole firmware debacle STARTED with 1.10. But since you seem to know so much about coding how about YOU give it a shot then, and tell them how they should be able to just roll it right back to previous decisions.
Why are past firmware still up for download (1.02, 1.12, 1.13, 1.15, 1.20) if they contain so many vulnerabilities?
You seem to be someone who works for D-Link that can give an answer to this question.
You’re taking the whole roll back talk to literally. People would like to use a f/w that worked for them in the past as oppose to the ones not working for them now.
They can re-do (which would probably take time) the old code to be done over whatever is currently in the h/w.
This may shock you but some of us have written software code for hardware before. Of course everything is not done the same, but to think others may not know of what is said is really un-called for on your part.
-
I do know what to say to that myself why do they still offer all the old vulnerable fimwares for download i mean when i did my routers firmware i did them one at a time cause i'm constantly looking for updates and i mean other than packet loss being high on wireless everything else seems to be working going to check my total uptime on the router right now...
and its still rebooting its self it seems on a daily basis for me 4 hours ago and then course my rotuers date being a day behind what the interface give me
-
Wow man, please just stop talking out of your ass. It wasn't even a business decision either. Get your facts straight. There were so many more vulnerabilities with the older firmware. This whole firmware debacle STARTED with 1.10. But since you seem to know so much about coding how about YOU give it a shot then, and tell them how they should be able to just roll it right back to previous decisions.
They already know how to roll the firmware back, they just won't allow it.
Reinvented your demonstrated technical prowess illustrated by your many posts in this forum is impressive especially considering you are an accountant and not a technical professional.
I am a graduate engineer with many years experience in both engineering and engineering management positions with a major aerospace company responsible for developing many systems similar to and incredibly more complex than the DGL-4500. I do know how these things work, both from a technical and management perspective. Suggest you stop the flaming unless you have something positive to add.
That said, the current v1.21 is clearly the best of the bunch from 1.10 to 1.20 and I don't feel the need to roll back anymore. If they really blow it out of the water, I still have my spare shrink wraped DGL-4500 with v1.02 to falll back on.
As I stated in my earlier post, Dlink has made good progress with v1.21 and I believe they will eventually resolve the remaining issues.
-
The only reason I can see why there might not be able to roll back is because they changed the way the firmware updater works.
Technically, if it stores the uploaded firmware in memory and flashes the old firmware - it should be downgrade-able. At the end, its the code. So they must have changed some code dealing with the upgrading/flashing of the firmware, more so the installation of the firmware than installation.
Obviously, I could be very wrong.
P.S. I managed to get my unit replaced without proof of purchase, since I went to the RMA location and gave in the unit manually and etc. So far HW v2 is running well except for the fact that it has an amazingly annoying high pitched sound which I am SO hoping will somehow disappear, if not, hopefully I can get this unit replaced.
-
I am still having issues. The router at times seems to lock up completely - all connectivity to anything just disappears.
I have just enabled DNS relay, and have rebooted the router and cleared the statistics after reboot. Now, my stats are as follows:
(I tried to upload a Screenshot but it would not allow me to....)
LAN Statistics
Sent : 13472 .
TX Packets Dropped : 0 .
Collisions : 0 .
Received : 10558 .
RX Packets Dropped : 0 .
Errors : 0 .
WAN Statistics
Sent : 7463 .
TX Packets Dropped : 0 .
Collisions : 0 .
Received : 35102 .
RX Packets Dropped : 0 .
Errors : 0 .
Wireless Statistics
Sent : 87 .
TX Packets Dropped : 0 .
Received : 0 .
RX Packets Dropped : 0 .
Errors : 0 .
I'll keep monitoring.
I downloaded the official release 121NA - is this in any way different from 121NAb02? If not then I'll stick with what is installed, as I don't want the hassle of setting everything up again, although I noticed that the changelogs are different (less info in the official release).
-
I wish some people knew what they were talking about before they posted. It's not a licensing issue, period. We simply cannot get the firmware rolled back due to the significant change in the code. HUGE fixes, and even an updated OS for the firmware. That's why. It has absolutely NOTHING to do with licensing.
Reinvented. You may want to check that angle out for yourself. There's more to it then you may know. ;)
As for the rest of you, I'm locking this thread. It's become useless to the OP and is way off topic.
-Lycan.
UPDATE: Any issues seen in v1.20 and v1.21 builds have been fixed and are in v1.22 and v1.23 which is the last build for this model router. It works best on Rev A2s