Hi,

Planning to get DIr-635. Anyone there that is using thing brand? Any comment? Need to know the following thing

a) reliability (hang, reboot, or etc)
b) Wireless peformance (signal and speed transfer)
c) Temperature (hot or not?)
d) LifeSpan

How long have u turn on the thing without restarting it? Do you turn on BT application 24H?

Just got a DIR-635. I am using this for ew reason

a) I am using G technology over N devices. This give me more than enough performance.
b) Price are cheapest among all
c) No bad comment so far from google or anyone i know.

So far i put this router to test. My test including

a) transfer from wireless to Lan, can get constant speed about 1.47mbyte/sec. this is worst a bit than my previous linksyswrt54g, which can go up to 1.57. But dlink has constant speed.

b) BT - no limitation on the user. See how long the router can stand without hang. ---undergoing

c) Temperature (after 3 hours turn on with full load), seem still okay. meaning room temperature. Coolest i know compare modem, AP and other brand devices i ever tested.

Still testing......................................................................

This post has been edited by bryansu: Jun 17 2007, 06:24 PM

I tested on the QOS today. PC A is connected to the router via lan and running BT connectced to 100 seed, and having speed of DL~500mbps and UL~160mbps. PC B is connected via wirless and did few test:

a) ping to yahoo.com and google.com
b) clear cache and then surf download.com, msn.com and snapfiles.com
c) download some file from the internet.

QOS is set PC B have highest priority and PC A has lowest priority. After testing QOS does prove to work. But bare in mind few thing about QOS which not many ppl understand:

a) QOS cannot guarantee packet will not lose in the router or internet. It will try to minimise loses but not 100%. Let say your uplink is 100mbps, PCA and PCB is connected to the router. PCB have more priority than PCA. When PCA is sending data at 80mbps constantly, suddenly PCB want to send 50mbps, don't expect all 50mpbs will go out and not lose. This is bull shit. What the router does is slowly cut down PCA speed by doing "windowing" on the TCP , and then try to let PCB go out first. This is what you call QOS.

b) QOS on DLINK DIR-635 is controlling the uplink only not the downlink.

c) QOS only start work and see the effect when there is traffic congestion in the network. What is traffic congestion? It means, if you have 100mbps pipe, and at the same time 2 PC want to pump 100mbps out...then there will be congestion of 200mbps. So router will look at the packet priority and let the highest priority one go out first. In this case 100mpbs of PC B will go out first, and another 100mbps will store in the router memory. When PC B 100mbps data is going out, then PC A 100mbps will go out later. Thaat is why router need memory, and if it have large memory then your packet will have more guarantee on not getting lose.


TESTING on DIR-635
==============
Testing as mention above is perform when QOS is turn on and turn off.

TEST A - QOS Turn off
---------------------------
C:\Documents and Settings\AdminUser>ping yahoo.com -n 30

Pinging yahoo.com [216.109.112.135] with 32 bytes of data:

Reply from 216.109.112.135: bytes=32 time=379ms TTL=46
Reply from 216.109.112.135: bytes=32 time=475ms TTL=46
Request timed out.
Reply from 216.109.112.135: bytes=32 time=300ms TTL=47
Reply from 216.109.112.135: bytes=32 time=289ms TTL=46
Reply from 216.109.112.135: bytes=32 time=290ms TTL=46
Request timed out.
Reply from 216.109.112.135: bytes=32 time=428ms TTL=47
Reply from 216.109.112.135: bytes=32 time=290ms TTL=46
Reply from 216.109.112.135: bytes=32 time=606ms TTL=46
Reply from 216.109.112.135: bytes=32 time=507ms TTL=46
Reply from 216.109.112.135: bytes=32 time=580ms TTL=46
Reply from 216.109.112.135: bytes=32 time=559ms TTL=46
Reply from 216.109.112.135: bytes=32 time=403ms TTL=46
Reply from 216.109.112.135: bytes=32 time=298ms TTL=47
Reply from 216.109.112.135: bytes=32 time=504ms TTL=47
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 216.109.112.135: bytes=32 time=460ms TTL=46
Reply from 216.109.112.135: bytes=32 time=432ms TTL=46
Reply from 216.109.112.135: bytes=32 time=364ms TTL=46
Reply from 216.109.112.135: bytes=32 time=289ms TTL=46
Reply from 216.109.112.135: bytes=32 time=496ms TTL=46
Request timed out.
Reply from 216.109.112.135: bytes=32 time=296ms TTL=46
Request timed out.
Reply from 216.109.112.135: bytes=32 time=472ms TTL=47
Reply from 216.109.112.135: bytes=32 time=483ms TTL=47

