Retina MacBook Pro horrible wifi

[ZoomOut]

64 bytes from 192.168.0.1: icmp_seq=123 ttl=64 time=8.287 ms
64 bytes from 192.168.0.1: icmp_seq=124 ttl=64 time=28.217 ms
64 bytes from 192.168.0.1: icmp_seq=125 ttl=64 time=53.689 ms
64 bytes from 192.168.0.1: icmp_seq=126 ttl=64 time=76.456 ms
64 bytes from 192.168.0.1: icmp_seq=127 ttl=64 time=96.619 ms
64 bytes from 192.168.0.1: icmp_seq=128 ttl=64 time=122.051 ms
64 bytes from 192.168.0.1: icmp_seq=129 ttl=64 time=142.069 ms
64 bytes from 192.168.0.1: icmp_seq=130 ttl=64 time=164.876 ms
64 bytes from 192.168.0.1: icmp_seq=131 ttl=64 time=162.904 ms
64 bytes from 192.168.0.1: icmp_seq=132 ttl=64 time=1.339 ms
64 bytes from 192.168.0.1: icmp_seq=133 ttl=64 time=32.321 ms
64 bytes from 192.168.0.1: icmp_seq=134 ttl=64 time=54.775 ms
64 bytes from 192.168.0.1: icmp_seq=135 ttl=64 time=78.232 ms
64 bytes from 192.168.0.1: icmp_seq=136 ttl=64 time=97.659 ms
64 bytes from 192.168.0.1: icmp_seq=137 ttl=64 time=120.261 ms
64 bytes from 192.168.0.1: icmp_seq=138 ttl=64 time=143.124 ms
64 bytes from 192.168.0.1: icmp_seq=139 ttl=64 time=165.846 ms
Request timeout for icmp_seq 140
Request timeout for icmp_seq 141
Request timeout for icmp_seq 142
Request timeout for icmp_seq 143
Request timeout for icmp_seq 144
Request timeout for icmp_seq 145
Request timeout for icmp_seq 146
Request timeout for icmp_seq 147
64 bytes from 192.168.0.1: icmp_seq=148 ttl=64 time=175.958 ms
64 bytes from 192.168.0.1: icmp_seq=149 ttl=64 time=195.804 ms
64 bytes from 192.168.0.1: icmp_seq=150 ttl=64 time=20.186 ms
64 bytes from 192.168.0.1: icmp_seq=151 ttl=64 time=4.641 ms
64 bytes from 192.168.0.1: icmp_seq=152 ttl=64 time=46.177 ms
Request timeout for icmp_seq 153
64 bytes from 192.168.0.1: icmp_seq=154 ttl=64 time=103.745 ms
64 bytes from 192.168.0.1: icmp_seq=155 ttl=64 time=121.355 ms
64 bytes from 192.168.0.1: icmp_seq=156 ttl=64 time=1.519 ms
64 bytes from 192.168.0.1: icmp_seq=157 ttl=64 time=170.398 ms
64 bytes from 192.168.0.1: icmp_seq=158 ttl=64 time=189.804 ms
64 bytes from 192.168.0.1: icmp_seq=159 ttl=64 time=17.434 ms
64 bytes from 192.168.0.1: icmp_seq=160 ttl=64 time=30.761 ms
64 bytes from 192.168.0.1: icmp_seq=161 ttl=64 time=53.501 ms
64 bytes from 192.168.0.1: icmp_seq=162 ttl=64 time=78.974 ms
64 bytes from 192.168.0.1: icmp_seq=163 ttl=64 time=99.073 ms
64 bytes from 192.168.0.1: icmp_seq=164 ttl=64 time=121.927 ms
64 bytes from 192.168.0.1: icmp_seq=165 ttl=64 time=1.451 ms
64 bytes from 192.168.0.1: icmp_seq=166 ttl=64 time=167.390 ms
64 bytes from 192.168.0.1: icmp_seq=167 ttl=64 time=190.278 ms
64 bytes from 192.168.0.1: icmp_seq=168 ttl=64 time=11.387 ms
64 bytes from 192.168.0.1: icmp_seq=169 ttl=64 time=31.109 ms
64 bytes from 192.168.0.1: icmp_seq=170 ttl=64 time=53.895 ms
64 bytes from 192.168.0.1: icmp_seq=171 ttl=64 time=76.670 ms
64 bytes from 192.168.0.1: icmp_seq=172 ttl=64 time=99.416 ms
64 bytes from 192.168.0.1: icmp_seq=173 ttl=64 time=122.022 ms
64 bytes from 192.168.0.1: icmp_seq=174 ttl=64 time=145.926 ms

Just showing a sample ...

 

[kittencounter]

I also had a D-Link Router which worked nice with the 2012 Retina Macbook Pro until the Macbook suddenly started to refuse to recognize it after 6 months. So it's surely some stupid software stuffs. It just didn't see the SSID of the D-Link Router until it worked again for a certain time and there is nothing you can do about it. I tried to fix the problem but I just couldn't. After a while I bought the new time capsule since I needed time machine storage anyway. Beside the D-Link also could not handle 3 smartphones, 1 iPad and 3 computers connected to it all the time. It also tends to drop connection when I download things with 100 Mbits from the internet. Not 1 single problem since I use the TC then and the range + speed + connection reliability of the TC is amazing. It's sure upsetting ..but it's not worth time and stress sometimes.

 

[ZoomOut]

Went to a store to day ...

Standing side by side:

2013 rMBP 13 - 2012 mbp 15 - 2013 Air 13 - 2012 Air 11 inch

Started terminal on all of them and started pinging the same major site.

ping was all over - nice steady ping 10 ms - ping was all over - nice steady ping.


I have no doubt now - that the broadwell wifi chip in the 2013 haswell Apple computers are flawed - weather or not it can or will be fixed with a firmware upgrade to the wifi chip - remains to be seen.

The worst part is not the error is there - but Apple being silent about it ..