Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[arod]

Sorry guys I know I mentioned "we should be getting beta fw" yesterday.. Please be believe me, I've been buggin' to get this fw ASAP. So it looks like it's going to be one more day (Friday).

[Fearreality]

I don't know if it matters or not but I wanted to share a couple of anomolies. I found that if I used the yahoo D-Link v2.0 widget, the router seemed to become non responsive in the web pages and lock up within 12-15 hours (at one time it would cause a certain dir-655 firmware to reboot). If I didn't access the web pages and I didn't run the widget It would last a day or 2 before becoming very slow, at which point I could still access the web pages but a soft reset wouldn't help; a hard reset was needed. If I disabled everything (Upnp, SPI, wmm, multicast, logging, access control, web filter, mac filter, e-mail [which stopped working around 1.12], DHCP,only using 2.4ghz, Manually set connection speed & WAN port speed & type, etc etc ), then the router would last 3 to 4 days and need the hard reset. It does help to leave it uplugged for a while and it also helps to reboot every single item on your network; without doing this step sometimes the router would crash and reboot itself within 10 minutes after plugging it in.
  I've read the posts were people say greater than 10 devices is too much for it to handle and my question is why. It should not matter how many devices are connected, you will just run into a bandwidth problem as the processor and memory have to handle more traffic and prioritize. I had an old Netgear that lasted 6 years and could handle way more than this 4500 and the hardware in it was no doubt much more inferior. I've also read "just turn off this or that"; again, if it can't handle it then don't have it as an option. Also, I don't know a router today that doesn't do SPI. I also read the posts were everyone blamed it on torrent downloading. Has anyone tracked how many calls are made by MySpace? Myspace requires many more connections than any torrent I've seen (unless you have tweaked your client to use some huge number). Nobody here thinks the hardware is horrible but I think everyone here expects the firware on it to be able to handle very high bandwidth requirements since it IS a gaming router.
  Just my 2 cents. I would love to help test but after 9 months of testing I went out and bought a linksys and loaded DD-WRT on it (they have glitches every once in a while but they are always working on it and you can always go back).

[DLP]

Sorry guys I know I mentioned "we should be getting beta fw" yesterday.. Please be believe me, I've been buggin' to get this fw ASAP. So it looks like it's going to be one more day (Friday).

I appreciate the update!

[Reinvented]

The router is not meant to handle more than a certain number of devices, since it tends to put a strain on it.  Takes processing power, and memory.  Bandwidth will be okay, however wireless clients, not so much.  That's a LOT of strain on the wireless radio transmitter.  That's why!  So, if you want your device to fail due to that, go right on ahead.

[Fearreality]

Seriously. So a 60 dollar router can handle 20+ wireless and this one can't even handle 5 wireless and 5 wired (I use a dlink switch to handle the wired)?!?! The hardware is capable. The firmware is not. The only thing I have not taken out of the equation is the d-link switch.

[Routers]

Hopefully the new firmware comes out sooner than later. I've been monitoring my router's stats and it is currently at 6 Day 13 Hour 02 Min 22 Sec with 0 Lan errors on 1.20 firmware. I downloaded a 1GB speedtest from optimum online's ftp and it downloaded in 6min and 56seconds. I'm not sure what changes I made since it last locked up.

[Puffnstuff]

I don't want them to rush the next fw like they did with 1.20 or more problems will crop up.  I hope they do more research before they release it.  I'm considering going with netgear next time I need a router.

[Xender]

Sorry guys I know I mentioned "we should be getting beta fw" yesterday.. Please be believe me, I've been buggin' to get this fw ASAP. So it looks like it's going to be one more day (Friday).

Thanks for the update.  I'm sure you would have rather gave everyone some good news but as of yet you have none to give.  Its a tribute to your professionalism that you delivered the news knowing it would not be received well.  I for one really appreciate that.

We've waited this long, a couple of days more isn't going to matter much if it ensures that we may be getting closer to resolving the firmware issue.

I am currently at 1.15 and as reported in another thread am having dropped packets and some wireless problems.  To be more specific I only have two wireless devices on line.  One is a laptop that is using a DWA-652 Xtreme N notebook adapter and I have to say that I have never lost connection between this device and the router.  I use it to wirelessly stream or download movies to watch on a 32" tv.

The other device is a 'Chumby' that has a 802.11b connection.  This device does periodically lose it ip address but not its connection.

I also have a XBox 360 that is hard wired.  I have no issues with its connections or speed.  I download demos frequently and am amazed at the speed which is consistant.  I use Comcast cable as my ISP.

I like this router and have no intention of replacing it anytime soon.  D-link is fully aware of the issues we are all having because Ru-Fi-Oh had done a good job of relaying not only complaints but files submitted by users in this forum.  Many thanks to them as well.  I'm positive this will all lead to a successful firmware solution.  Trashing D-Link does not inspire them to provide a good solution.

Thanks again!
Xender

[Fearreality]