Ping statistics for 216.109.112.135:
Packets: Sent = 30, Received = 22, Lost = 8 (26% loss),
Approximate round trip times in milli-seconds:
Minimum = 289ms, Maximum = 606ms, Average = 418ms

C:\Documents and Settings\AdminUser>ping google.com -n 30

Pinging google.com [64.233.167.99] with 32 bytes of data:

Reply from 64.233.167.99: bytes=32 time=360ms TTL=236
Reply from 64.233.167.99: bytes=32 time=293ms TTL=236
Reply from 64.233.167.99: bytes=32 time=350ms TTL=236
Reply from 64.233.167.99: bytes=32 time=285ms TTL=236
Reply from 64.233.167.99: bytes=32 time=288ms TTL=236
Reply from 64.233.167.99: bytes=32 time=285ms TTL=236
Request timed out.
Reply from 64.233.167.99: bytes=32 time=303ms TTL=236
Reply from 64.233.167.99: bytes=32 time=554ms TTL=236
Reply from 64.233.167.99: bytes=32 time=384ms TTL=236
Reply from 64.233.167.99: bytes=32 time=362ms TTL=236
Reply from 64.233.167.99: bytes=32 time=286ms TTL=236
Reply from 64.233.167.99: bytes=32 time=558ms TTL=236
Reply from 64.233.167.99: bytes=32 time=582ms TTL=236
Request timed out.
Reply from 64.233.167.99: bytes=32 time=445ms TTL=236
Reply from 64.233.167.99: bytes=32 time=289ms TTL=236
Reply from 64.233.167.99: bytes=32 time=394ms TTL=236
Reply from 64.233.167.99: bytes=32 time=302ms TTL=236
Request timed out.
Reply from 64.233.167.99: bytes=32 time=565ms TTL=236
Reply from 64.233.167.99: bytes=32 time=494ms TTL=236
Reply from 64.233.167.99: bytes=32 time=571ms TTL=236
Reply from 64.233.167.99: bytes=32 time=413ms TTL=236
Reply from 64.233.167.99: bytes=32 time=431ms TTL=236
Reply from 64.233.167.99: bytes=32 time=366ms TTL=236
Reply from 64.233.167.99: bytes=32 time=288ms TTL=236
Reply from 64.233.167.99: bytes=32 time=643ms TTL=236
Reply from 64.233.167.99: bytes=32 time=422ms TTL=236
Reply from 64.233.167.99: bytes=32 time=618ms TTL=236

Ping statistics for 64.233.167.99:
Packets: Sent = 30, Received = 27, Lost = 3 (10% loss),
Approximate round trip times in milli-seconds:
Minimum = 285ms, Maximum = 643ms, Average = 412ms


Test B - QOS turn on
-------------------------
C:\Documents and Settings\AdminUser>ping yahoo.com -n 30
Pinging yahoo.com [66.94.234.13] with 32 bytes of data:
Request timed out.
Reply from 66.94.234.13: bytes=32 time=243ms TTL=49
Request timed out.
Request timed out.
Reply from 66.94.234.13: bytes=32 time=241ms TTL=48
Reply from 66.94.234.13: bytes=32 time=266ms TTL=49
Reply from 66.94.234.13: bytes=32 time=266ms TTL=48
Request timed out.
Reply from 66.94.234.13: bytes=32 time=275ms TTL=48
Request timed out.
Reply from 66.94.234.13: bytes=32 time=243ms TTL=49
Reply from 66.94.234.13: bytes=32 time=248ms TTL=48
Reply from 66.94.234.13: bytes=32 time=240ms TTL=49
Request timed out.
Reply from 66.94.234.13: bytes=32 time=239ms TTL=49
Request timed out.
Reply from 66.94.234.13: bytes=32 time=238ms TTL=49
Reply from 66.94.234.13: bytes=32 time=233ms TTL=49
Request timed out.
Reply from 66.94.234.13: bytes=32 time=246ms TTL=49
Reply from 66.94.234.13: bytes=32 time=238ms TTL=48
Reply from 66.94.234.13: bytes=32 time=235ms TTL=49
Reply from 66.94.234.13: bytes=32 time=237ms TTL=48
Reply from 66.94.234.13: bytes=32 time=238ms TTL=49
Request timed out.
Reply from 66.94.234.13: bytes=32 time=236ms TTL=48
Request timed out.
Reply from 66.94.234.13: bytes=32 time=271ms TTL=48
Reply from 66.94.234.13: bytes=32 time=264ms TTL=49
Reply from 66.94.234.13: bytes=32 time=239ms TTL=48

Ping statistics for 66.94.234.13:
Packets: Sent = 30, Received = 20, Lost = 10 (33% loss),
Approximate round trip times in milli-seconds:
Minimum = 233ms, Maximum = 275ms, Average = 246ms


