Print

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

[LookIntoMyEyees]

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!!!!

[Puffnstuff]

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.

[d01100100]

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.

[d01100100]

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

[anon]

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

  very true

[jdiffend]

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.

[stephenaron]

i am running 1.21NA,  2009/09/18. is that beta 3?

[Coop]

"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.

[FurryNutz]

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...

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

[kxz]

Uptime 22+ Days on 1.21NA,  2009/09/18 =D

[Lycan]

http://forums.dlink.com/index.php?topic=9327.0;topicseen

[Lycan]

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.)

[johnnybegood]

if everything good with B08
whats the plan
youll attack the shareport
or shareport will be under beta siege

[FurryNutz]

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

[FurryNutz]

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.  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.