I agree that this time the issue was escalated in a timely manner and the communication channels stayed open. And please know this is not the first time I have posted. I tried to help before and communication stopped; even after I sent some WireShark logs. I even offered to create a server that they could just “unpack” and run for testing. In my posts here I am actually defending the router (not trashing). The hardware is good enough to run more than what people are saying. The key is having the right firmware to handle and shape the traffic.
  I understand they are working on fixing it and it does NOT go unappreciated, but you are talking about almost a year. It would be really cool to visit the forums all excited about a new feature they added to the firmware and then we could all talk about how great it works and how to fine tune it. This simply is not the case. Right now the only time my heart skips a beat is when the router passes the 10 hour mark. Don't get me wrong, they fix the issues but it seems that something else always breaks when they do. All I expect is to buy a router off the shelf, take it home, plug it in, and it work the way it was advertised (ie reliable uptime).
  I don’t run much but what I do run is important. I would like to have a stable internet connection. I have had Brighthouse out 3 times and they couldn’t find anything wrong. They replaced my modem twice (just in case). So here I am taking days off work. And if I am working from home I hope that the router stays up long enough for me to do that work (Rarely does). Speaking of; while typing this and at 4 hours of uptime, I just got disconnected and had to reboot the router. Please take this for what it is, I love the router but the firmware is lacking. I only bought the Linksys as a temporary fix and I am leaving the D-link attached so I can test when the new firmware is released.

[anon]

f/w is killing the h/w potential.

[defaultPlayer]

Sorry guys I know I mentioned "we should be getting beta fw" yesterday.. Please be believe me, I've been buggin' to get this fw ASAP. So it looks like it's going to be one more day (Friday).

I look forward to testing out the beta firmware.  May I ask which issues were addressed in the beta fw? Is it only the router slowdown issue?  Has the UPnP failing issue also been looked into yet?

I'd also like to mention that I agree with every comment that I've read posted by Fearreality and we appear to share many of the same thoughts about this router.

[Routers]

well my router finally died today after almost 7 days. The admin page was not accessible. I had to reboot. =(

[d01100100]

Trashing D-Link does not inspire them to provide a good solution.

This is the new age of the internet.  It's far easier to complain than to do something about it.  At least complaining means the customer cares.

I had ordered another router with another company right before 1.20 came out.  I ended up loading 1.20 as 1 last attempt, and if it didn't work I'd get by, switch to another brand and move on with my time.  People expect a lot for their cash nowadays.  Welcome to the instant on, MTV, I want it now generation.  They want it fast and accurate, without conceding both ideals may directly impact each other.  Loading a beta firmware? Caveat emptor.

Complaining in this forum isn't necessarily adding any pressure on the firmware developers.  It's putting pressure on the forum admins who need to go to the developers while getting crapped on near daily.

I'd say the issue here is that QA is lacking for this product, but only so far as the expectations that customers expect from the hardware was higher than they imagined.  A device that acts as firewall, QoS, wireless, wired, netfilter, port scanning all-in-one, and you still expect fries with that.

Even though my 1.20 router has been stable, I still have complaints with it.  NTP sync never works, the router can't understand using DNS from within its own private allocated networks, and I don't feel like opening a hole in the firewall to allow the router to query its private LAN.

I've seen 1 error show up so far in almost a week of operation, and as you can tell from my stats, most of my traffic is from LAN to WAN, with a small percentage being LAN to LAN.

Connection Up Time :  6 Day 2 Hour 09 Min 19 Sec  

LAN Statistics
Sent :73682854
TX Packets Dropped :0
Collisions :0
   
Received :77339814
RX Packets Dropped :0
Errors :1

WAN Statistics
Sent :76452970
TX Packets Dropped :0
Collisions :0
   
Received :73647740
RX Packets Dropped :0
Errors :0

[iconeater]

 People expect a lot for their cash nowadays.  Welcome to the instant on, MTV, I want it now generation.  They want it fast and accurate, without conceding both ideals may directly impact each other.  Loading a beta firmware? Caveat emptor.

Complaining in this forum isn't necessarily adding any pressure on the firmware developers.  It's putting pressure on the forum admins who need to go to the developers while getting ****ped on near daily.

Let just put this in context, We the consumers who purchased this router based either on the previous solid performance from other DGL line products or the advertising and hype from dlink. See Dlinktv.

And for a YEAR now dlink has failed to provide as stable working software package for this router.

It has nothing to do with instant whatever MTV generation BS.

I and others like me are not demanding anything out of bounds we just want what was promised to us based on the product specs, ads, and other documents.

We just want what we paid for. A stable product that works as promised. THAT IS IT. A year and 4 firmware releases later is far too long to still not have this router working as promised. IMHO Dlink's window of consumer patience has run out.

Now, that is not to say we are not willing to wait a little longer so that yet ANOTHER defective firmware is not released.

I am being as vocal as I can about this issue until it is resolved, because as a consumer I would have appreciated this information prior to purchase. And now that the price point for this router has gone down as low as $130 down from it's high of $250 more are likely to be sold.

The forum Mods are definitely appreciate, I just hope they are not the only one from Dlink to see this. 

[anon]

 Welcome to the instant on, MTV, I want it now generation.  They want it fast and accurate, without conceding both ideals may directly impact each other.

I still can’t believe to this day people make comments like that and have little to no evidence to prove it. I’m sure if you looked through the dgl-4500 board you’ll have seen more patients in wanting to get a fix/problem solved than the so called “complaining” about it. I can go on but this is neither the time nor forum for that.
If this goes anything like the last beta f/w timeline for the dgl-4500, we’ll have to wait until the current beta for the dir-655 is finalized.