how to debug epicly slow wifi but fast lan
How can I debug a problem where my wifi is REALLY slow(it takes a minute for this page to load...even my router's admin page - 192.168.0.1)?
I've tried upgrading my hardware firmware(using a DIR-600 Dlink router). And it still sometimes happens. LAN connection is decent, but using WIFI is really deadly. And I don't think it is signal because I have 100% as I am beside my router.
What gives? What's wrong with my wifi? Is this hardware? software? where do i satrt debugging(short of using a new router)
here are some benchmarks i made using a simple ping to google.com:
WIRELESS:
ping google.com
PING google.com (******): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
64 bytes from ******: icmp_seq=0 ttl=54 time=2151.072 ms
64 bytes from ******: icmp_seq=1 ttl=54 time=1985.512 ms
64 bytes from ******: icmp_seq=2 ttl=54 time=1260.442 ms
64 bytes from ******: icmp_seq=3 ttl=54 time=689.094 ms
64 bytes from ******: icmp_seq=4 ttl=54 time=282.469 ms
64 bytes from ******: icmp_seq=5 ttl=54 time=196.629 ms
64 bytes from ******: icmp_seq=6 ttl=54 time=124.606 ms
--- google.com ping statistics ---
7 packets transmitted, 7 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 124.606/955.689/2151.072/790.436 ms
LAN
ping google.com
PING google.com (******): 56 data bytes
64 bytes from ******: icmp_seq=0 ttl=54 time=52.667 ms
64 bytes from ******: icmp_seq=1 ttl=54 time=55.384 ms
64 bytes from ******: icmp_seq=2 ttl=54 time=54.553 ms
64 bytes from ******: icmp_seq=3 ttl=54 time=54.734 ms
64 bytes from ******: icmp_seq=4 ttl=54 time=52.043 ms
64 bytes from ******: icmp_seq=5 ttl=54 time=52.813 ms
64 bytes from ******: icmp_seq=6 ttl=54 time=54.003 ms
--- google.com ping statistics ---
7 packets transmitted, 7 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 52.043/53.742/55.384/1.153 ms
You can see the HUGE difference
Solution 1:
First thing is to try different settings on your wireless.
Try a different channel - you may be getting interference from another source nearby.
Try different encryption settings.
Try moving your router to a different location.