Internet seemed very very sluggish when working at home via a wireless access point...
Tested with ping and found the reason:
PING rottentomatoes.com (209.237.233.38): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
64 bytes from 209.237.233.38: icmp_seq=2 ttl=54 time=267.700 ms
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
64 bytes from 209.237.233.38: icmp_seq=5 ttl=54 time=256.533 ms
Request timeout for icmp_seq 6
64 bytes from 209.237.233.38: icmp_seq=7 ttl=54 time=258.127 ms
Request timeout for icmp_seq 8
Request timeout for icmp_seq 9
Request timeout for icmp_seq 10
Request timeout for icmp_seq 11
Request timeout for icmp_seq 12
Yikes... what's going on... almost every packet being dropped causing essentially unusable websites.
Test 1: Unplug wireless access point and plug Ethernet cable directly into MBP
PING rottentomatoes.com (209.237.233.38): 56 data bytes
64 bytes from 209.237.233.38: icmp_seq=0 ttl=54 time=257.605 ms
64 bytes from 209.237.233.38: icmp_seq=1 ttl=54 time=255.540 ms
64 bytes from 209.237.233.38: icmp_seq=2 ttl=54 time=256.139 ms
64 bytes from 209.237.233.38: icmp_seq=3 ttl=54 time=255.279 ms
64 bytes from 209.237.233.38: icmp_seq=4 ttl=54 time=255.586 ms
64 bytes from 209.237.233.38: icmp_seq=5 ttl=54 time=255.591 ms
64 bytes from 209.237.233.38: icmp_seq=6 ttl=54 time=256.747 ms
64 bytes from 209.237.233.38: icmp_seq=7 ttl=54 time=255.630 ms
64 bytes from 209.237.233.38: icmp_seq=8 ttl=54 time=256.657 ms
64 bytes from 209.237.233.38: icmp_seq=9 ttl=54 time=255.682 ms
64 bytes from 209.237.233.38: icmp_seq=10 ttl=54 time=255.122 ms
64 bytes from 209.237.233.38: icmp_seq=11 ttl=54 time=255.626 ms
Conclusion 1: It's not the modem or ISP, but the WAP
Test 2: Try wireless with my trusty Linux netbook...
No problems with dropped packets.
Conclusion 2: It is the MBP + wireless that is the problem
Now what can I do about it?
I have googled around and found some older threads about problems with wireless with OS 10.6.3 and various ad hoc solutions, but nothing really current.
Any suggestions? Either for fixes or additional diagnostics?
System: 15" i5 MBP running 10.6.5
Tested with ping and found the reason:
PING rottentomatoes.com (209.237.233.38): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
64 bytes from 209.237.233.38: icmp_seq=2 ttl=54 time=267.700 ms
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
64 bytes from 209.237.233.38: icmp_seq=5 ttl=54 time=256.533 ms
Request timeout for icmp_seq 6
64 bytes from 209.237.233.38: icmp_seq=7 ttl=54 time=258.127 ms
Request timeout for icmp_seq 8
Request timeout for icmp_seq 9
Request timeout for icmp_seq 10
Request timeout for icmp_seq 11
Request timeout for icmp_seq 12
Yikes... what's going on... almost every packet being dropped causing essentially unusable websites.
Test 1: Unplug wireless access point and plug Ethernet cable directly into MBP
PING rottentomatoes.com (209.237.233.38): 56 data bytes
64 bytes from 209.237.233.38: icmp_seq=0 ttl=54 time=257.605 ms
64 bytes from 209.237.233.38: icmp_seq=1 ttl=54 time=255.540 ms
64 bytes from 209.237.233.38: icmp_seq=2 ttl=54 time=256.139 ms
64 bytes from 209.237.233.38: icmp_seq=3 ttl=54 time=255.279 ms
64 bytes from 209.237.233.38: icmp_seq=4 ttl=54 time=255.586 ms
64 bytes from 209.237.233.38: icmp_seq=5 ttl=54 time=255.591 ms
64 bytes from 209.237.233.38: icmp_seq=6 ttl=54 time=256.747 ms
64 bytes from 209.237.233.38: icmp_seq=7 ttl=54 time=255.630 ms
64 bytes from 209.237.233.38: icmp_seq=8 ttl=54 time=256.657 ms
64 bytes from 209.237.233.38: icmp_seq=9 ttl=54 time=255.682 ms
64 bytes from 209.237.233.38: icmp_seq=10 ttl=54 time=255.122 ms
64 bytes from 209.237.233.38: icmp_seq=11 ttl=54 time=255.626 ms
Conclusion 1: It's not the modem or ISP, but the WAP
Test 2: Try wireless with my trusty Linux netbook...
No problems with dropped packets.
Conclusion 2: It is the MBP + wireless that is the problem
Now what can I do about it?
I have googled around and found some older threads about problems with wireless with OS 10.6.3 and various ad hoc solutions, but nothing really current.
Any suggestions? Either for fixes or additional diagnostics?
System: 15" i5 MBP running 10.6.5