Pinging google.com [64.233.167.99] with 32 bytes of data:

Reply from 64.233.167.99: bytes=32 time=312ms TTL=236
Reply from 64.233.167.99: bytes=32 time=321ms TTL=236
Reply from 64.233.167.99: bytes=32 time=288ms TTL=236
Reply from 64.233.167.99: bytes=32 time=292ms TTL=236
Reply from 64.233.167.99: bytes=32 time=319ms TTL=236
Reply from 64.233.167.99: bytes=32 time=319ms TTL=236
Request timed out.
Reply from 64.233.167.99: bytes=32 time=289ms TTL=236
Reply from 64.233.167.99: bytes=32 time=310ms TTL=236
Reply from 64.233.167.99: bytes=32 time=299ms TTL=236
Reply from 64.233.167.99: bytes=32 time=292ms TTL=236
Reply from 64.233.167.99: bytes=32 time=303ms TTL=236
Reply from 64.233.167.99: bytes=32 time=327ms TTL=236
Reply from 64.233.167.99: bytes=32 time=321ms TTL=236
Reply from 64.233.167.99: bytes=32 time=288ms TTL=236
Request timed out.
Reply from 64.233.167.99: bytes=32 time=291ms TTL=236
Reply from 64.233.167.99: bytes=32 time=296ms TTL=236
Reply from 64.233.167.99: bytes=32 time=313ms TTL=236
Reply from 64.233.167.99: bytes=32 time=304ms TTL=236
Reply from 64.233.167.99: bytes=32 time=291ms TTL=236
Reply from 64.233.167.99: bytes=32 time=316ms TTL=236
Reply from 64.233.167.99: bytes=32 time=308ms TTL=236
Reply from 64.233.167.99: bytes=32 time=318ms TTL=236
Reply from 64.233.167.99: bytes=32 time=300ms TTL=236
Reply from 64.233.167.99: bytes=32 time=304ms TTL=236
Reply from 64.233.167.99: bytes=32 time=321ms TTL=236
Reply from 64.233.167.99: bytes=32 time=289ms TTL=236
Reply from 64.233.167.99: bytes=32 time=290ms TTL=236
Reply from 64.233.167.99: bytes=32 time=290ms TTL=236

Ping statistics for 64.233.167.99:
Packets: Sent = 30, Received = 28, Lost = 2 (6% loss),
Approximate round trip times in milli-seconds:
Minimum = 288ms, Maximum = 327ms, Average = 303ms




Explanatioin on the test.
================

As i have mention earlier, QOS cannot guarantee loses so what show we look at. We show look at whether the packet from PC will go out first or not when QOS is turn on. Hence we need to look at the response time. Fast response time mean the packet is going out faster, therefore return also faster. If the packet is in queue, the of course the packet will not go out that early. To summary out, pls look below.


QOS turn off
--------------
Ping statistics for 64.233.167.99: (google.com)
Packets: Sent = 30, Received = 27, Lost = 3 (10% loss),
Approximate round trip times in milli-seconds:
Minimum = 285ms, Maximum = 643ms, Average = 412ms


QOS turn on
--------------
Ping statistics for 64.233.167.99:
Packets: Sent = 30, Received = 28, Lost = 2 (6% loss),
Approximate round trip times in milli-seconds:
Minimum = 288ms, Maximum = 327ms, Average = 303ms


As you can see, the ping response time is higher on the QOS turn on than the QOS turn off. 303ms is better than 412. This clear prove QOS is working. Is not easy to have a router with the price of RM385 and work perfectly without problem. Normall router than support QOS will cause you a lot.


In term of surfing msn.com, snapfiles.com and download.com, normal user cannot differentiate the speed. Only with the ping test can u see the test result.

Objective of testing
=============
why test this thing? Very simple just want to prove Dlink DIR-635 is not bull shitting us. And is worth the money to buy it. If other ppl got other brand , kind pls post the result and let everyone know. I am not promoting DIR-635, just that i wan everyone to see thing in different point of view and be a smart consumer. If everyone know every product well enough, then those stupid company with stupid product will not survive. Hence every company will produce good stuff. lsatly consume will benefit.

I already bought few brand last time...and waste money to find so many bug and problem.....


This post has been edited by bryansu: Jun 19 2007, 05:10 AM

Never tested on the range, but heard was good. the only thing i noticed is when i am using linksys or smc wireless, the signal strength was -55db, but using this, the signal was -40db. which prove it is strong.

But honestly, why dont u buy an PURE ACCESS POINT, and put on two floor. This is a gurantee of bandiwdth and also strength.AP also very cheap nowadays.

Don't forget no matter how strong you access point, the total bandwidth is only

13.6mbps (actual total transfer).

This post has been edited by bryansu: Jun 22 2007, 10:24 PM