-
Post you feedback and comments here.
-
First let me say THANK YOU!
Now...
Who among us are going to be the Ginnie Pigs? If there are not enough volunteers I'll put my money where my mouth is, but I'd like to know a few things first.
Can this firmware be Downgraded? If so, to what limits.
Should this Firmware be done with a complete config redo or can it load saved settings without issue?
How many Official testers from Dlink are there? Are they testing all hardware versions?
I know you stated you've done basic testing to insure it wont brick devices, however in the off chance it does will you be giving RMAs?
Again Thanks!
-
Hi,
I jumped the gun and flashed. It took at least 7min after flashing count down before it booted. I restored configuration with no problems. Wireless signal at 94%. I'm seeing a lot of TX dropped packets in the wireless as well of RX packets. Any thoughts? Thanks for the beta hope it fixes our problems...
-
I'm assuming Reinvented already upgraded. He's a trusted Beta tester outside of D-Link. It's totally up to you if you want to upgrade and wait for other peoples feedback.
This firmware can be only downgrade as far back to 1.20
You should be able to load a config from 1.20. However, since 1.20 is apparently buggy I would do from scratch anyways.
There are a couple D-link testers for the DGL-4500 firmware. We divided them by router class.
Packet drops can be caused by anything in you wireless environment.. Test out the performance and see if you notice a difference
-
Hi Ru-Fi-Oh, and others,
I just flashed to it. Immediately, I noticed some quirks with the CAPTCHA authentication. One being, it kept telling me that I did not have enough permissions to perform certain actions such as making a GameFuel rule. Even though I was logged in as an administrator.
That is actually VERY annoying, and should be addressed. However, in my honest opinion, and maybe some others - take it out. It's absolutely useless, and is only a hindrance for users who cannot read it very well, and it's not a very good way to stop people from breaking in. The rule of thumb is you should have a good strong password for it, and that's it and you should never have to worry.
The conditions for it to bug out may be leaving it on, and rebooting it later after some major changes to the settings. Again, take it out.
Gaming has yet to be tested, as I just finished a few minutes ago.
I will update my post with more stuff as it shows up.
One of the BIG things that we should test right now is UPnP functionality, as it hasn't been working. In my opinion, this is the reason as to why the router stops responding to WAN and even LAN. Try it out with uTorrent (it should be fine). Do however make sure that in order for you to get UPnP to work properly, you need to make sure there is no port forward rules for it, and that UPnP is checked in the uTorrent client.
Update #1:
Okay guys, I've already finished by battery of tests for the router. So far, the wireless portion still unfortunately sucks. Whether it be 2.4 GHz N/G mixed, or G and B mixed, or G only. Encryption I've always left the same (WPA/WPA2 and AES/TKIP), since this will kinda be a standard for those who have legacy clients who can't quite support WPA2 or AES only. The wireless speeds suck still, and performance drops off almost immediately. When I test, I do not even bother with 5 GHz, since it's 1) limited to a certain number of channels, and 2) because the range sucks indoors.
I fired up uTorrent, and UPnP does seem to be working properly!
Note here:
[INFO] Fri Jun 12 17:29:48 2009 UPnP added entry 255.255.255.255 <-> XX.XX.XX.XX:32711 <-> 192.168.0.102:32711 UDP timeout:0 'uTorrent (UDP)'
[INFO] Fri Jun 12 17:29:48 2009 UPnP added entry 255.255.255.255 <-> XX.XX.XX.XX:32711 <-> 192.168.0.102:32711 TCP timeout:0 'uTorrent (TCP)'
So there, we have it adding entries for both TCP and UDP.
Now, as I move onto my tests, I play a few games here and there. My life mostly revolves around work, but I have tested playing Battle.net games, and some FPS such as Battlefield 2142, L4D, and CSS.
Latency is still the same of course, until you end up having huge spikes at times. Our goal is to get wireless performance ON par with the wired portion. It hasn't done this for a LONG while.
If you guys can, please test out gaming over wireless, AND wired. See if you notice a huge drop off in performance. It is however a wireless gaming router, and should perform as such.
If you use a mix of N/G and 2.4 GHz, please list out your settings. Mine are as follows:
Channel: Channel 11 - 2.462
Channel Width: Auto 20/40 Hz
Transmission Rate: Auto
Security Mode: WPA-Personal
WPA Mode: Auto (WPA or WPA2)
Cipher Type: TKIP and AES
Group Key Update Interval: 3600
My theory is that N is just completely messed up, and for some reason in the Status page, it ALWAYS shows a channel difference of 4 channels, since 802.11N requires channel bonding to TWO channels. I have a feeling that it has problems with that. So if I choose a channel of 11, the secondary channel will be 7. This might be WHY it has performance problems.
Now, as far as the rebooting after 3 or 4 days, I've yet to see that. Normally after my tests, the symptoms would show almost immediately while playing a game.
More will be updated later!
Update #2:
Gaming is still having lots of disconnect issues, and high latency. I do have QoS turned on, and setup my rules appropriately. But, I still get random spikes, and I managed to get disconnected twice in a row, within a span of about 2 minutes. Gaming was okay for first 45 minutes or so.
Still needs some work!
Will update more, to see if it can last longer, without killing WAN or LAN.
Update #3:
Gaming is holding up - sort of. I noticed that my link speed has dropped significantly compared to 1.15 FW. I cannot for the life of me get it past 52 Mbps. It used to be a solid 78 or so in Status -> Wireless, and that was decently okay for gaming. The spikes still happen, very badly. Doesn't quite lock me out of wan, but the latency gets so bad, that I check the tab, and it shows it's broadcasting and connecting at around 18 Mbps. That's pretty bad, and really needs to be fixed. Wireless gaming should be better, and not result in 7800ms of ping! It even displays that in the Statetable, after playing a game, with QoS rules engaged, and even without now. It's getting a bit better for sure. When it spikes, i cannot access pages for a few seconds, but it turns back to normal. Doesn't require a reset at all.
So, with that in mind, we are definitely headed in a better direction. Just more quirks that needs to be taken care of.
-
Reinvented,
OUTSTANDING Feedback! Although, it :'( me to hear as I was so hopeful this was going to be the one.
Thank You! Looking forward to your next post.
-
Ok I've flashed to it and have restored my settings. Only time will tell if this fw works properly and if it doesn't I'll be here *****ing about it. ;D
-
I flashed my router last night probably about 20mins after this beta firmware was uploaded. I reloaded my settings from my saved settings file and everything seemd to hum right along. I had no issues that I know of through out last evening and this morning, although admittedly my use was light. This morning I had my sons each jump on their xbox360s (Both wired connections) while I did some work from one of our laptops (wireless over an 802.11N connection). Everything was fine for about 2 hrs. Then about 10 mins ago the router froze. It was not responsive over wireless or wired, couldn't get to the admin screens nothing. Basically the exact same symptoms as before with the only remedy being to hard reset the router. So it lasted maybe 12hrs total.
This is really getting annoying. I do a lot of work with very large companies with huge networks and systems, I guess it's time to bite the bullet and bring home the same technology I use at work. I guess I'll have to switch over to something that I won't have to reboot almost every day. I'll be paying more for a real router but now it is just a business decision so I can do my work at home. I wonder how much real Cisco tech has filtered down into their home products.
-
I highly recommend that you don't restore your settings from a file...the reason being is because it can get corrupted, and there's a possibility that the codes don't necessarily match properly.
-
I'll second that, If you are up to it. Take screen shots or copy paste setting into notepad or text app depending on OS. Try a complete reset and reload settings. If it fails in the same manner then we know 100% issue is not resolved.
-
I just experienced the same slowdown issue and had an uptime of roughly 22 hrs before it occured. Nothing seems to have been fixed at addressing this issue here.
I've also noticed wireless link speeds are HORRIBLY the same as with 1.20. My network connected HDTV that used to get speeds in the 240-270 mbps range on wireless-N (5GHz) with firmware 1.15 and below now only gets 6-13 mbps with 1.20 and this beta. It's signal strength is still the same (~50%) so there's no new interference.
I am currently checking UPnP with WHS to see if at least SOMETHING appears to have been fixed on my end with this beta. As of this moment I personally have seen no improvement from 1.20 to 1.21.
-
After dealing with the 1.20 FW fiasco I have been sitting and waiting patiently for a fix. I downloaded and flashed my router several hours ago & like so many of us who have been stymied with inoperable FW's , am taking a wait and see attitude. I will say this, I did the 30/30/30 reset and configured my router from scratch! So far so good. Like I said time will tell. I will provide as much info as I can as things develop, hopefully all good. Thanks to all who have contributed fixes to this major problem. Your help and time is greatly appreciated.
-
I just experienced the same slowdown issue and had an uptime of roughly 22 hrs before it occured. Nothing seems to have been fixed at addressing this issue here.
I've also noticed wireless link speeds are HORRIBLY the same as with 1.20. My network connected HDTV that used to get speeds in the 240-270 mbps range on wireless-N (5GHz) with firmware 1.15 and below now only gets 6-13 mbps with 1.20 and this beta. It's signal strength is still the same (~50%) so there's no new interference.
I am currently checking UPnP with WHS to see if at least SOMETHING appears to have been fixed on my end with this beta. As of this moment I personally have seen no improvement from 1.20 to 1.21.
I just got heartburn.
Come on Dlink put the A-Team on this fix, not the summer interns.
-
This firmware sounds like my cousin Oliver. Oh! I hate him.
(http://www.easyimage.us/media/files_image/user1453/131823eabab.jpg)
-
Just a followup to my last post - UPnP with WHS is still broken and the UPnP port forwarding rules disappear after 10-15 minutes.
Additionally, as far as the wireless link speed goes for me it only seems to give low results with 802.11n and not 802.11a. I only use the 5GHz mode with this router since it's not simultaneous dualband and I have another AP that is used for 2.4GHz.
Sadly, none of the major firmware flaws have been fixed with this beta.
-
Ru-Fi-Oh:
so far these are the problem issues
Reinvented and defaultPlayer thank you, with your permission
I summerised the problem issues:
1.quirks with the CAPTCHA authentication
2.UPnP functionality
3.The wireless speeds suck still,
and performance drops off almost immediately.
4.N is just completely messed up, and for some reason in
the Status page, it ALWAYS shows a channel
difference of 4 channels, since 802.11N requires
channel bonding to TWO channels.
5.Gaming is still having lots of disconnect issues,
and high latency.
6.Wireless, and that was decently okay for gaming.
The spikes still happen, very badly.
Doesn't quite lock me out of wan, but the latency gets so bad,
that I check the tab, and it shows it's broadcasting
and connecting at around 18 Mbps.
That's pretty bad, and really needs to be fixed.
7.Network connected HDTV that used to get speeds in the 240-270 mbps range
on wireless-N (5GHz) with firmware 1.15 and below now only gets 6-13
Reinvented and defaultPlayer thank you again
-
I am having the same excat problems as before. I uploaded the beta F/W on Fridday not long after it was posted.24 hours later it does not work. Same as before. Not even rebooting the router works. This needs to be fixed ASAP
-
oh my ... its SO annoying ... i nearly have to restart my router every day cuz of these slowdowns etc
dlink PLS ... fix it or put a 121b2 firmware that allows us to downgrade to 116 ... didnt have problems with that one!
-
Well my router has been up just over a day and the router menu is already slowing down when accessing through the web browser. I believe that the best improvement they could make immediately is allowing us to downgrade to fw 1.02.
-
I believe that the best improvement they could make immediately is allowing us to downgrade to fw 1.02.
dlink PLS ... fix it or put a 121b2 firmware that allows us to downgrade to 116 ... didnt have problems with that one!
I think I'm going to have to agree with D-Link taking a step back on this one and re-releasing 1.15 as 1.21. That's the quickest way to resolve all of these major issues so at least we can get our router's basic functions working 24/7 and ASAP. After that then they can take their time on tweaking 1.20; I just want my trusty rock solid DGL-4500 back.
-
By the time they fix everything with the DGL-4500, there will be a new model. :[
-
Still running 1.20, however I noticed the router seemed to be running a little warm. I remounted it in the vertical position and use a small fan to blow air around it. Been up for over 7 days now. Could the 1.2x fw be loading the hw a little heavier causing higher heat sensitivity? Just a thought...
-
Still running 1.20, however I noticed the router seemed to be running a little warm. I remounted it in the vertical position and use a small fan to blow air around it. Been up for over 7 days now. Could the 1.2x fw be loading the hw a little heavier causing higher heat sensitivity? Just a thought...
Interesting please keep us up-to-date on your routers progress and uptime
-
This firmware sounds like my cousin Oliver. Oh! I hate him.
(http://www.easyimage.us/media/files_image/user1453/131823eabab.jpg)
ROFLMAO! Oliver!! 1.21
-
Not likely. Mine's been sitting in the upright position since I've had it and plus I have AC going.. Still fails because of UPnP, and wireless.
-
I think I'm going to have to agree with D-Link taking a step back on this one and re-releasing 1.15 as 1.21. That's the quickest way to resolve all of these major issues so at least we can get our router's basic functions working 24/7 and ASAP. After that then they can take their time on tweaking 1.20; I just want my trusty rock solid DGL-4500 back.
1.02 was way more stable than 1.15.
By the time they fix everything with the DGL-4500, there will be a new model. :[
Been saying that for months now. I kinda got that feeling back when 1.15 was released and was claimed to have "fixed" some things.
They should try going back to what worked and take it from there. Until then put out an updated version of 1.02.
Oh and did I forget to mention shareport still does not work.... shocking....
-
Installed 1.21 firmware.
So far so good.
Statistic as below:
LAN Statistics
Sent :57977
TX Packets Dropped :3
Collisions :0
Received :0
RX Packets Dropped :0
Errors :0
WAN Statistics
Sent :5235226
TX Packets Dropped :0
Collisions :0
Received :7441834
RX Packets Dropped :0
Errors :0
Wireless Statistics
Sent :5360909
TX Packets Dropped :14885
Received :3862657
RX Packets Dropped :5609
Errors :1275
It's been up for 4 days and 22 hrs, very bad in wireless connection on n.
It's better if we can choose the 2nd channel for bonding instead of getting it done auto.
Setup as below:
Wireless Radio : Enabled
802.11 Mode : Mixed 802.11n, 802.11g and 802.11b
Channel Width : 40MHz
Channel : 4
Secondary Channel : 8 (done automatically)
WISH : Active
Wi-Fi Protected Setup : Enabled/Configured
Security Mode: None (using MAC filter).
-
So... I disabled the CAPTCHA authentication, and now when I try to log into the router, I keep getting an error, asking for the CAPTCHA code, but nothing is displayed....
How do I gain access to the router now?
This happens even after I reboot the router....
Thanks,
crash
-
Different song, Same old dance!
Well folks in less than 36 hours I lost all connectivity, But ALAS there's a remedy. Walk over to the tried and true DGL-4500, PULL THE FREAKING PLUG, WAIT 10 SECONDS or so, reinsert the afore mentioned " freaking plug, and like magic all is well once more in this never ending battle.
One of the first things I noticed soon after flashing was that share port would see but not connect to anything connected to it. I could live with that I think. I knew that by rebooting I could take care of that issue. But I persisted! It wasn't long after that that my download and upload speeds started degrading. In it's final death throws I finally put it's agony to rest. PULLED THE FREAKING PLUG!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
-
Ru-Fi-Oh!!!!!!!!!!!!!!!!!!!!!!
we demand!!!!!!!!!!
version 1.02
>:( >:( >:( >:( >:( >:( >:(
-
Think mine just bombed. Haven't been home to check it out yet but I am locked out remotely which usually means it's shot. I have been pretty quiet for a while. Watching but not posting. I have sent what I can to Dlink especially with the PS3 issues only to get the cold shoulder now with all responses stopping.
I know there was some complaining against the guys that were in here *****ing and demanding.
I'm sorry but I don't blame them at all. It's become quite unreal again and is as bad if not worse than the move from 1.02 way back when. I don't know what to do other than laugh sometimes. I work on high end routers daily and thought for home I picked a good and fun product to mess with for my gaming needs. However it's quite sad at this point to say that this product is pretty much a door stop. I like a lot of people upgraded from the dgl-4300.
I guess for now it's back to the dd-wrt router.
Really D-Link. I'ts time to get some higher end techs on the job and get your product at least working for people. Right now it doesn't even function as a low end router. Much less a 200 dollar product that most here paid.
-
Here are my statistics, i haven't rebooted since the beta firmware release. Wireless is lacking a lot in performance.
LAN STATISTICS
Sent :773784
TX Packets Dropped :7
Collisions :0
Received :433602
RX Packets Dropped :0
Errors :0
WAN STATISTICS
Sent :4924255
TX Packets Dropped :0
Collisions :0
Received :6829818
RX Packets Dropped :0
Errors :0
WIRELESS STATISTICS
Sent :5393107
TX Packets Dropped :12350
Received :4529678
RX Packets Dropped :3185
Errors :5022
-
Well folks this latest flavor of FW is very unstable like I mentioned I followed all posted procedures before flashing and it's been a nightmare ever since Here are my stats:
Sent :33321
TX Packets Dropped :3
Collisions :0
Received :0
RX Packets Dropped :0
Errors :0
WAN STATISTICS
Sent :46497
TX Packets Dropped :0
Collisions :0
Received :427333
RX Packets Dropped :0
Errors :0
WIRELESS STATISTICS
Sent :959073
TX Packets Dropped :709
Received :918380
RX Packets Dropped :0
Errors :11129
Copyright © 2004-2008 D-Link Systems, Inc.
-
LAN Statistics
Sent :2760141
TX Packets Dropped :3
Collisions :0
Received :1824533
RX Packets Dropped :0
Errors :0
WAN Statistics
Sent :1614217
TX Packets Dropped :0
Collisions :0
Received :5741825
RX Packets Dropped :0
Errors :0
Wireless Statistics
Sent :586233
TX Packets Dropped :23765
Received :601894
RX Packets Dropped :1995
Errors :9438
So far I have had to reboot 3 times, oh and the clock still doesn't keep time. Another thing go to your log, look through it you should see info, warn, etc. I have over 1900 messages but if you uncheck all and only select the ones you want to see 0 show.
I know there are warn messages for multiple categories I can see them when all check boxes are selected but, when I to try to view just 1 or 2, anything but all check boxes, 0 messages is all I get.
So The filter is broken too.
Oh and here's a new one for you Just now All Google site were dead to me. All other sites were fine, except for yahoo.com which thought I was on a mobile browser cause it would auto redirect me to m.yahoo.com. Reboot via the admin page Google sites now back and all other working as they should, for now.
I mean really, basic items like this filter and the clock not working? How Mickey Mouse of a development team is on this?
(http://www.easyimage.us/media/files_image/user1453/1358eb67d7c.jpg)
-
Think mine just bombed. Haven't been home to check it out yet but I am locked out remotely which usually means it's shot. I have been pretty quiet for a while. Watching but not posting. I have sent what I can to Dlink especially with the PS3 issues only to get the cold shoulder now with all responses stopping.
I know there was some complaining against the guys that were in here *****ing and demanding.
I'm sorry but I don't blame them at all. It's become quite unreal again and is as bad if not worse than the move from 1.02 way back when. I don't know what to do other than laugh sometimes. I work on high end routers daily and thought for home I picked a good and fun product to mess with for my gaming needs. However it's quite sad at this point to say that this product is pretty much a door stop. I like a lot of people upgraded from the dgl-4300.
I guess for now it's back to the dd-wrt router.
Really D-Link. I'ts time to get some higher end techs on the job and get your product at least working for people. Right now it doesn't even function as a low end router. Much less a 200 dollar product that most here paid.
+1 or they could give us the jtag pin-out, source code, and let us fix it ourselves. I'd rather deal with my own mistakes than those of others. And yes mine is running worse with 1.21 than 1.20 . It actually caused my whole network to lock up twice. If I had my choice I would want to go back to 1.16 because even 1.02 had issues (hence the reason I have had two 4500's crippled).
-
I have seen the same issue that Iconeater had with google. It's a real pain... The messages were broken on 1.20 too. I know there must be someone concerned about what all this people that has bought the 4500. If there isn't ( just a dude planing on a new hardware with the label "Problems Fixed Here"), just let us know so we move on. Maybe we can find a product that doesn't bug out because you use it.
-
I have seen the same issue that Iconeater had with google. It's a real pain... The messages were broken on 1.20 too. I know there must be someone concerned about what all this people that has bought the 4500. If there isn't ( just a dude planing on a new hardware with the label "Problems Fixed Here"), just let us know so we move on. Maybe we can find a product that doesn't bug out because you use it.
Iconeater emailed me saying he was banned for Abusive Tones and Flaming.
Dlink is posting trolling messages as "users" to start flame wars and get active complainers banned. Don't get sucked in.
They have deleted many of my messages and Many Topics namely the class action lawsuit one from the DGL-4500 forum.
I THINK THAT IS HORRIBLE DLINK!
(http://www.easyimage.us/media/files_image/user1453/13632ea48e7.jpg)
-
So if it's OK for you to assume we're posing as regular users then it must be OK for us to assume you Cindy Brady are also iconeater?? You got nothing but time to harass normal users who legitimately having working routers and want to give positive feedback. As soon as something positive is posted you guys are quick to bash.
We as D-Link employees are here to help and not play games with an issue so serious. We understand the nature of this issue unfortunately things aren't going the way we want it to. Trust me, do you think we like having these problem and dealing with these complaints? All we can do is take what you guys give us and try to fix it.
-
You know what, Ru-Fi-Oh? I do think you're doing your best to get this fixed.
It's a shame you don't seem to have an appropriate "sales manager" type stepping in to liaison, 'cause as you're aware, you have some really frustrated customers.
"Trust me, do you think we like having these problem and dealing with these complaints?"
See, that's awful PR, if you'll excuse me for saying so. Oh well.
-
Ru-Fi-Oh there have been what 10, 12 maybe more firmware "fixes" to resolve these issues. As far as I can tell there is no difference between the 1.20 and this latest beta 1.21.
If you think we don't want a fix and all we want to do is complain you are mistaken.
Realize that you are dealing with people who paid a premium price for above average device and are getting below average results some for a year or longer.
Who do I contact to send this router back to Dlink and be refunded?
I'm convinced your developers can't fix this router.
-
Ru-Fi-Oh:
so far these are the problem issues
Reinvented and defaultPlayer thank you, with your permission
I summerised the problem issues:
1.quirks with the CAPTCHA authentication
2.UPnP functionality
3.The wireless speeds suck still,
and performance drops off almost immediately.
4.N is just completely messed up, and for some reason in
the Status page, it ALWAYS shows a channel
difference of 4 channels, since 802.11N requires
channel bonding to TWO channels.
5.Gaming is still having lots of disconnect issues,
and high latency.
6.Wireless, and that was decently okay for gaming.
The spikes still happen, very badly.
Doesn't quite lock me out of wan, but the latency gets so bad,
that I check the tab, and it shows it's broadcasting
and connecting at around 18 Mbps.
That's pretty bad, and really needs to be fixed.
7.Network connected HDTV that used to get speeds in the 240-270 mbps range
on wireless-N (5GHz) with firmware 1.15 and below now only gets 6-13
Reinvented and defaultPlayer thank you again
Ru-Fi-Oh:
we want these things fixed ASAP we payed good money for this router the minimum
is to fix these ASAP days not weeks and months
this is crazy and outrageous!!!!!!!!!!!!!!
this is not professional !!!!!!!!!
sorry for my tone but i think we all deserve a working firmware to this expensive router
-
Right now I've been up for 3 days and 19hrs and while it hasn't ground to a halt yet web pages and the router menu have some delay before they load up. I've also noticed that my lan error count is starting to slowly creep up again as I near the 4 day mark just like 1.20 did.
D-Link will you please rewrite the code and allow us to roll back to 1.02 which has been the most reliable fw that I've used to date.
-
Although I am not a hardware or Software engineer I believe the channel separation is needed to keep frequency interference to a minimum, just a thought. As far as bonding goes, 2 frequencies transmitting the same info, simultaneously and in Sync. I could be wrong and more than likely am ???
-
As before, I've mentioned EVERYTHING that I possibly could in trying to get this fixed. Still keeping in touch with Ru-Fi-Oh on my progress towards the testing. Every problem that I've listed is up above in my previous posts.
Yes, it absolutely DOES SUCK that we don't have a working product anymore. However, there isn't much we can do about that right now. And flaming and trolling doesn't help either. It is afterall a place to help. Iconeater did start trolling, and started flaming me as well earlier. However he seemed to shape up a bit. However, him getting banned was his own doing, and the moderators should not have to take blame for that after he was warned several times. Now, you can go smash D-Link elsewhere. This is a place for help, and in fact, they don't HAVE to help you at all, or provide you with beta firmwares or anything. They could easily shut this board down, and give you absolutely NO SUPPORT of ANY KIND. I am glad they put it up, as opposed to being on the phone with support, and someone who doesn't speak english.
Some of the code cannot be rolled back, as there were some important updates provided by Ubicom. Again, Ubicom mostly provides the major updates, and it's D-Link's job to modify it. However, if there are major problems with it in the first place, its not D-Link - but Ubicom.
In the meantime, since I am tired of testing myself, and I'd like to actually enjoy some of my free time this summer I threw up an old WRT54GS with DD-WRT. I'm getting used to that now more, since it provides a bit more, and is actually stable for my needs. Buy a cheap router in the meantime if you'd like.
-
I honestly believe that there's a memory leak with this router which is why it cannot stay functional for long periods of time without a reboot.
-
As before, I've mentioned EVERYTHING that I possibly could in trying to get this fixed. Still keeping in touch with Ru-Fi-Oh on my progress towards the testing. Every problem that I've listed is up above in my previous posts.
Yes, it absolutely DOES SUCK that we don't have a working product anymore. However, there isn't much we can do about that right now. And flaming and trolling doesn't help either. It is afterall a place to help. Iconeater did start trolling, and started flaming me as well earlier. However he seemed to shape up a bit. However, him getting banned was his own doing, and the moderators should not have to take blame for that after he was warned several times. Now, you can go smash D-Link elsewhere. This is a place for help, and in fact, they don't HAVE to help you at all, or provide you with beta firmwares or anything. They could easily shut this board down, and give you absolutely NO SUPPORT of ANY KIND. I am glad they put it up, as opposed to being on the phone with support, and someone who doesn't speak english.
Some of the code cannot be rolled back, as there were some important updates provided by Ubicom. Again, Ubicom mostly provides the major updates, and it's D-Link's job to modify it. However, if there are major problems with it in the first place, its not D-Link - but Ubicom.
In the meantime, since I am tired of testing myself, and I'd like to actually enjoy some of my free time this summer I threw up an old WRT54GS with DD-WRT. I'm getting used to that now more, since it provides a bit more, and is actually stable for my needs. Buy a cheap router in the meantime if you'd like.
LOL whatever he put you in your place. But i digress.
So no one should complain or "flame or Troll" but instead get a cheap router and forget about all this.
hmmm?
I been doing nothing but reading and seems to me the "base code" which can not be changed hence, the no downgrading, is the issue. IF in fact this a something caused by Ubicom, wouldn't other manufacturers or other Dlink devices which uses this hardware and "base code" all be having issues? Is that in fact the case? What other routers use the same hardware as the DGL-4500.
So when can we expect the next firmware "fix"? What's the count at now 14?
-
LOL whatever he put you in your place. But i digress.
So no one should complain or "flame or Troll" but instead get a cheap router and forget about all this.
hmmm?
I been doing nothing but reading and seems to me the "base code" which can not be changed hence, the no downgrading, is the issue. IF in fact this a something caused by Ubicom, wouldn't other manufacturers or other Dlink devices which uses this hardware and "base code" all be having issues? Is that in fact the case? What other routers use the same hardware as the DGL-4500.
So when can we expect the next firmware "fix"? What's the count at now 14?
How did a 12 year old "put me in my place" ?
No, you can get a cheap router to tie you over until an actual fix comes out. And just FYI, ALL of the top flagship models ARE having problems. Same exact ones.
-
How did a 12 year old "put me in my place" ?
Rather effectively actually. ;D
If all Ubicom devices are acting up, and it seems D-Link can't fix them then how do I get my money back so I can go elsewhere?
Or, maybe D-link can just ship us "cheap" routers for us to use while they get this flagship gaming router off the bottom of the ocean?
-
Rather effectively actually. ;D
If all Ubicom devices are acting up, and it seems D-Link can't fix them then how do I get my money back so I can go elsewhere?
Or, maybe D-link can just ship us "cheap" routers for us to use while they get this flagship gaming router off the bottom of the ocean?
own!!!!!!!!!!!!
-
Ok, i think this is sinking down to a personal level. Let's try to keep this a little more peaceful before, like mentioned in other posts, we all get shut out. We all know the issues and they know them as well. If we can wait, we got 2 options, fork out the $$ and get a new router or sit and hope for the best. :'(
-
My own $.02:
I purchased and used a DGL-4300 for *years* - as in well past 4 - without a hitch - until this past Jan, when it decided that it simply would not do DHCP for me anymore.
Based upon the use I got out of my 4300, plus the use I got out of my DIR-524s (Rev A and rev C) I decided to grab the 4500 w/ N Draft 2 - I now have a laptop with built-in N NIC, so I figured what the heck.
I then upgraded to the latest f/w out ATM - 1.15? - without bothering to read if it was worth it or not. I got stuck with crap f/w that I could not revert - all my fault.
However, things have gotten better, then worse, through the revisions. I was experiencing dropped packets (I ran my 4300 for 6 months with a single dropped packet - the 450 drops 1 per week or more - on the *wired* network). Wireless connectivity for my laptop is great - but for devices that do no support WAP, or G, it is straight horrible. My ancient iPaqs (a pair of 2490Cs) show diminished signal strength outside of 10 feet from line of sight to the router. My network goes stone cold dead within days. My machines are inaccessible from the real world every 3-4 days.
This may sound like a rant, but in fact it is more of a plea. Please, please *PLEASE* put pressure on Ubicom to fix this s*** ASAP - I have always preferred D-Link over Netgear as all DL products have. just. worked. No ifs, no ands, no buts.
I have a real world job and yet have a small beast of a computer at home - using RDC is *vital* for me for obtaining files that are not accessible anywhere else b/c of time, space, or other factors - both work file sand school work. I simply cannot afford to buy another router right now, and I cannot afford to not be using Gigabit Ethernet for my internal network at home, so plugging in the DIR-524s is simply economically infeasible. The 4300 still will not work (I have tried every sort of reset I could find in the forums and FAQs, to no avail - it simply does not send out IPs anymore to machines on my network) and I have to have this working immediately. If D-Link is willing to swap my currently upgraded 4500 (1.20) with a router running an older f/w (preferably 1.02 so *I* can decide which one to go with in the interim until these issues get resolved) I am most willing to open a ticket - the router is approaching its 6 month b'day in my household, and I have to say this is the first time I have ever had a problem with a D-Link - if it were not for these forums I would quite possibly have tried to exchange it at Best Buy, but reading here it is obvious that the problem lies in the router....
Some thoughts:
My router hoses itself within a 24 hr period if I have logging enabled (which I really, really *REALLY* want to have enabled as I report intrusion activities to SANS.org). However, if I disable logging, I can get 3-5 days of use out of it. That plus the fact that the router says it needs 2A of current, plus a comment made earlier, have me thinking - does this thing *really* need 2A of current? Is it slowly frying itself b/c of bad parts in the box? I have a set of NetGear GS108 Gigabit Switches - notorious for dying abruptly with the flashing lights of doom syndrome. The problem was that there was a very large batch of bad capacitors used in numerous models sold, and removing and replacing said caps with some found at Radio Shacks across the US make them work perfectly fine - I have one repaired over a year ago without a hiccup - in use right now with my 4500 serving remote areas of the house with Gigabit Ethernet. My thought is that the combination of such high current plus faulty hardware (and possibly the heat being dissipated from the components) could all be interacting to make our routers unstable?
BTW, I have my router mounted upside down (as that is really the only place I could place it so that I had ready access to the OLED info screen: http://picasaweb.google.com/johnlgalt/TheBeast#5308321719746502562
Finally, one more thought - This is absolutely horrible performance out of a product that I paid $150 of my hard earned money for - for example, I just had to hard reset the router b/c it stopped working, all my machines could not even ping the router, and I could not log into it. Thus far, it has been running for 36 Minutes and 31 Seconds, and I have the following:
Sent : 27316 .
TX Packets Dropped : 10 .
Collisions : 0 .
Received : 31781 .
RX Packets Dropped : 0 .
Errors : 0 .
***10*** packets dropped in ***36*** minutes??? That is a major problem. My 4300 would not accumulate 10 dropped packets in a friggin month.
Ru-Fi-Oh - are there any non upgraded routers left out there that D-Link is willing to swap with users?
-
own!!!!!!!!!!!!
Yeah, that's not really being owned.
In fact, i still fail to see how he did. All Iconeater did was point out that I have lots of posts here on these forums...that was it. Pretty bad insults if you ask me. Learn to come up with something more, and then maybe we'll take you seriously.
-
After reading all of the posts after the 1.20 and subsequent 1.21 beta fw updates i decided to do some poking around. I visited some of the other forums and to my dismay could of sworn I was still here looking at the dgl-4500 forum. D-Link has a real mess on their hands. I am a casual user but consider myself technologically adept. It's no big deal for me to get up from my little corner and walk over to the router ( cussin all the way ) and doing a hard reboot to get things working again. I have nothing but sincere empathy for all you hard core gamers and those who depend on this piece of equipment to work correctly and soundly. Again I'll say my most sincere thanks to the Moderators who are stuck in the middle of this quagmire, I can imagine this is a real headache for y'all. I'll sit here and monitor this board patiently until there's a solid fix. I don't mind testing and tweaking. For now let me say that you have my full support and confidence that this issue will be resolved amicably
-
I just had the best dream, I figured I'd share it cause we all need some good news.
In my dream This router was fixed buy the next firmware and Reinvented finally had a good comeback.
Oh it was awesome.
Well, back to bed. ;D
-
If I had to take sides I would say Reinvented has done more than any of us here. I was posting back about 8 months ago and he has been having all of the issues I have. I was able to return my first router, so I was off the boards for a while. But 1.02 was giving me issues on the second one and I saw good results on 1.16. So I flashed away. Then I thought maybe 1.20 would get rid of my one last issue of wan disconnects, but it got much worse. That is the only reason I started posting again. He has had a lot of patience to put up with it this long. I bought a new router 1 week after having 1.20. If he tested as much as I did i know his personal time spent on the router is well over 500+ hours. That is a lot of time in his life he will never get back, So please cut him some slack since he is one of the only ones being useful (I know there are others like Puffnstuff, not trying to leave anyone out, just trying to make a point).
On a separate note I am going to hook up the 4500 as a second router and slowly but surely test each computer on my network. I have 1.21 loaded and I will post my findings along the way.
-
I bought another router. I had it waiting in a box before I loaded 1.20. I was fed up with all the firmwares after 1.02. I'm lucky that 1.20 has worked for me. It seems to have worked for other people as well, some of which don't post.
Back to the 1.21 discussion.
Due to how buggy their captcha implementation is, would it be possible for D-Link to disable this option by default, instead of enabling it? Similiar to how they disable HTTPS admin access by default (which I believe has an expired cert).
Another thing on TX Packets Dropped in their stats. After any reboot, I always see either 3 errors. I'll clear the statistics and check back later. With 1.20, this is the first firmware where this number has stayed 0 after I do a clear right after reboot. It's still 0 dropped after 11 day uptime. If you're seeing the errors and they continue climbing that's symptomatic of what I saw with previous firmwares where the router would gradually or promptly grind to a halt, varying in degrees.
From browsing through this thread and trying to cherry pick useful device information, did anyone have any luck with NTP actually updating?
-
Thanks for the feedback good or bad.. Ever since this code came out we've been picking apart all the issues and results you guys have posted and comparing it to results we've seen in house. Again, I apologize that it's gone this far without a fix. All I could do on my end is keep pushing and pushing this to our PM group and see what happens. Please don't feel we are ignoring you. We monitor this thread real closely to gather information.
-
Thanks for the feedback good or bad.. Ever since this code came out we've been picking apart all the issues and results you guys have posted and comparing it to results we've seen in house. Again, I apologize that it's gone this far without a fix. All I could do on my end is keep pushing and pushing this to our PM group and see what happens. Please don't feel we are ignoring you. We monitor this thread real closely to gather information.
That is actually one of the best responses i've heard so far. It's a good way to keep the crowd calm. Thanks for your work and please keep us posted.
-
+1
-
Well 1.21 locked up my router while I was at work today. When I got home I couldn't access the net and my son complained to me that its been slow all day. I had to power cycle it to get reconnected again.
-
My router just locked up (1.21). Couldn't even access the administration page. Had to power cycle.
This is awful.
-
How many PCs does everyone have connected? Wireless? Wired? xBox? PS3?
-
Wired: 1 PC, 1 Slingbox, and 1 Satellite Receiver
Wireless: 4 Laptops and 3 Towers (XP, Vista, and Win7)
-
I have:
1 WebSTAR DPC2100R2 Modem
1 Linksys wrt310n Router
1 D-Link dgl-4500 Router
1 D-Link dgs-2208 Switch
1 xBox wireless (wired didn't make a difference)
1 wired tower with 64bit XP SP3
2 wired towers with Server 2003 SP1
1 wired tower with Suse 11.1 as server
1 wireless laptop with XP SP2
1 wireless laptop with XP SP3
1 wireless laptop with Vista
1 wireless laptop with Windows 7/Suse 11.3 as client
All of the towers have gigabit NICs (mixed brands)
All of the wireless have G (mixed brands)
-
Two wired, up to four wireless devices.
Only one wired device is doing much in the way of traffic.
-
I am only using two wired pc's right now with wireless disabled. This is such a terrible situation that d-link has us all in. It's obvious that they didn't test the router for any length of time before they released this fw into the wild.
D-link should immediately allow for us to roll back to an earlier fw version and be required to not develop any code that will prevent you from rolling back to a previous version.
-
So far with everyone that posted, it doesn't seem the amount of PC's is the cause. What brand cards are in your wired devices?? And for everyone else what brands are their wireless? I've had terrible results with Atheros cards in my laptops so I replaced them with broadcom and my speeds doubled with half the error rate.
-
I am only using two wired pc's right now with wireless disabled. This is such a terrible situation that d-link has us all in. It's obvious that they didn't test the router for any length of time before they released this fw into the wild.
D-link should immediately allow for us to roll back to an earlier fw version and be required to not develop any code that will prevent you from rolling back to a previous version.
I agree with this. Again I really feel for people that have no other option. I grew very tired of it all last night and upgraded my wrt54g with the latest dd-wrt and it's working great. Why I don't just stay there I have no idea. Actually thinking of putting dd-wrt on the other 3 access points I have running 2 of which are a bridge. We shall see how stable it stays for the next week or so first I guess.
For those that only have 1 router is who it really sucks for. My father in-law uses the internet and I got really tired of him calling saying he couldn't get on only to find out I didn't set a timer to reboot my dgl-4500. I also still have my dgl-4300. It was so solid that I just don't know what to think on the 4500. Maybe it's time to dump them and just stick with something else but I won't be going back to linksys either as had nothing but problems with one of their routers they let out way to early and I got duped on that one.
Really nice thing is the ongoing PSP-PS3 issue I worked with D-Link on for quite some time until they stopped responding works perfect with the dd-wrt. I'm actually connected to my ps3 from my psp right now as I type this.
Also IMO DLink is at the point if not way past it of offering some sort of trade in to customers of the 4500. While that may seem like a lot I have been on these boards to see the big fail from 1.02 and now another large one with 1.20. The others in between weren't great but they did function. 1.02 and 1.20 are the ones that stand out as about the worst Quality testing I have seen from a company. While I know they apologize that it happened it still happened and I have a hard time imagining what's going on behind the wall of the corporate office and the people involved. If it is Ubicom then DLink needs to put together an official statement and either take the blame or give it but something needs to happen on a higher level than some beta forums with a few mods updating the affected that even know where to find this info.
-
As far as my wired PC it's an intel gigabit nic.
And the wireless cards are mixed: Atheros, Ralink, Belkin, Intel, and Linksys. All Wireless G
-
OK so after looking through this thread I've gathered all the common issues all of you have posted. Please feel let me know if I've missed anything.
RELATED ISSUES EVERYONE IS HAVING:
- TX dropped packets in the wireless as well of RX packets
- 3+ hours of wired and wireless use the unit becomes
unresponsive. (Cannot access router GUI, web pages don’t load and Latency)
- Gaming is still having lots of disconnect issues,
and high latency
- UPnP Functionality issues.
- Quirks with the CAPTCHA authentication
Also to confirm is everyone here using A1 hardware?
-
Yes Ru Fi Oh.
We're using A1 hardware.
-
Ru-Fi-Oh:
Yes, A1 version for me as well. I have 2 always on PCs connected, one via dual Gigabit NICs directly into the router, and the second via a single Gigabit NIC connected through the earlier mentioned NetGear Gigabit switch. I also have an always on (but mostly idle / sleeping) Brother Networked printer, Model HL-5250DN, attached through same Gigabit switch, and I have a 3rd PC and a laptop that occasionally connect, both by wired connections, one through the Gigabit switch and the other via direct connection into the router.
The laptop also has wireless N capabilities, so I sometimes use it via wireless. The iPAQs I mentioned in my last post only support wireless B, but I have my router set to Mixed more (G + N) and I get pretty similar results in terms of connectivity and packet loss on the wired connections regardless of wireless on or off. Honestly, though, I do see a *lot* of dropped packets on wireless if I add B into the mix and connect my iPAQs, but in GN mode it seems to not affect my overall usability versus N only or wireless disabled.
-
I'm using Hardware Revision A1 and have been waiting patiently for a fixed firmware.
Currently running 1.20 b3 (or what ever the last 1.2 was) - I didn't dare to update to the release or the newest beta.
I'm getting issues with the wireless too.
BTW.......
In the DGL-4500 Configuration Menu under the Advanced Tab, under Gaming, I see you list PlayStation and Xbox, BUT... There is no entries for Nintendo Wii in the Application Name pull down menu.
-
Using A1 here plus I sent you pm with my sn.
-
I an A1 and 4 wireless clients. Also to be noted are the issues with shareport and logging. Thanks
-
Using A1 hardware here also.
-
Well I was gonna offer to beta test this since I too am a victim but frankly I've seen enough. I recommend everyone immediately file a complaint with the Better Business Bureau at www.bbb.org
This will light some fires under D-Link and have a very negative effect on business if they don't handle their business. My router was running fine at 1.15 for months without a reboot, I upgraded last week and well now ya know the rest of the story. What's criminal about this is is they still have it on the website knowing full well there is a problem.
I just filed my complaint and I recommend everyone else do the same ASAP. They have an obligation to immediately replace these routers for down rev versions that work at their expense. We should accept nothing less!
-
BTW also using A1
-
yep A1
and pls dont forget the 3 day reset issue
-
WOW I've read through this entire thread, and am convinced that being in the beta will bring more problems, Hell no! I beta tested 1.20 and that was just horrid to my wireless, now theirs packets drops off the wazoo! OMG just give us a rollback to 1.02 and call it a day, and maybe release a new model with this upcoming FW your working on, and no ones the wiser, its that simple. No need to stress yourself over this Ru-Fi-Oh, just give us rollback, thats all that is needed for resolution.
-
While that may seem like a lot I have been on these boards to see the big fail from 1.02 and now another large one with 1.20. The others in between weren't great but they did function. 1.02 and 1.20 are the ones that stand out as about the worst Quality testing I have seen from a company.
? 1.02 just as bad as 1.20. You sure thats what you meant? Anyone can look back a few pages and see the fall came when people upgrade to f/w after 1.02. Remember 1.03 and 1.10...
-
too many people skim through all these posts an think they know it all. Not enough have tried actually using all the different variations out there, but only notice the problems when they perform an upgrade, and then immediately blame D-Link for the problems they are encountering. I wish all the folks that are posting the same hogwash in multiple forums would take 2 seconds to read the posts again - they'll see that it is the Ubicom f/w that was r-written that is causing the issues, and also that the f/w was written on *their* end to not allow downgrading.
Therefore,
1) D-Link (along with other companies) are suffering the consequences of this Ubicom mistake, and
2) D-Link cannot offer the downgrade as it is not them who forced the non-downgradeable upgrade on their routers.
Please wake up and smell the coffee and really read *carefully* what is going on. attacking D-Link, the mods here, trolling, etc. is only going to get you banned, instead of getting you the solution.
The call of hardware revision numbers means something is up with the PM team - they are looking at it in a new light now, and patience is all that is required.
-
too many people skim through all these posts an think they know it all. Not enough have tried actually using all the different variations out there, but only notice the problems when they perform an upgrade, and then immediately blame D-Link for the problems they are encountering. I wish all the folks that are posting the same hogwash in multiple forums would take 2 seconds to read the posts again - they'll see that it is the Ubicom f/w that was r-written that is causing the issues, and also that the f/w was written on *their* end to not allow downgrading.
Therefore,
1) D-Link (along with other companies) are suffering the consequences of this Ubicom mistake, and
2) D-Link cannot offer the downgrade as it is not them who forced the non-downgradeable upgrade on their routers.
Please wake up and smell the coffee and really read *carefully* what is going on. attacking D-Link, the mods here, trolling, etc. is only going to get you banned, instead of getting you the solution.
The call of hardware revision numbers means something is up with the PM team - they are looking at it in a new light now, and patience is all that is required.
First line really set the tone of a BS rant coming. had me laughing
1) The ones who are suffering (really wouldn't use that word but ok) is the end-user not D-Link
2) This has been said over and over and over by different people...as in its old news.
I myself and a few others have been waiting "patiently" for over a year now...
I will ask this of you. Did you actually read what you posted?
-
too many people skim through all these posts an think they know it all. Not enough have tried actually using all the different variations out there, but only notice the problems when they perform an upgrade, and then immediately blame D-Link for the problems they are encountering. I wish all the folks that are posting the same hogwash in multiple forums would take 2 seconds to read the posts again - they'll see that it is the Ubicom f/w that was r-written that is causing the issues, and also that the f/w was written on *their* end to not allow downgrading.
Therefore,
1) D-Link (along with other companies) are suffering the consequences of this Ubicom mistake, and
2) D-Link cannot offer the downgrade as it is not them who forced the non-downgradeable upgrade on their routers.
Please wake up and smell the coffee and really read *carefully* what is going on. attacking D-Link, the mods here, trolling, etc. is only going to get you banned, instead of getting you the solution.
The call of hardware revision numbers means something is up with the PM team - they are looking at it in a new light now, and patience is all that is required.
adding to Anon's REPLY ROFL...ah..So true.
Anyway I'll just add this:
1. My router says D-Link on it
2. D-link got my $$$
3. Where's the Support for consumers at Ubicom.com
Where anywhere on the packaging, literature, or router itself does it say for support contact Ubicom...It doesn't.
This is D-links responsibility, they are the ones who should have tested this "base code" from Ubicom more thoroughly prior to it's release, D-link is the one with Ubicom Support not us, and they should be Flaming Ubicom's forums IF IN FACT ubicom is at fault.
It's rather easy to point the finger at someone else, especially when consumers have no real way of verifying claims.
Ubicom's error or not THIS IS 100% D-LINKS RESPONSIBILITY
*did you read that carefully?*
-
? 1.02 just as bad as 1.20. You sure thats what you meant? Anyone can look back a few pages and see the fall came when people upgrade to f/w after 1.02. Remember 1.03 and 1.10...
What I meant was the move from 1.02. Not the 1.02 itself. I would love to go back to 1.02 which was the best version I have seen. It's been downhill after 1.02.
-
If you haven't done so already, please PM Lycan the serial number of your A1 unit.
I've sent mine, just curious what's the game plan with the SN#'s? Recall, refund, special SN based update based on A1 hardware...what? :) Thanks.
-
I'm curious about the game plan as well. I sent a pm with my A1 Serial number yesterday.
-
OK so after looking through this thread I've gathered all the common issues all of you have posted. Please feel let me know if I've missed anything.
RELATED ISSUES EVERYONE IS HAVING:
- TX dropped packets in the wireless as well of RX packets
- 3+ hours of wired and wireless use the unit becomes
unresponsive. (Cannot access router GUI, web pages don’t load and Latency)
- Gaming is still having lots of disconnect issues,
and high latency
- UPnP Functionality issues.
- Quirks with the CAPTCHA authentication
Also to confirm is everyone here using A1 hardware?
Using H/W Ver. A1 S/N F3OB179002646
These are my stats after approx. 15 mins. of up time after reboot of router using f/w 1.21 beta
LAN STATISTICS
Sent :5953
TX Packets Dropped :3
Collisions :0
Received :0
RX Packets Dropped :0
Errors :0
WAN STATISTICS
Sent :1642
TX Packets Dropped :0
Collisions :0
Received :52644
RX Packets Dropped :0
Errors :0
WIRELESS STATISTICS
Sent :50278
TX Packets Dropped :10
Received :48550
RX Packets Dropped :0
Errors :816
-
Sent s/n. Had to reboot again today.
-
1.quirks with the CAPTCHA authentication
2.UPnP functionality
3.The wireless speeds suck still,
and performance drops off almost immediately.
4.N is just completely messed up, and for some reason in
the Status page, it ALWAYS shows a channel
difference of 4 channels, since 802.11N requires
channel bonding to TWO channels.
5.Gaming is still having lots of disconnect issues,
and high latency.
6.Wireless, and that was decently okay for gaming.
The spikes still happen, very badly.
Doesn't quite lock me out of wan, but the latency gets so bad,
that I check the tab, and it shows it's broadcasting
and connecting at around 18 Mbps.
That's pretty bad, and really needs to be fixed.
7.Network connected HDTV that used to get speeds in the 240-270 mbps range
on wireless-N (5GHz) with firmware 1.15 and below now only gets 6-13
-
I've sent mine, just curious what's the game plan with the SN#'s? Recall, refund, special SN based update based on A1 hardware...what? :) Thanks.
Can we get an answer to this question especially now that LYcan wants our personal information, and CLOSED THE MAIN THREAD with all the issues.
-
Maybe d-link will replace our a1's with a3's or something.
-
Maybe d-link will replace our a1's with a3's or something.
I got my A1 replaced with an A2. I didn't know they made an A3..
-
Oh come on ... please not -.-
I'm from Germany and I have A1 ... I bought this router during my visit to Canada so I guess I have a problem now if there won't be a firmware which fixes stuff ....
Is there any way of replacing this one from Germany? The router's not even a year old!
(Sorry if there are some mistakes, it's 3 in the morning here and I'm tired ....)
-
ok i remove it just to make u happy. if dlink can't fix it just let me know so i can move on.
-
I got my A1 replaced with an A2. I didn't know they made an A3..
No need to get excided as it was just some wishfull thinking on my part. We all need a router that we can rely on 24/7 and we don't have one right now.
-
One last thing we're going to need. The people that have wireless issues please post a "screen shot" of the TX RX statistics located in the Status > Statistics
-
Ok, dumb question... How can i post the attachment? It gives me an error saying that the directory for the attachements isn't writable. Again, sorry...
-
3min after a reset.
(http://i43.tinypic.com/513875.jpg)
-
Rebooted yesterday
Sent :3016386
TX Packets Dropped :0
Collisions :0
Received :1695383
RX Packets Dropped :0
Errors :0
WAN Statistics
Sent :1349507
TX Packets Dropped :0
Collisions :0
Received :3969846
RX Packets Dropped :0
Errors :0
Wireless Statistics
Sent :351403
TX Packets Dropped :578
Received :205853
RX Packets Dropped :30
Errors :2018
-
One last thing we're going to need. The people that have wireless issues please post a "screen shot" of the TX RX statistics located in the Status > Statistics
My screen shot of the statistics is after 27 minutes of uptime since last reboot.
(http://i42.tinypic.com/a2srq9.png)
Edit: I also have an A1 hardware version since I have not made note of it prior. Do you still need anymore A1 serials?
Edit2: Here is after 5 hrs worth of uptime. The only wireless devices that were used was a laptop for 15 minutes web browsing and 2-3 hrs of COD4 on Xbox Live.
(http://i44.tinypic.com/2cwn9r4.png)
-
3min after a reset.
(http://i43.tinypic.com/513875.jpg)
3.5hrs later
(http://i44.tinypic.com/sfhu9y.jpg)
-
One thing I've noticed is that on earlie fw versions I had a lot of lan errors but no slowdowns and with 1.20+ I have few lan errors but they start to creep up just before it locks up.
-
screenshot after 9 days 11 hrs uptime
LAN Statistics
Sent :106127
TX Packets Dropped :3
Collisions :0
Received :0
RX Packets Dropped :0
Errors :0
WAN Statistics
Sent :11623068
TX Packets Dropped :0
Collisions :0
Received :19149242
RX Packets Dropped :0
Errors :0
Wireless Statistics
Sent :17249079
TX Packets Dropped :196621
Received :10297884
RX Packets Dropped :30278
Errors :16760
-
3.5 hours uptime. Power outage while we were out, very light wireless.
LAN Statistics
Sent :144558
TX Packets Dropped :3
Collisions :0
Received :115015
RX Packets Dropped :0
Errors :0
WAN Statistics
Sent :106111
TX Packets Dropped :0
Collisions :0
Received :960580
RX Packets Dropped :0
Errors :0
Wireless Statistics
Sent :14329
TX Packets Dropped :1
Received :4732
RX Packets Dropped :0
Errors :81
-
I've also noticed that with this fw that a lot of lan tx packets are dropped.
-
my router just reseted by it self
and i didnt pull the ac plug out
did this happen to anyone else?
-
my router just reseted by it self
and i didnt pull the ac plug out
did this happen to anyone else?
yep a few times when it changed (due to aome reason i don't know) the WLAN channels ...
Statistics after 4 Day 18 Hour 29 Min 57 Sec
LAN Statistics
Sent :7539965
TX Packets Dropped :4
Collisions :0
Received :5415621
RX Packets Dropped :0
Errors :32
WAN Statistics
Sent :4866320
TX Packets Dropped :0
Collisions :0
Received :11975900
RX Packets Dropped :0
Errors :0
Wireless Statistics
Sent :1223811
TX Packets Dropped :6390
Received :912395
RX Packets Dropped :5030
Errors :2299
-
my router just reseted by it self
and i didn't pull the ac plug out
did this happen to anyone else?
My Router has experienced these auto resets on several occasions also!
Here are my stats after 13 hours of up time
LAN STATISTICS
Sent :21410
TX Packets Dropped :3
Collisions :0
Received :0
RX Packets Dropped :0
Errors :0
WAN STATISTICS
Sent :75712
TX Packets Dropped :0
Collisions :0
Received :1264225
RX Packets Dropped :0
Errors :0
WIRELESS STATISTICS
Sent :335803
TX Packets Dropped :414
Received :264595
RX Packets Dropped :12
Errors :1525
Copyright © 2004-2008 D-Link Systems, Inc.
-
(http://i44.tinypic.com/2i9l652.jpg)
This is about 3 hours after reboot. I have no idea why I'm seeing so many LAN errors and Dropped packets.
I have another brand router I have been using and after 48 hours of it being in use, there were 0 dropped packets or LAN errors. Wireless had a few errors, but it was less then 20.
Please get this fixed guys.
-
my router just reseted by it self
and i didnt pull the ac plug out
did this happen to anyone else?
Yes. When I'm experiencing the slow down and I use the OLED screen and move around inside of it to the clock and logs sections it will automatically shut itself off and reboot. This only occurs when the logs report that it starts rejecting packets and I notice web pages slow or failing to load. Give it a try next time you see your router slow down and see if it reboots itself while moving around inside the OLED screen.
-
could anyone try and tell me if the next firmware will fix this router the A1
or we will have to go and replace the entire device?
-
The router just died after 10 days uptime.
It basically just died eventhough it's said online, but you just can't connect to it.
Power cycle is the only way to do restore it back.
-
Hell my router died this time after only a day of uptime. I've noticed that when I dl large files but stay connected it will slow down but still run. Once I shut my pc down the router will stop responding and requires a reboot. This is way past getting old and shame on d-link for not properly testing the fw before releasing it. D-link should either trade us for new revised hardware or give us refunds for the router.
-
2 days 15 hours up time and now I have to reboot
LAN Statistics
Sent :4407627
TX Packets Dropped :0
Collisions :0
Received :2640572
RX Packets Dropped :0
Errors :0
WAN Statistics
Sent :1855275
TX Packets Dropped :0
Collisions :0
Received :6582262
RX Packets Dropped :0
Errors :0
Wireless Statistics
Sent :866252
TX Packets Dropped :1878
Received :544417
RX Packets Dropped :1477
Errors :6833
-
Ok, 5 minutes after reboot only 2 wire devices hooked up at this time. A printer and a wireless bridge hooked up to my TV. Neither are being used.
LAN Statistics
Sent :11963
TX Packets Dropped :15
Collisions :0
Received :9753
RX Packets Dropped :0
Errors :0
WAN Statistics
Sent :4662
TX Packets Dropped :0
Collisions :0
Received :9222
RX Packets Dropped :0
Errors :0
Wireless Statistics
Sent :1238
TX Packets Dropped :0
Received :505
RX Packets Dropped :0
Errors :31
-
Mine has also randomly rebooted itself lately on its own.
-
Well folks had to roll back to fw 1.20, 1.21 was just to unstable and unreliable. at this point I am left speechless except for a few expletives deleted that come spontaneously. been cruising different sites looking for another router. This really sucks
-
Hey guys... I was wondering what is the status on a solution to the FW issue we have. I know we have seen our contact info being asked for as well as S/Ns. What will the purpose of that will be? What are you guys cooking up? ???
-
Wow, really?
The week just started... maybe give them a few hours to... I don't know... get to work
Also remember this is not the only board they have to look over. Should check out the $%!*storm in the Dir-655.
-
CENSORED
I'm sorry but stuff like that is what keeps us in the dark. I know that we are all in a crunch but we need to keep our cool in order to get answers. Like it's been said before, this forum doesn't even need to be open. It's way to early in the week to start off like that.
*** modified by Fatman to remove a quote that has been censored.
-
are you guys for real???????????
the beta was released on the 12
today is the 22 and the beta is worse than the 1.20
this forum has to be here it is dlink responsibility to fix this and give answers to
customers 24/7
especially if there is a problem like this
there should be a team working around the clock to fix this
this has gone long enough!!!!!!!!!!!!!!!!!!!!!
-
are you guys for real???????????
the beta was released on the 12
today is the 22 and the beta is worse than the 1.20
this forum has to be here it is dlink responsibility to fix this and give answers to
customers 24/7especially if there is a problem like this
there should be a team working around the clock to fix this
this has gone long enough!!!!!!!!!!!!!!!!!!!!!
You keep telling yourself that.
-
Although fw 1.20 is no bargain, I don't have the uncommanded reboots as before, The numbers are still atrocious. this is after a little less than 5 hours of up time!
TRAFFIC STATISTICS
Traffic Statistics display receive and transmit packets passing through your router.
LAN STATISTICS
Sent :12483
TX Packets Dropped :3
Collisions :0
Received :0
RX Packets Dropped :0
Errors :0
WAN STATISTICS
Sent :34940
TX Packets Dropped :0
Collisions :0
Received :581303
RX Packets Dropped :0
Errors :0
WIRELESS STATISTICS
Sent :191794
TX Packets Dropped :664
Received :166691
RX Packets Dropped :19
Errors :2234
Copyright © 2004-2008 D-Link Systems, Inc.
-
it's a good thing i dont have your view of life
annon
:)
-
You clowns just go ahead and piss off the moderators. I'm sure that will get the problems fixed faster. Me, I'm patiently waiting. Go ahead and check routers made by other manufacturers. They seem to have their share of problems also.
-
Don't worry, we will get through this, though I will caution that name calling against mods will get your forum privileges revoked, there is simply no call for it EVER. As I have said before, they guys here to help you on D-Links payroll don't even get to influence these things directly, abuse to them will not be tolerated.
Also, I realize that I am not going to be responding to the person who made the statement, but I still feel the need to respond to it. This forum is a community for users to help each other, the mods here are not a Tech Support team for your fora pleasure. If you want to complain call customer service, if you want to have a problem troubleshoot call technical support.
D-Link is under no onus to respond to anything on these boards, the mods post as themselves, they ban as D-Link agents. We are given the freedom to speak as ourselves, and we participate where it amuses us to do so, or where we think we can help. Every D-Linker could quit posting right now and we would not be violating anyone's expectations. If you need to communicate with D-Link, use one of the above numbers. If you want to communicate with experienced users of the same products you use (regardless of their status as D-Link employees or not) then I suggest you act in a civil manner and enjoy the forums we are all building together.
Thank you those of you taking the level-headed approach. You are the users who make this forum possible.
-
"Fatman" is right. There are people on this forum with D-Link products that fail altogether just as often as yours merely reboots. People who have replaced their switches six or seven times, and patiently wait for the next one to die without complaining. The DES-1228P, for example.
As "Fatman" points out, D-Link is under no onus to respond to anything on these boards. Nor apparently, are they under any onus to fix design flaws, even when (like the DES-1228P) the failure rate exceeds 100%. Not before they release the product, and certainly not after.
Heed ray3rd's advice. Wait patiently until D-Link fixes the problem. Just because they keep people waiting until their warranties run out with other models, doesn't mean they're doing it with THIS one.
As ray3rd points out, just because you're being ripped off, there's no reason to "piss off the moderators".
-
lol, he said name calling against mods (you probably wont get that unless you've been here a while).
Great, now my comment under the persons who got deleted looks strange.
I don't remember any name calling in that post, other than it being more crazy talk.
-
D-Link representatives: may we please have a status update?
-
Cool your jets RogerStrong, I understand you are upset, but I would seriously contemplate eating my own shorts if you have received any DES-1228Ps that went into Christmas mode since April. That is all I can say on the issue, now could you give it up or at least quit threadjacking? I have been patient with you, but this is the wrong thread to start this in.
-
Great, now my comment under the persons who got deleted looks strange.
Sorry Anon, I debated with how to fix your post that wouldn't look weird, and I decided that a quote from that ex-member wasn't worth sweating over.
I don't remember any name calling in that post, other than it being more crazy talk.
I don't know if anyone else caught it but he was directly calling names on Ru-Fi-Oh, which is hard to belive if you know the guy IRL, he is one of the more agreeable people I know.
lol, he said name calling against mods (you probably wont get that unless you've been here a while).
I wasn't even going for that reference, your memory is longer than mine.
Oh and before I go, I almost forgot.
D-Link representatives: may we please have a status update?
I wouldn't know I don't work with these products, but I can tell you that as soon as we have anything prepared, I expect you will see it front and centre here before anywhere else.
*** modified by Fatman because he always put every verb in the correct tense.
-
I would seriously contemplate eating my own shorts if you have received any DES-1228Ps that went into Christmas mode since April.
The switch that died today was received April 13th - a replacement for a replacement for the original. (Another died in May - the third in that one's location. We'll see how long its replacement lasts.)
On the off chance that this is a new revision that fixes the problem - we've heard this before with this model - it still begs the following question: Where's the recall? We have three more. Must we wait each of them to fail, each with a massive disruption to the company, or will D-Link replace KNOWN BAD hardware so that we can schedule the replacement for off-hours?
That is all I can say on the issue
Why?
If the problem is - in theory - fixed, WHY is D-Link unwilling to let people know?
They owe their customers at least an explanation.
This is the wrong thread to start this in.
It's relevant. People with this product are having the same problem we're having with our product - a company that released a defective product, shows no real sign of fixing it, and are stalling people until their warranties run out.
You've said elsewhere that there's no official D-Link presence here; that the forums for D-Link users to interact, share stories and assist each other. That is what I'm doing. It may not be what D-Link wants to hear, but it's relevant to the users.
-
Ignore RogerStrong, he is going to be taking a break for 3 days and will take a permanent one if threadjacking continues to be his MO. Lets get this thread back to the DGL-4500, I am tired of mod duties today.
-
I was just going to reply to RS, that this forum is for the DGL-4500 not the DES-1228p. I believe there is a forum for that item somewhere else.
-
There is (I can only assume he starting threadjacking because he wasn't getting enough views there). I am not trying to censor dissent, merely enforce common (and commons sense) forum etiquette rules. If someone posted about the DGL-4500 in an DES-1228P thread I would have had the same reaction.
But back to the topic at hand, how is Firmware 1.21's beta treating everyone here?
-
Up to know I'm getting allot of wireless Rx and Tx. I haven't seen automatic reboots but it gets to a point where it stalls. I think everyone has the same or similar problems since 1.20 and 1.21. Hope we can get some fixes.
-
But back to the topic at hand, how is Firmware 1.21's beta treating everyone here?
I'm having the same problem I had with 1.20: after a couple of days, things slow down, the GUI becomes inaccessable, and a power cycle is required to get the router going again.
-
@Fatman,
Sorry, I meant nothing serious by the last set of comments I made.
...just tired of all this really.
Oh, and the dgl-4500 with me just did a re-boot. Nothing special, was on the web (router is view) and then router went through the off/on motions.
I don’t really say much to mods here (no name calling lol). Tech support is pretty much the only group I see fixing anything at this point and I’m not talking about the script readers d-link likes to pass off as “techs”.
-
I just rolled back to 1.20 because 1.21 is just too unreliable.
-
One of the things that has drove me most crazy about this new firmware is I have to reboot the router constantly to connect to my printer via shareport. It will always show my printer and will connect immediately after reboot, but if I try to connect after a day or so it will try to connect, act like it is going to, but the status just goes right back to "available". It is very frustrating because everything worked properly prior to 1.20 and 1.21 beta. I'm not sure if this is something with the latest shareport build, but with all the other issues concerning these latest firmware builds I thought it would be more appropriate to post this here.
-
I had to reboot my router again, I got about 2.5 days out of it this time. Same symptoms as usual, HTTP traffic goes dead and I was unable to get to my router by through the HTTP login. I tried to view stats from the device itself and almost every stats page was empty.
I also noticed last night that my network was extremely sluggish, although my ping times didn't reflect that. Yet using SMB shares or other protocols took very very long to respond. After a reboot this morning, the response are back to under 1 second.
-
so am i to assume the new update doesn't help yet.
I just came back from vacation and it was hard to remember to reboot my router remotly every two days.
I am one of those who sent in configs.
Do we not have a fix yet.
This is getting ridiculous
At least give us back the option to an older firmware untill a new one is fixed
or create a new firmware that will change thing back to the way it was for the time being because this is just getting out of hand.
I can go out an buy a new router for 200 and would elivate the headaches and i am almost at that point.
-
hikari as i read on one of the pages before it seems as if its not dlinks fault we cannot roll back ... so probably no way ... if i HAD money, i would go buy the DIR-855, but i don't so i have to wait together with you all -.-
-
I plugged out the router and changed it to AEBS.
Had enough of it and keep guessing when this DGL is going to die.
-
Had to reboot again tonight. It is 2 1/2 days since last reboot.
-
Ugh, mine just locked up again, no access to the web gui, as usual.
-
hikari as i read on one of the pages before it seems as if its not dlinks fault we cannot roll back ... so probably no way ... if i HAD money, i would go buy the DIR-855, but i don't so i have to wait together with you all -.-
You would do well to read some other reviews on the 855 first before dropping your cash on it.
-
You would do well to read some other reviews on the 855 first before dropping your cash on it.
VERY good point to follow.
-
This is just to post status of my router using beta firmware 1.21 H/W: A1.
I've have had it up and running for 8 days and counting ( I know 8 days is nothing. I will keep pushing this without forcing a reboot until we get new firmware). I did notice the WAN slowing down but not locking up and avoided doing a reboot to see how long I can push the router and so far it's been manageable as far as browsing and downloading torrents over wired and wireless connection. The slow down doesn't bother me because it happens for about 5 seconds then goes back to normal. I do see how this can be an issue with gaming and noticed it there as well.
Status page:
(http://i24.photobucket.com/albums/c43/isoh/status.jpg)
Statistics:
(http://i24.photobucket.com/albums/c43/isoh/stats.jpg)
Wireless Stats:
(http://i24.photobucket.com/albums/c43/isoh/wireless.jpg)
-
I've have had it up and running for 8 days and counting
Wanna trade 4500's?
-
WOW, 8 days is great. How about trying it in multimode. My Wii only uses "g" and my sons Nintendo DS only uses "b". And the computers use "n".
-
You would do well to read some other reviews on the 855 first before dropping your cash on it.
well ... if you had to recommend a router to me with dual 2.4 / 5 ghz at the same time ans gigabit lan which one would be it? screen is defenitely not neccessary ...
-
WTF ? My router just rebooted itself. Weird.
-
WOW, 8 days is great. How about trying it in multimode. My Wii only uses "g" and my sons Nintendo DS only uses "b". And the computers use "n".
IEEE 802.11b traffic pre-empts draft N. Your entire network loses N capability while an IEEE802.11b device is associated. You could be running an IEEE802.11g/b router with no difference in wireless capability.
-
Thanks, didn't know that. But its a good thing he doesn't use his Nintendo DS too much.
-
To make matters worse it just occurred to me (as the DS does not support WPA) that means you are either running no security (not a great idea in most circumstances) or are running WEP (which also pre-empts Draft N also).
-
well ... if you had to recommend a router to me with dual 2.4 / 5 ghz at the same time ans gigabit lan which one would be it? screen is defenitely not neccessary ...
I've heard good things about the Airport Extreme, http://www.apple.com/airportextreme/. It's similar to the dir-855(two radios, gigabit wan and lan ports), but cheaper and the Airport Extreme does not have QoS or an OLED screen.
Wow! 3/5 rating on newegg for the dir-855, and it's $250! I thought the 4500 was a lot when it first came out.
I wish I would have gotten the Linksys wrt600n and put ddwrt on it, but I've heard they changed the hardware so it's not possible anymore.
-
As posted in another thread.
I've had 12 days Uptime, but I'm still getting lockups. The lockup just occurs farther between than other users.
I caught the router locking up today. I logged into it, and attempted to retrieve the logs, where the router reported that it was running low on memory. A second attempt specified that the router was out of memory and then completely locked up. Depending upon your usage of the router, this might explain why different usage patterns can lead to widely different experiences.
I get a lot of extraneous logged due to 2 FIOS settox boxes broadcasting on what the -4500 considers an unroutable network. It should just ignore the traffic, but it logs an entry, once every few seconds. Additional traffic due to what happens on the network or WAN facing can lead to a very full log. I don't see any way to trim or adjust the log retention values. If I uncheck INFO, I don't believe this actually reduces the level of logging, it only reduces what is displayed. The logging information is still kept in the router memory.
-
Ru-Fi-Oh, may I ask what hardware revision you're testing with?
Thanks!
-
This is just to post status of my router using beta firmware 1.21 H/W: A1.
-
There is a Nintendo DS that actually does support WPA now. It's the Nintendo DSi. I found this out not too long ago.
-
It is a much bigger improvement that I had realized, they did not stress the important features enough and instead only advertised the cameras.
-
Ha. Take that Pfft ! ;D
-
Oh, thanks, weoh! Somehow I missed the A1 info. Ooops!
OK, well, this is a puzzle then, isn't it? We're having _almost_ no post-1.20 success stories with A1 hardware.
Ru-Fi-Oh's device seems to be behaving differently.
It appears that it's not a unusual scenario that's causing the problem, because the issue seems to be so widespread.
Were there bad batches of DGL-4500s?
Is there a D-Link rep here who would be willing to send me an A2 (or more recent) for testing? I seem to be having very consistant outages with my A1, so I may be a good candidate for a real-world study.
-
If you PM'ed Lycan your personal info before, you should be getting another PM back asking for your email. ;)
Still waiting...
-
OK, well, this is a puzzle then, isn't it? We're having _almost_ no post-1.20 success stories with A1 hardware.
Depends on what you define as success.
I have an A1 router. It has also locked up twice now with 1.20, but I can also demonstrate 10-12 day uptimes. After my last bout with it locking up due to running out of memory, I'm playing around with the log functions to see if I can isolate that issue. Unlike everyone else though who I believe has an A1, my router had major issues with every firmware between 1.02 and 1.20.
-
Well lycan pm'd me for my email and told me he was swapping out my a1 with an a2. I'm hoping that it will behave better than my a1 has. Just today with only two days uptime on 1.20 my son and I were trying to play css at the same time. It locked up the router forcing me to power cycle it to get going again.
-
My A2 that got switched out did not work at all. I NEVER had reboot problems, however the WAN slowed down, and locked me out of LAN as well. More than likely your A2 will come shipped with 1.12. After that, go ahead and stick with 1.15. Do not go to 1.16, and definitely do not go to 1.2x+
-
??? Info was sent on the 18th, no PM received...yet. I've been following all of these threads since day one waiting for the fix to come.
Now mama ain't happy,(with the network) so nobody's happy. Please help!
-
Actually 1.16b worked best for me of all the post 1.02 fw I've used. I'm hoping that the new unit will behave correctly and I will be able to stop babysitting it.
-
Reinvented, Is your A2 working as it should?
I posted a new Thread question in the 4500 forum but the Mods removed it. Not sure why I feel it's a valid question and I broke no rules so here it goes.
I sent in a complaint to the Better Business Bureau (BBB) against D-link and within 24 hours they responded that my router was defective and they sent me an RMA A2 with 1.12FW. I'm worried that the A2 routers are having the same problems as the A1 but I'm not sure.
- What are the differences in the Hardware version for the 4500?
- Are there others in here with the A2 having these problems?
- What firmware is most successful with the A2 hardware?
- Can the 1.12 be downgraded? I know 1.15 can't but not sure about 1.12
The A2 router should be here soon, I'll post if it works as it should or not here.
My complaint is still active but I have updated it with D-links response which I found positive, at least compared to here and the support numbers I've wasted hours on. I will keep this complaint active until my issues are completely resolved.
I Call On Nerds Everywhere And Trash Egos Regularly
No, my A2 does not work with 1.2x +
There are no hardware differences at all. Just different shipping firmware. Most people here, and should have an A1. 1.12 can not be downgraded to 1.02. 1.12 was just as bad. The best out of all of these so far, would definitely have to be 1.15. Again, as I mentioned - stick with that.
-
Back from vacation I do have an A1 and info has been PMed to Lycan
-
(http://i42.tinypic.com/jucuoo.jpg)
After about 3 days of uptime, complete lock up. I was able to get the above screen shot by disabling all of my wireless devices and using a ethernet connected computer to get into admin pages. I got several disconnects in trying to do so and had to refresh the page several times to get any info to show up.
-
I have PM'd Lycan, with my info, and yes its an A1
-
Don't worry, we will get through this, though I will caution that name calling against mods will get your forum privileges revoked, there is simply no call for it EVER. As I have said before, they guys here to help you on D-Links payroll don't even get to influence these things directly, abuse to them will not be tolerated.
Also, I realize that I am not going to be responding to the person who made the statement, but I still feel the need to respond to it. This forum is a community for users to help each other, the mods here are not a Tech Support team for your fora pleasure. If you want to complain call customer service, if you want to have a problem troubleshoot call technical support.
D-Link is under no onus to respond to anything on these boards, the mods post as themselves, they ban as D-Link agents. We are given the freedom to speak as ourselves, and we participate where it amuses us to do so, or where we think we can help. Every D-Linker could quit posting right now and we would not be violating anyone's expectations. If you need to communicate with D-Link, use one of the above numbers. If you want to communicate with experienced users of the same products you use (regardless of their status as D-Link employees or not) then I suggest you act in a civil manner and enjoy the forums we are all building together.
Thank you those of you taking the level-headed approach. You are the users who make this forum possible.
I was trying to say this in an earlier thread - all the hating and clamoring for a fix - yes, we're *all* frustrated - but thanks for putting it so eloquently that the boards here are *discussion* forums and not lunatic ranting forums.
To make matters worse it just occurred to me (as the DS does not support WPA) that means you are either running no security (not a great idea in most circumstances) or are running WEP (which also pre-empts Draft N also).
Yeah, I have a few issues with a couple of iPaqs (HX 2490C) that I have upgraded the OS on but that "supposedly can use WPA" but in actuality only use WEP....I learned the hard way that N and WEP don't mix.
If you PM'ed Lycan your personal info before, you should be getting another PM back asking for your email. ;)
Still waiting...
Me too - I was one of the very first ones to send the info.
If the email has already been sent it is entirely possible that it went to my junk box - but that has well over 1000 msgs right now.... -(
-
Well after two days of uptime my router just rebooted all by itself while I was playing css which kind of upset me. This is all so very lame and needs to corrected quickly.
-
Any news ? Any news at all ?
-
I've been doing some serious testing on my DGL-4500. After experimenting with various settings The router was experiencing a rare form of lucid operation. It was running for a few days with numbers I had never seen before IE: Rates holding stable at 300mb/s at signal strengths at 100% my downloads were outstanding and my Tx / Rx drop packets were virtually nil. I thought I had hit on the correct combination of settings. But alas it didn't last! This piece of equipment ( I'm being generous calling it that ) has a mind of it's own. I'm at the end of my rope. GOLLY
-
The last time I turned off my router (DGL-4500) was 3 weeks ago while I need to replace my old power strip with a new one...and i just checked the router status and uptime 's stable still today...
(http://i43.tinypic.com/e9axat.jpg)
don't get me wrong...I'm not try to pouring gasoline into the fire in this Firmware issue,
as a consumer, just want to raise a question why changing the whole firmware structure in the first place that DGL-4500 users need to take risk to update their firmware version,if something goes wrong, then can't switch back to default firmware version? ...
I'm glad that I did a reseach before I bought this router and simply just use it right out of box and never touch the firmware update (But in the other way,it's not sounds right either...JMHO
-
Yeah just about all of us wish we'd just stayed with 1.02.
-
My only gripe with 1.02 was how it would reboot my router when I tried to load a rtsp page.
-
My only gripe with 1.02 was how it would reboot my router when I tried to load a rtsp page.
Oh yeah I remember that. Did it ever get fixed in the later f/w?
-
Funny thing. Every night before I go to bed I unplug the router. Is that funny or sad ?
-
sad, definitely sad!
-
hey lycan, I sent you a PM
-
If you haven't seen Lycan's post regarding not taking serial info any more.. Please read the following link.
http://forums.dlink.com/index.php?topic=6229.0
-
Router slowed awfully and the GUI was inaccessable again this morning. Power cycled.
-
Any more improvements with the F/w?
-
Any more improvements with the F/w?
guess they'll let us know ... all the asking won't help us in any way ... it's just getting riddiculous of always reading such posts ... they need logs or whatever or nothing ... this asking flaming spamming etc doesn't help at all (including this post ^^).
-
The more I'm using it, the more I feel there's a memory leak.
I can lengthen the time in between lockups via, not enabling features.
Disable wireless, disable DNS, clear the logs, reset the stats and the router can go longer without lockups.
Basically anything that doesn't require saving state on the router.
I've been able to catch the router once while it was in the process of crashing, and it reported out of memory errors while attempting to display its log entries. I don't think there is a way to disable logging, only disable the viewing of the log entries. Anyone else having spurious data flooding their DGL logs?
I'll get on average about 15 log lines per minute, which can add up. Things like having my settop boxes update, talk to each other, having a torrent going can quickly multiply the lines fast. There isn't any way of determine the buffer use of the logging within the router, nor any way to configure it to be a fixed size or not record INFO type messages. I'd rather those messages not be stored at all.
-
does this router offer crash recovery mode, so then I can go back to firmware 1.15.
There were two ways of doing it, a safe way and a unsafe way.
I remember the unsafe way was by putting an older dlink router di-624 rev c into crash recovery mode by unplugging the router ten seconds after starting a flash process. In flash recovery it gives you a generic page which lets you flash it with any firmware, but you run the risk of damaging the router
these are the instructions on how to do it the safe way
[Step 1]
Connection Must be with LAN Cable, Not WiFi
[Step 2]
Before Flash, Go to [Tools|System]
press [Restore] To Factory Default Settings First.
[Step 3]
Statically assign an IP address to your computer
IP: 192.168.0.100
Subnet Mask: 255.255.255.0
Gateway & DHCP Server: 192.168.0.1
To Crash Recovery Firmware Update (Must Thru LAN, Not WiFi):
[Step 4]
Unplug the power from the router. KEEP HOLDING the
[Reset] button and Plug the power back,
Continue holding for 12 seconds and then release.
[Step 5]
Open Internet Explorer and browse to 192.168.0.1.
You should now see the Crash Recovery page.
Browse to the location of the firmware on your hard-drive
and click the [Send] button.
[Step 6]
After loading the firmware, perform a "Hard Reset"
by pressing the [Reset] button at least 12 sec.
This ensures that the firmware is locked in.
You should Now see the Normal Router Config Page.
[Step 7]
The default Username is admin and password is blank (nothing).
[Step 8]
Go to [Tools|System] press [Restore] To Factory Default Settings again
[Step 9]
Reboot router & you can now Config you router again.
But, Do not load any "setting Backup" from any
Version Firmware after FW update or you are
asking for trouble.
-
i cant stand this firmware, is there a way of using a hex editor and changing the version number from 1.15 to a higher number to trick the d-link version checker, i cant stand this firmware, I need 1.15 back.
-
does this router offer crash recovery mode, so then I can go back to firmware 1.15.
Give it a shot and let us know how it goes.
-
can you put 1.02?
-
Seems like we tried doing this several months ago to no avail.
-
1) No, this router does not have a crash recovery mode.
2) No, you cannot roll back to any earlier firmware, once upgrading past 1.2x+
3) No, editing the binary will not work. If anything, you would brick your router due to a binary mismatch.
-
1) No, this router does not have a crash recovery mode.
2) No, you cannot roll back to any earlier firmware, once upgrading past 1.2x+
3) No, editing the binary will not work. If anything, you would brick your router due to a binary mismatch.
I would put it as more we're not allowed to go back.
D-Link should pressure the group they contracted those services for it. I don’t remember any f/w or seeing it mentioned as a feature that the dgl-4500 will have to be restarted every 3-6 days to maintain operation. But here we are….
It has been over a month now and we don’t have a fix, which was the same last year. Glad to see they still have the time to come out with new products but none to fix the old.
Has anyone been getting IP protocol 17 and IP protocol 6 for wireless connections near the time when a restart is needed? I was able to see it right before the router stopped me from accessing it through the browser. After the restart I’ve yet to see them.
-
I cannot believe I spent $150 on this router, d-link has let me down too many times now
-
I cannot believe I spent $150 on this router, d-link has let me down too many times now
i agree ... if dlink doesnt come out with a fix very soon, i guess i'll try my luck with netgear ....
-
i was actually looking into the linksys wrt600n
-
well, i have only read the first page, but, i am already convinced not to download this beta, i have 1.20, and it is running fine, at one point when i was connecting a PSP it went offline, so i did a hard reboot, as far as signal loss, ever since i put a set of HawkingTech's [HAI7SIP] Hi-Gain 7dBi Omni-Directional Antenna, i have not had any, i stress, ANY loss in signal. as stated from their website...
"Hawking Technologies™ HAI7SIP, 2.4GHz Hi-Gain WiFi antenna boosts your wireless signal strength from 2dBi (standard power) to 7dBi."
i have three of these. and i have not had any issues, soon i will get one more signal amplifier, i have two right now... DIR-625 is what i used before, i had an extra antenna, so when i got the DGL-4500, i already had the antenna's replacements. soon though, i will be blasting my signal.
those of you who are suffering this signal loss, i recommend you take a trip over to HawkingTech for their range boosting antenna's, D-Link for the routers, HawkingTech for the Antenna's.
Hawking Technology's Hi-Gain 7dBi Omni-Directional Antenna
http://www.hawkingtech.com/products/productlist.php?CatID=32&FamID=58&ProdID=214 (http://www.hawkingtech.com/products/productlist.php?CatID=32&FamID=58&ProdID=214)
-
i was actually looking into the linksys wrt600n
Had one. Had a Netgear before that. Both sucked hard for one reason or other. The only router that's been stable for me for years is an ancient Linksys WRT54G.
-
Kamikazi2142 if i work in the 5ghz spectrum will these antennas also work?
-
dlp you cant be serious a friend of mine has the wrt600n
and its way better than wrt54
much more stable mid enterprise router
its not even the same league
-
has anyone tried turning off DNS relay feature in the network settings, DIR-655 users claim that fixes the freezing & web gui loading problems after 3-4 days.
-
dlp you cant be serious a friend of mine has the wrt600n
and its way better than wrt54
much more stable mid enterprise router
its not even the same league
That's cool. Maybe I had a faulty WRT600N. :-\
-
has anyone tried turning off DNS relay feature in the network settings, DIR-655 users claim that fixes the freezing & web gui loading problems after 3-4 days.
If you do that then you have to enable a lan side dns or you will not be able to connect to the net.
-
has anyone tried turning off DNS relay feature in the network settings, DIR-655 users claim that fixes the freezing & web gui loading problems after 3-4 days.
Already a topic open : http://forums.dlink.com/index.php?topic=6205.0
-
If you do that then you have to enable a lan side dns or you will not be able to connect to the net.
In order for me to disable dns relay, I also need to disable advaced DNS service. However, after disabiling those and adding a primary dns from comcast, nothing can be brought up on the web (error locating local remote server).
-
do an "ipconfig /release" release followed by an "ipconfig /renew" and tell me if you are online then.
-
do an "ipconfig /release" release followed by an "ipconfig /renew" and tell me if you are online then.
Didn't work for me. Tried that and couldn't get online.
-
Kamikazi2142 if i work in the 5ghz spectrum will these antennas also work?
they state that they are for 2.5ghz, but i run them in 5ghz, they seem to hold up just fine.
-
So is there any update yet.
The fact there are so many posts all over about this also.
I am following one thread this one and that is work.
Please let us know whats going on it feels someone has dropped the ball with this update.
Update should of worked with out a hitch and not letting us downgrade is what makes it worse.
I have contributed log's and what not since the begining but have yet to hear from anyone.
-
When you run the ipconfig/all what does it say your gateway and DNS server informatmion is?
-
lol I check this forum every day. One day I hope to find a surprise. A new firmware.
-
lol I check this forum every day. One day I hope to find a surprise. A new firmware.
Same here, I am kinda getting tired of having to do a hard reboot on my DGL-4500 every day.
-
lol I check this forum every day. One day I hope to find a surprise. A new firmware.
don't we all :(
-
Someone should talk to the consumerist.com and engadget. They might be able to help
-
There is firmware in the works.. Don't have ETA but should be soon. We've been pressin' to make sure the next code is solid. Keeping fingers crossed!
-
There is firmware in the works.. Don't have ETA but should be soon. We've been pressin' to make sure the next code is solid. Keeping fingers crossed!
Glad to see it. Keep up the great work. I'll pass along the info to the dgl-4500 in my house.
-
Interesting new symptom (for me at least) for the every 2-3 day power recycle requirement.
Initially my v1.20 router would just lock up with no access to anything thereby requiring the power recycle to reagin functionality. The last several events have had a different symptom...I lose access to the interent, but retain access to the LAN. I can log onto the router configuration page, but eveytime I do it comes up with the "measureing link speed...wait a few screen" and eventually refreshes the router log on screen. Logging on to the router again produces the same message and effect. A power recycle fixes it all. Hope this might provide a clue to the problem in the firmware....
On another note......
I think we all need to be patient. When you have a problem that according to some posts takes up to a week or more to exhibit itself, even when you think you have a fix you must run it a long time under varied operating conditions to be sure your fix is viable. If it fails then you start over with more development time and even more testing time. I believe a permanent fix will eventually be found. At least we can keep operating with the power recycle workaround as irritating as that is.
-
http://forums.dlink.com/index.php?topic=6402.new#new
-
Downloaded will install tonight.
Does having A1 make a diffrence with this patch?
-
Doesn't matter.. mainly for A1 but works with A2
-
Something really strange is going on now my dgl-4500 has been up 5 days 14 hrs this round and is still working. This is the first time ever on 1.21b this has happened.
-
what hardware version?
-
A1 and I just received the replacement a2 today but its still in the box. I never opened it.
-
Had to restart mine yesterday.
All connectivity down.
Also been noticing my logs are fulling up faster then before.
I have yet to find the time to trouble shoot .
-
Someone should talk to the consumerist.com and engadget. They might be able to help
Funny you should say that. From the Founders of Gizmodo and Engadget please add your reviews at http://gdgt.com/d-link/dgl-4500/
Keep it clean, keep it factual, and rate this router, D-Link, and The level of resolution response along with any tips, hacks, or workaround you have found.
Won't you be My Neighbor! ;)
-
Well it's been 6 days and 9hrs so far and my router is still up. The only difference is that my son has been away so only my pc has put traffic on the router for the majority of this time. I'm thinking about just keeping it hooked up until it crashes to see how long it will last. This is very strange indeed especially after all of the problems I've had before this particular run.
-
4 day uptime with disabled dns-relay here ... now sending files via icq and downloading some stuff with 20 connections got it down... files stopped downloading, upload aborted, general slowdown
-
Puff,
if you could try NOT to reboot the router or make any changes.. Would like to see how long it will go for. Generate traffic like normal and when your son gets back ask him to do what he does on your network :D
-
Yeah I'd already decided to do that. I had the new one in my hands ealier and just put it back into the box. I'm gonna keep her running until she croaks. Nevertheless I'm curious as to why it is still running, 6 days 14hrs now when it never has done this before with any post 1.2x firmware.
-
Connection Up Time : 7 Day 4 Hour 17 Min 29 Sec ;D
I did want to add that I unchecked the informational setting in logging before I started this run.
-
and you are running 1.21b02 beta 1?
-
Firmware Version : 1.21NA, 2009/06/02
It's the first 1.21 beta and for some strange reason it's actually working for me now. It did not work prior to this particular run and would crap out on the 4th day if not before each and every time. It took me by surprise when I checked the status page and saw just how long it has been running this time. Did all of the planets line up just right or did I hold my mouth in the right position this time? Like I've already stated I'm going to let this run its course before I install the new a2 unit.
-
I have not yet updated to the 1.21b02 firmware (about to); still on 1.20, and getting the freezes every 24 hours or so). However, I wanted to point out that when the internet drops / router locks-up, and I goto the device itself and cycle through the options on the led screen with the physical buttons, it will reboot automatically when I cycle to the date/time section; figured I would share that symptom as hopefully it may lead to the root of the problem. Model is A1.
-
Connection Up Time : 8 Day 2 Hour 53 Min 06 Sec
The error count is starting to go up a little bit now but she's still running strong.
-
How many PCs do you have connected?
-
I only have two wired clients hooked up at this time. One other thing that i did was remove the router from its wall mount and place it on the stand with nothing around it to block the airflow to it. It's locked up before since being moved to the stand so this time just doesn't make any sense to me but I'm not going to complain about how longs its been up. I might just try loading livenewscameras.com just to see if a rtsp page kills it.
-
Did it have any slowdowns with that many in the past? Also are they widows or macs?
I just want to see what it is you're doing different to have it not degrade in performance.
-
I run all windows clients, vista ultimate x64 and my setup has not changed with the exception of my oldest son moving out and no longer being on my network. In the past it didn't matter whether or not it was two or three clients the performance would degrade in the same way. With this particular run my performance has not degraded and my router is approaching 9 days uptime with no issues so far. I have noticed that my error count is starting to creep up but the router is not affected.
-
Connection Up Time : 9 Day 2 Hour 28 Min 02 Sec
-
I was about to post my DFL-800's uptime as a joke of sorts, but someone reset the darned thing 3 days ago. Now who is laughing?
-
Connection Up Time : 10 Day 1 Hour 24 Min 53 Sec and right after I copied this the router froze up. I went ahead and installed the new A2 unit and put it back into its box. The A2 is running 1.12 and I'm not going to change that unless it starts acting up
-
I have downloaded and installed the 1.21 Beta and the problem still persists. In fact it seems like its even worse. Before i had 1.21 i only needed to restart the router every 2-4 days. Now it seems like the router restarts itself multiple times in 1 day ???
I really had hope that this router would one day be what its advertised to be. When this router does work though it is just simply amazing, but thats rare. I get kicked off of all my wireless things and even the wired computer.
Now looking forward to another beta :'(.
Is there anyway i can get a replacement that has 1.12 or 1.15 firmware?
-
I am running 1.21 Beta i have 6 days 4:15:43 everything good so far!..... a lot of error everytime i try loading 192.168.0.1 i get a spider man picture (wonder what went wrong here) jk but yea i get slow downs but mostly its doing fine but still i did not *** pay 150 for a router that will just die. :)
-
DHCP or PPPoE?
-
I'm still having to type my password 2-4 times before it's accepted. I just typed it 4 times. I'm running Safari 4.0.3 and Mac OS X 10.5.8. Before 1.20 I had no problems.
Home page 192.168.0.1 will stop loading in a few days.
I did the 30-30-30 trick, re-flash the firmware and manually configure the router. That help some but I'm still having issues like the ones mentioned above. My wireless performance is erratic at best. Sometimes devices have no problems connecting but other times they do and seem very slow.
-
Running 1.21NA, I'll usually get about 9 days of uptime, give or take a day or two. After 6-7 days of uptime, however, internet speeds start to show signs of slowness. By the 9th day, you really notice overall network lag (on both LAN and WAN), and the system will usually restart on it's own. I always know how close my router is to death by how slow the admin page loads (and when it doesn't load the page at all, a router crash/reboot is imminent in the next 3-5 minutes).
Yuck!
-
Oh, and I should add that I too have to re-enter my password up to 3 times from time to time. It's not browser dependent either, as I've tried it on various different OS's (Vista, OSX, 7, Gentoo). It also tends to not happen immediately after a crash/reboot, but will happen after a soft proper reboot.
-
Well guys I am here because today like a rookie I upgraded my firmware to 1.21NA from 1.02. I did not do my research was having issue with my ftp server so thought I would try it. Now I am getting 3mb/s out of 10 or less using wireless. Very very sad I believe that I just made the worst IT mistake I have ever made and there is no fix. I actually love this router it is the best I have ever had and I have had uptimes of 50 days or more without reset. I don't want a new firmware at all just a way to role back to 1.02 and i'll be so happy. This seriously just popped my life balloon. Please D Link if you read this just make it so we can role back don't worry about any advancements. Now my router is like the Linksys routers I used to have. Man what a huge let down. :(
Please bring back 1.02 ;D
-
Here's my feedback on 1.21NA ... it sucks. It's the worse firmware since 1.01, and may actually top 1.01 as the worse firmware for the 4500.
-
Okay, so things have mostly been stable for the most part. In fact, I've had some really bad lockups as of late.
The scenario:
Test:
-DNS Relay Enabled
-Advanced DNS Servers Diabled
-Manual DNS Servers (OpenDNS: 208.67.222.222, and 208.67.220.220)
-GameFuel Rules: Automatic with a few rules in place
Result: WAN Lockup after 1 day and ~14 hours following a crash/reboot.
Test:
-DNS Relay Disabled
-Advanced DNS Servers Disabled
-Manual DNS Servers (OpenDNS: 208.67.222.222, and 208.67.220.220)
-GameFuel Rules: Automatic and no other rules
Result: No lockups, and uptime of 2 days, 19 hours.
Test:
-DNS Relay Enabled
-Advanced DNS Servers Disabled
-Manual DNS Servers (OpenDNS: 208.67.222.222, and 208.67.220.220)
-GameFuel Rules: Automatic and no additional rules
Result: WAN Lockup/Instant reboot/crash after ~17 hours.
I can also confirm that the password used under Safari still requires multiple inputs. Mozilla seems fine. Might be under certain conditions where there are harder characters, or ascii characters.
-
Woot i have 49 days 19:44:50 i am runing firmware 1.02. I know this is a section for 1.21 feedback but i just want to say haha to all of you who updated suckers. ( omg my router just got mest up no! ) Just kidding well yea guys. i have 2 routers 1 with 1.21 and another one with 1.02 i got from e bay my 1.21 can't do nothing but just look nice and my 1.02 is awsome!! but still d link suck as a company they don't care about us all they want is money money money!!!!
-
Lately I'm having visions of my a1 with 1.21 with a couple of j class hobby motors launching it up into the air to new heights.
-
I've been thinking of replacing mine soon.
Any high load conditions I place on the router locks it up. If I want to copy TV shows recorded by my DVR shares into my ps3 while also trying to web browse while downloading can cause the router to lock up. If I don't tax it, it runs fine for days, even weeks. If I do only 1 action, and don't touch it or even breathe, it works fine.
D-Link routers are still rated favorably for performance on smallnetbuilder's router charts, but then again their reviews show 1.02 listed as the firmware, and they're really dated.
The TEW-633GR appears to have the same processor as the DGL-4500, but uses a different switch, Vitesse instead of the RealTek inside the DGL.
Either that or the WNDR3700, which lists Atheros as the processor.
-
The more I play with this, the more I'm starting to think the current firmware can't handle multiple simultaneous connection initiations at the same time.
People more ****e[1] to seeing these errors are those with multiple devices on the same router that are capable of requesting several connections. Especially those who patch their tcpip.sys to allow for more half-open connections.
I've been able to halt the router via trying to preload multiple webpages via 7-8 tabs. If I have a SMB file copy going from 1 computer to another, then try to queue a movie into my ps3, I can cause a halt. Doing a simple file copy then requesting even a couple of web pages can cause a halt, especially a webpage with a lot of ads to different domains.
The reason why I can see stability for long periods of time is I'm a lone user on the network and can serialize most of my requests. Rarely do I need to force several actions through the router at once, but households with multiple people don't have the same luxury. I've been seeing more halts lately since I got a new ps3 slim and have been playing with the media features on it, hence pushing more bits through the router from various sources at the same time.
The main selling point for the DGL-4500 is supposedly its throughput. With the way it is acting, it's like having a 80mph speed limit, with a 2 lane highway with no breakdown lane. Very fast, but narrow pipe that works great... with little to no traffic.
[1] the word is p.r.o.n.e., which is why word filters with no context suck
-
The more I play with this, the more I'm starting to think the current firmware can't handle multiple simultaneous connection initiations at the same time.
People more ****e[1] to seeing these errors are those with multiple devices on the same router that are capable of requesting several connections. Especially those who patch their tcpip.sys to allow for more half-open connections.
I've been able to halt the router via trying to preload multiple webpages via 7-8 tabs. If I have a SMB file copy going from 1 computer to another, then try to queue a movie into my ps3, I can cause a halt. Doing a simple file copy then requesting even a couple of web pages can cause a halt, especially a webpage with a lot of ads to different domains.
The reason why I can see stability for long periods of time is I'm a lone user on the network and can serialize most of my requests. Rarely do I need to force several actions through the router at once, but households with multiple people don't have the same luxury. I've been seeing more halts lately since I got a new ps3 slim and have been playing with the media features on it, hence pushing more bits through the router from various sources at the same time.
The main selling point for the DGL-4500 is supposedly its throughput. With the way it is acting, it's like having a 80mph speed limit, with a 2 lane highway with no breakdown lane. Very fast, but narrow pipe that works great... with little to no traffic.
[1] the word is p.r.o.n.e., which is why word filters with no context suck
:D very true
-
Firmware 1.21 Build 03 Beta
The shareport firmware seems to work better. I can attach a USB drive at any time and I'm able to connect and disconnect without the issues I mentioned in another post.
It's still not perfect though. If I try to play a movie stored on a USB hard drive, it works for a while, then stops, continues, stops, disconnects, reconnects and I have to reload the video and find where I left off.
Network seems to still have slowdowns but I don't think I've had any crashes. That's not to say it won't just that I haven't had it happen yet. I still need to try downloading a torrent and watching a Netflix video on my XBOX 360 at the same time.
-
i am running 1.21NA, 2009/09/18. is that beta 3?
-
"i am running 1.21NA, 2009/09/18. is that beta 3?"
yes i believe it is. I upgraded to beta 3 and it says the same on my status view. on that note, i have had much better luck with this firmware than with any of the other 1.20+ firmwares this one i was up for 9 days + with no issues after 9 days i did start to experience slow downs however. and have rebooted it because of this. all and all this is much better than previous firmwares for me. before i was up for 3 - 4 days before i couldn't even load up a webpage never mind anything else.
-
I loaded this firmware and have all the same problems I did before. Here is a screenshot of me pinging the router (notice the ridiculous times) it said it was connected at 300mbit and then the router reboots...
(http://www.westcoastnetworking.com/dlink.png)
My MacBook Pro w/OSX 10.6.2 Network Utility reports my link speed: 270 Mbit/s
Im on Beta 3 FW 1.21NA, 2009/09/18
Connection Up Time : 9 Day 2 Hour 25 Min 39 Sec
Ping has started…
PING 192.168.1.1 (192.168.1.1): 56 data bytes
64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=1.226 ms
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=1.884 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=1.233 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=1.166 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=1.154 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=1.093 ms
64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=0.915 ms
64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=1.194 ms
64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=1.080 ms
64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=1.454 ms
~
--- 192.168.1.1 ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.915/1.240/1.884/0.251 ms
2nd Set:
64 bytes from 192.168.1.1: icmp_seq=547 ttl=64 time=2.148 ms
64 bytes from 192.168.1.1: icmp_seq=548 ttl=64 time=2.047 ms
64 bytes from 192.168.1.1: icmp_seq=549 ttl=64 time=1.755 ms
64 bytes from 192.168.1.1: icmp_seq=550 ttl=64 time=1.274 ms
64 bytes from 192.168.1.1: icmp_seq=551 ttl=64 time=1.799 ms
64 bytes from 192.168.1.1: icmp_seq=552 ttl=64 time=0.861 ms
64 bytes from 192.168.1.1: icmp_seq=553 ttl=64 time=1.758 ms
64 bytes from 192.168.1.1: icmp_seq=554 ttl=64 time=1.727 ms
64 bytes from 192.168.1.1: icmp_seq=555 ttl=64 time=1.090 ms
64 bytes from 192.168.1.1: icmp_seq=556 ttl=64 time=2.122 ms
64 bytes from 192.168.1.1: icmp_seq=557 ttl=64 time=0.868 ms
64 bytes from 192.168.1.1: icmp_seq=558 ttl=64 time=1.110 ms
64 bytes from 192.168.1.1: icmp_seq=559 ttl=64 time=1.088 ms
64 bytes from 192.168.1.1: icmp_seq=560 ttl=64 time=1.017 ms
64 bytes from 192.168.1.1: icmp_seq=561 ttl=64 time=1.177 ms
64 bytes from 192.168.1.1: icmp_seq=562 ttl=64 time=0.773 ms
64 bytes from 192.168.1.1: icmp_seq=563 ttl=64 time=1.012 ms
64 bytes from 192.168.1.1: icmp_seq=564 ttl=64 time=1.113 ms
64 bytes from 192.168.1.1: icmp_seq=565 ttl=64 time=1.006 ms
64 bytes from 192.168.1.1: icmp_seq=566 ttl=64 time=1.006 ms
64 bytes from 192.168.1.1: icmp_seq=567 ttl=64 time=1.010 ms
64 bytes from 192.168.1.1: icmp_seq=568 ttl=64 time=1.089 ms
64 bytes from 192.168.1.1: icmp_seq=569 ttl=64 time=1.146 ms
64 bytes from 192.168.1.1: icmp_seq=570 ttl=64 time=2.411 ms
64 bytes from 192.168.1.1: icmp_seq=571 ttl=64 time=1.158 ms
64 bytes from 192.168.1.1: icmp_seq=572 ttl=64 time=0.631 ms
64 bytes from 192.168.1.1: icmp_seq=573 ttl=64 time=1.114 ms
64 bytes from 192.168.1.1: icmp_seq=574 ttl=64 time=0.950 ms
64 bytes from 192.168.1.1: icmp_seq=575 ttl=64 time=0.992 ms
64 bytes from 192.168.1.1: icmp_seq=576 ttl=64 time=0.834 ms
64 bytes from 192.168.1.1: icmp_seq=577 ttl=64 time=0.683 ms
64 bytes from 192.168.1.1: icmp_seq=578 ttl=64 time=1.167 ms
64 bytes from 192.168.1.1: icmp_seq=579 ttl=64 time=1.144 ms
64 bytes from 192.168.1.1: icmp_seq=580 ttl=64 time=1.066 ms
64 bytes from 192.168.1.1: icmp_seq=581 ttl=64 time=1.090 ms
64 bytes from 192.168.1.1: icmp_seq=582 ttl=64 time=1.158 ms
64 bytes from 192.168.1.1: icmp_seq=583 ttl=64 time=1.019 ms
64 bytes from 192.168.1.1: icmp_seq=584 ttl=64 time=0.664 ms
64 bytes from 192.168.1.1: icmp_seq=585 ttl=64 time=1.359 ms
64 bytes from 192.168.1.1: icmp_seq=586 ttl=64 time=1.010 ms
64 bytes from 192.168.1.1: icmp_seq=587 ttl=64 time=1.719 ms
64 bytes from 192.168.1.1: icmp_seq=588 ttl=64 time=1.202 ms
64 bytes from 192.168.1.1: icmp_seq=589 ttl=64 time=1.343 ms
64 bytes from 192.168.1.1: icmp_seq=590 ttl=64 time=1.112 ms
64 bytes from 192.168.1.1: icmp_seq=591 ttl=64 time=1.866 ms
64 bytes from 192.168.1.1: icmp_seq=592 ttl=64 time=3.405 ms
64 bytes from 192.168.1.1: icmp_seq=593 ttl=64 time=1.115 ms
64 bytes from 192.168.1.1: icmp_seq=594 ttl=64 time=1.934 ms
64 bytes from 192.168.1.1: icmp_seq=595 ttl=64 time=1.087 ms
64 bytes from 192.168.1.1: icmp_seq=596 ttl=64 time=1.190 ms
64 bytes from 192.168.1.1: icmp_seq=597 ttl=64 time=0.897 ms
64 bytes from 192.168.1.1: icmp_seq=598 ttl=64 time=1.074 ms
64 bytes from 192.168.1.1: icmp_seq=599 ttl=64 time=1.117 ms
64 bytes from 192.168.1.1: icmp_seq=600 ttl=64 time=1.059 ms
64 bytes from 192.168.1.1: icmp_seq=601 ttl=64 time=0.950 ms
64 bytes from 192.168.1.1: icmp_seq=602 ttl=64 time=1.163 ms
64 bytes from 192.168.1.1: icmp_seq=603 ttl=64 time=1.250 ms
64 bytes from 192.168.1.1: icmp_seq=604 ttl=64 time=1.181 ms
64 bytes from 192.168.1.1: icmp_seq=605 ttl=64 time=1.262 ms
64 bytes from 192.168.1.1: icmp_seq=606 ttl=64 time=1.115 ms
64 bytes from 192.168.1.1: icmp_seq=607 ttl=64 time=4.103 ms
64 bytes from 192.168.1.1: icmp_seq=608 ttl=64 time=1.446 ms
64 bytes from 192.168.1.1: icmp_seq=609 ttl=64 time=1.017 ms
64 bytes from 192.168.1.1: icmp_seq=610 ttl=64 time=1.141 ms
64 bytes from 192.168.1.1: icmp_seq=611 ttl=64 time=0.892 ms
64 bytes from 192.168.1.1: icmp_seq=612 ttl=64 time=1.085 ms
64 bytes from 192.168.1.1: icmp_seq=613 ttl=64 time=1.569 ms
64 bytes from 192.168.1.1: icmp_seq=614 ttl=64 time=1.449 ms
64 bytes from 192.168.1.1: icmp_seq=615 ttl=64 time=1.319 ms
64 bytes from 192.168.1.1: icmp_seq=616 ttl=64 time=1.254 ms
64 bytes from 192.168.1.1: icmp_seq=617 ttl=64 time=1.274 ms
64 bytes from 192.168.1.1: icmp_seq=618 ttl=64 time=1.063 ms
64 bytes from 192.168.1.1: icmp_seq=619 ttl=64 time=1.397 ms
64 bytes from 192.168.1.1: icmp_seq=620 ttl=64 time=1.026 ms
TimeOuts:
Request timeout for icmp_seq 64
Request timeout for icmp_seq 546
-
Uptime 22+ Days on 1.21NA, 2009/09/18 =D
-
http://forums.dlink.com/index.php?topic=9327.0;topicseen
-
Try this out please.
http://forums.dlink.com/index.php?topic=9480.0
It should let you roll back the firmware you were using before. (assuming you weren't using a pre-1.2X code.)
-
if everything good with B08
whats the plan
youll attack the shareport
or shareport will be under beta siege :D
-
A1 HW
NUMBER OF WIRELESS CLIENTS: 1
SSID MAC Address IP Address Mode Rate (Mbps) Signal (%)
Airport One N 002xxxxxxxB 6.x.xx.x 802.11n (5GHz) 27 26
LAN STATISTICS
Sent :4726189
TX Packets Dropped :2
Collisions :0
Received :3698103
RX Packets Dropped :0
Errors :50
WAN STATISTICS
Sent :3688399
TX Packets Dropped :0
Collisions :0
Received :11313124
RX Packets Dropped :0
Errors :0
WIRELESS STATISTICS
Sent :113589
TX Packets Dropped :353
Received :68545
RX Packets Dropped :13677
Errors :2154
-
Using an A1 HW and FW b08, I did some file xfers from my Windows XP PC to my Mac Laptop over a Gb Lan network connected to the 4500 using the 300Mb wireless N only connection. I used a 50Mb, 417Mb, and a 1.1Gb files. The 50Mb completed in less than 15 seconds. The 417Mb file took about 3-4, minutes. ;D The 1.1Gb file was going to take about 10-15mins. I started the xfer with the 1.1Gb file and had to take a phone call. I came back after my phone call and found that the xfer had stopped. >:( A message on my Mac LT said that there was an interruption to the connection to my Windows PC. I looked at my wireless status and the wireless was disconnected from the 4500. I re-established the connection and re-tested the 1.1Gb file. As the file as xfering, I noticed the speed of the xfer was way down from 2.1Mb to 800kb and was going to take several hours to finish. I tried the 417Mb file and it too was going to take 20 minutes to finish. The 50Mb file was going to take over a minute to complete. The speed during xfer was also way down from the initial first test. I presume that if I restart my Mac LT and the Windows PC and try again that the speed should go back up. I also presume that 1.1Gb files should xfer without disconnection over wireless. ::)
Restarting my Mac LT, and reconnecting to the Windows XP PC, I restarted the file xfers again and the 50mb file completed with in 15 seconds, the 417mb completed in 3-4minutes and the 1.1Gb file completed in 7 minutes with out disconnection. The xfer speeds were hanging around 2.0Mb to 2.3Mb range during the xfers.
Thinking back while the 1.1Gb file was xfering, I was using a wireless Uniden house phone when the 1.1Gb was xfering. I bet that could have been the cause of the disconnection. The phones are 5.8Ghz phones.
-
Im curious as to why there are numberous entries about my Mac Laptop connecting to the 4500 when I'm just chatting online and browsing during this time frame? No wireless house phones are in use. I did notice after about and hour of using my LT, I got a disconnection from the 4500 and it finally reconnected in about a minute. Wireless still needs some work? Using B08 FW.
[INFO] Tue Dec 08 13:46:27 2009 Airport One N: Wireless system with MAC address 0021E9E1CDCB secured and linked
[INFO] Tue Dec 08 13:46:21 2009 Airport One N: Wireless system with MAC address 0021E9E1CDCB associated
[INFO] Tue Dec 08 13:46:21 2009 Above message repeated 1 times
[INFO] Tue Dec 08 13:34:38 2009 Administrator logout
[INFO] Tue Dec 08 13:26:56 2009 Airport One N: Wireless system with MAC address 0021E9E1CDCB secured and linked
[INFO] Tue Dec 08 13:26:56 2009 Airport One N: Wireless system with MAC address 0021E9E1CDCB associated
[INFO] Tue Dec 08 13:26:56 2009 Above message repeated 1 times
[INFO] Tue Dec 08 13:17:51 2009 Administrator logout
[INFO] Tue Dec 08 13:16:33 2009 Airport One N: Wireless system with MAC address 0021E9E1CDCB secured and linked
[INFO] Tue Dec 08 13:16:33 2009 Airport One N: Wireless system with MAC address 0021E9E1CDCB associated
[INFO] Tue Dec 08 13:16:33 2009 Above message repeated 1 times
[INFO] Tue Dec 08 13:06:39 2009 Airport One N: Wireless system with MAC address 0021E9E1CDCB secured and linked
[INFO] Tue Dec 08 13:06:39 2009 Airport One N: Wireless system with MAC address 0021E9E1CDCB associated
[INFO] Tue Dec 08 13:06:39 2009 Above message repeated 1 times
[INFO] Tue Dec 08 13:02:17 2009 Airport One N: Wireless system with MAC address 0021E9E1CDCB secured and linked
[INFO] Tue Dec 08 13:02:11 2009 Airport One N: Wireless system with MAC address 0021E9E1CDCB associated
[INFO] Tue Dec 08 13:02:11 2009 Above message repeated 1 times
[INFO] Tue Dec 08 13:01:25 2009 Airport One N: Wireless system with MAC address 0021E9E1CDCB secured and linked
[INFO] Tue Dec 08 13:01:12 2009 Airport One N: Wireless system with MAC address 0021E9E1CDCB associated
[INFO] Tue Dec 08 13:01:12 2009 Above message repeated 1 times
[INFO] Tue Dec 08 11:45:21 2009 Airport One N: Wireless system with MAC address 0021E9E1CDCB secured and linked
[INFO] Tue Dec 08 11:45:21 2009 Airport One N: Wireless system with MAC address 0021E9E1CDCB associated
[INFO] Tue Dec 08 11:45:21 2009 Above message repeated 1 times
-
Have been using the DGL4500 A1 - 121 Beta 03, has been working fine for me for at least 2 week, haven't had any restarts, i will move to the beta08 now that i know its out. its nice to see that dlink has taken notice to our pissing and moaning, Sincere thanks to the people working on this project. seems like its all up hill from here.
-
so far so good,
B03 Uptime has been 18 hours compared to 20min-2hrs with 1.21NA official.
sorry no status for B08
DGL4500 A1: Default settings with wlan name/wpa2 & computer time adjusted.
LAN1 = HTPC1 Win7 x64
LAN2 = HTPC2 Win7 x86
LAN3 = Test sys Hackintosh/XP/7
LAN4 = HDHomerun UPNP dual ATSC Tuner
WLAN1= Laptop G
WLAN2= Ipod Touch,HTPC1 Remote,ORB (atsc tv stream)
note: when i first purchased this A1 unit, fw1.02 did not work at all, just enough to get to the latest fw (1.1x).
I updated to 1.21NA for what ever reason late summer, all of a sudden late november/dec the dgl45 went loopy.
all is good with B03
ty
sk
-
I'm on 8 days, 6 hours uptime and no lockups. Much more stable than 1.21NA prod FW.
-
What FW are you using? Beta ?
-
Yes, beta. 1.21NA Beta 08.
-
Same here, looking good. Hope they get wireless more stable. ::)
-
Try reading the thread fully and you might get the point. We are trying to provide Dlink with some ping information regarding the Wireless connection to the 4500. Are you using the 4500 for wireless? I presume that if your not then it's not to worry yourself. Thanks but I'll pass the on stale cookies. I have fresh ones from everyones mom. Have a great week and Merry Christmas.
-
Thats ok, not worried, The post doesn't concern you. And I never said I was the know.
-
Try looking at my screen shot again before you open your mouth again. Like I said the router and firmware when this was taken wasn't available to the public. It was posted here because I didn't have write access for some reason when they gave me ftp access. You trolling the dlink forums doesn't mean you are in the "know".
I wish I still lived at home and my mom baked me cookies... ::)
Dude, slow your roll. Everyone here is trying to provide feedback so we can get this **** taken care of. Fuzzy has been helpful so what's all the hateration about? Keep it on topic before this thread gets locked up and people get banned. All the extra talk is not helping anyone.
-
Me slow my roll? You obviously have no clue on what is going on in the background to resolve the issues with the firmware. Not only myself but others volunteer their time to capture data with special dgl4500's. Any improvements in the latest firmware were not because FurryNuts has trolled the fourm. Please enlighten me on what FurryNuts has done. I wasn't aware he was able to capture/log and help the devs at dlink.
His post stating that his macbook worked fine has no bearing into troubleshooting any technical problems and is in no way helpful. Like I told him, know what you are talking about before you open your mouth.
Happy Holidays...
I'm not going to enlighten you on anything and I do know what I'm talking about. Seems like you have a personal issue just because Fuzzy posts in every thread. That's his business and not yours. Matter of fact, if Lycan thinks it's a problem, it's for him to say, not you.
I'm having the same problems with my router in which you don't know how to fix either. The intelligent folk here are trying to help these Dlink folks out with data and you're here trying to flame people.
It would be really nice of Dlink to just ban you from the site and let you deal with your issue on your own. Deal with your own emotional issues outside of this forum because we don't really care what you're going thru. We're here to help figure out this router issue.
Happy Holidays? You don't even seem like a happy person.
-
Well I'm going to leave all the information up to people at Dlink and WILL continue to post any information I feel may or may not help Dlink in there development of there products. IMO, your not qualified to judge who's postings may or may not be of any help. However feel free to do as you wish. I don't have to pay any attention and thus my discussion on regarding this with you is closed. Any information continuing will be directed to Dlink. Have a great day.
-
We're here trying to provide feedback to help Dlink fix the issue, period. If I knew what was going on and expertise in writing firmware, the issue would be fixed already.
-
Wow. OK. Thats enough of that.
Knock it off. All of you.
I'm locking this thread as it's reached a rediclous length and people are no longer working together.
There are other feedback links. Work there and keep it clean.