Not sure if 1.0.2 is the latest vesion or not but I do see they released a firmware here showing fix some bug with Mac os maybe you can try: http://www.tp-link.com/en/download/RE650.html#Firmware BTW, if you still have the problem after upgrade, I think you need to send your issue to support@tp-link.com.

uutommi wrote

Not sure if 1.0.2 is the latest vesion or not but I do see they released a firmware here showing fix some bug with Mac os maybe you can try: http://www.tp-link.com/en/download/RE650.html#Firmware BTW, if you still have the problem after upgrade, I think you need to send your issue to [EMAIL="support@tp-link.com"]support@tp-link.com[/EMAIL].

Thanks. Unfortunately 1.0.2 is already the latest version, which supposedly includes the Mac fixes. However, it does not fix this particular problem.

I guess you need to send the puzzle to the support guy and let them figure out for you.

Hi xnpu,

I am currently testing the RE650 (received today) and have updated the firmware to 1.0.5 Build 20171218 Rel. 65960.

I too am using it as an Access Point hardwired to my router and have just carried out a ping test from my Macbook Pro to the RE650 and don't seem to be getting any packet drops.

Can you please check the pings below that I have copied and pasted from the Terminal app on the Macbook Pro which I used to run the ping.

Is this how you were pinging the RE650 or were you doing it using some other command line tool?


PING 192.168.0.2 (192.168.0.2): 56 data bytes
64 bytes from 192.168.0.2: icmp_seq=0 ttl=64 time=3.673 ms
64 bytes from 192.168.0.2: icmp_seq=1 ttl=64 time=3.424 ms
64 bytes from 192.168.0.2: icmp_seq=2 ttl=64 time=3.514 ms
64 bytes from 192.168.0.2: icmp_seq=3 ttl=64 time=3.553 ms
64 bytes from 192.168.0.2: icmp_seq=4 ttl=64 time=3.530 ms
64 bytes from 192.168.0.2: icmp_seq=5 ttl=64 time=3.462 ms
64 bytes from 192.168.0.2: icmp_seq=6 ttl=64 time=37.663 ms
64 bytes from 192.168.0.2: icmp_seq=7 ttl=64 time=22.769 ms
64 bytes from 192.168.0.2: icmp_seq=8 ttl=64 time=8.367 ms
64 bytes from 192.168.0.2: icmp_seq=9 ttl=64 time=3.381 ms
64 bytes from 192.168.0.2: icmp_seq=10 ttl=64 time=3.711 ms
64 bytes from 192.168.0.2: icmp_seq=11 ttl=64 time=3.452 ms
64 bytes from 192.168.0.2: icmp_seq=12 ttl=64 time=3.502 ms
64 bytes from 192.168.0.2: icmp_seq=13 ttl=64 time=3.412 ms
64 bytes from 192.168.0.2: icmp_seq=14 ttl=64 time=3.491 ms
64 bytes from 192.168.0.2: icmp_seq=15 ttl=64 time=59.262 ms
64 bytes from 192.168.0.2: icmp_seq=16 ttl=64 time=42.363 ms
64 bytes from 192.168.0.2: icmp_seq=17 ttl=64 time=30.910 ms
64 bytes from 192.168.0.2: icmp_seq=18 ttl=64 time=3.498 ms
64 bytes from 192.168.0.2: icmp_seq=19 ttl=64 time=3.513 ms
64 bytes from 192.168.0.2: icmp_seq=20 ttl=64 time=3.507 ms
64 bytes from 192.168.0.2: icmp_seq=21 ttl=64 time=0.839 ms
64 bytes from 192.168.0.2: icmp_seq=22 ttl=64 time=3.542 ms
64 bytes from 192.168.0.2: icmp_seq=23 ttl=64 time=3.431 ms
64 bytes from 192.168.0.2: icmp_seq=24 ttl=64 time=19.459 ms
64 bytes from 192.168.0.2: icmp_seq=25 ttl=64 time=8.421 ms
64 bytes from 192.168.0.2: icmp_seq=26 ttl=64 time=0.993 ms
64 bytes from 192.168.0.2: icmp_seq=27 ttl=64 time=3.467 ms
64 bytes from 192.168.0.2: icmp_seq=28 ttl=64 time=3.765 ms
64 bytes from 192.168.0.2: icmp_seq=29 ttl=64 time=3.474 ms
64 bytes from 192.168.0.2: icmp_seq=30 ttl=64 time=3.689 ms
64 bytes from 192.168.0.2: icmp_seq=31 ttl=64 time=3.529 ms
64 bytes from 192.168.0.2: icmp_seq=32 ttl=64 time=3.562 ms
64 bytes from 192.168.0.2: icmp_seq=33 ttl=64 time=15.335 ms
64 bytes from 192.168.0.2: icmp_seq=34 ttl=64 time=8.290 ms
64 bytes from 192.168.0.2: icmp_seq=35 ttl=64 time=0.896 ms
64 bytes from 192.168.0.2: icmp_seq=36 ttl=64 time=3.991 ms
64 bytes from 192.168.0.2: icmp_seq=37 ttl=64 time=3.702 ms
64 bytes from 192.168.0.2: icmp_seq=38 ttl=64 time=3.605 ms
64 bytes from 192.168.0.2: icmp_seq=39 ttl=64 time=3.512 ms
64 bytes from 192.168.0.2: icmp_seq=40 ttl=64 time=3.699 ms
64 bytes from 192.168.0.2: icmp_seq=41 ttl=64 time=3.527 ms
64 bytes from 192.168.0.2: icmp_seq=42 ttl=64 time=61.685 ms
64 bytes from 192.168.0.2: icmp_seq=43 ttl=64 time=1.141 ms
64 bytes from 192.168.0.2: icmp_seq=44 ttl=64 time=127.099 ms
64 bytes from 192.168.0.2: icmp_seq=45 ttl=64 time=3.433 ms
64 bytes from 192.168.0.2: icmp_seq=46 ttl=64 time=3.469 ms
64 bytes from 192.168.0.2: icmp_seq=47 ttl=64 time=3.467 ms
64 bytes from 192.168.0.2: icmp_seq=48 ttl=64 time=1.795 ms
64 bytes from 192.168.0.2: icmp_seq=49 ttl=64 time=0.871 ms
64 bytes from 192.168.0.2: icmp_seq=50 ttl=64 time=3.517 ms
64 bytes from 192.168.0.2: icmp_seq=51 ttl=64 time=8.438 ms
64 bytes from 192.168.0.2: icmp_seq=52 ttl=64 time=1.008 ms
64 bytes from 192.168.0.2: icmp_seq=53 ttl=64 time=0.848 ms
64 bytes from 192.168.0.2: icmp_seq=54 ttl=64 time=0.857 ms
64 bytes from 192.168.0.2: icmp_seq=55 ttl=64 time=3.404 ms
64 bytes from 192.168.0.2: icmp_seq=56 ttl=64 time=3.467 ms
64 bytes from 192.168.0.2: icmp_seq=57 ttl=64 time=3.333 ms
64 bytes from 192.168.0.2: icmp_seq=58 ttl=64 time=3.463 ms
64 bytes from 192.168.0.2: icmp_seq=62 ttl=64 time=0.947 ms
64 bytes from 192.168.0.2: icmp_seq=63 ttl=64 time=114.112 ms
64 bytes from 192.168.0.2: icmp_seq=64 ttl=64 time=3.233 ms
64 bytes from 192.168.0.2: icmp_seq=65 ttl=64 time=3.210 ms
64 bytes from 192.168.0.2: icmp_seq=66 ttl=64 time=3.425 ms
64 bytes from 192.168.0.2: icmp_seq=67 ttl=64 time=3.268 ms
64 bytes from 192.168.0.2: icmp_seq=68 ttl=64 time=0.862 ms
64 bytes from 192.168.0.2: icmp_seq=69 ttl=64 time=0.718 ms
64 bytes from 192.168.0.2: icmp_seq=70 ttl=64 time=13.996 ms
64 bytes from 192.168.0.2: icmp_seq=71 ttl=64 time=1.355 ms
64 bytes from 192.168.0.2: icmp_seq=72 ttl=64 time=113.726 ms
64 bytes from 192.168.0.2: icmp_seq=73 ttl=64 time=0.990 ms
64 bytes from 192.168.0.2: icmp_seq=74 ttl=64 time=1.091 ms
64 bytes from 192.168.0.2: icmp_seq=75 ttl=64 time=1.018 ms
64 bytes from 192.168.0.2: icmp_seq=76 ttl=64 time=0.987 ms
64 bytes from 192.168.0.2: icmp_seq=77 ttl=64 time=0.900 ms
64 bytes from 192.168.0.2: icmp_seq=78 ttl=64 time=1.014 ms
64 bytes from 192.168.0.2: icmp_seq=79 ttl=64 time=12.607 ms
64 bytes from 192.168.0.2: icmp_seq=80 ttl=64 time=0.999 ms
64 bytes from 192.168.0.2: icmp_seq=81 ttl=64 time=1.006 ms
64 bytes from 192.168.0.2: icmp_seq=82 ttl=64 time=1.009 ms
64 bytes from 192.168.0.2: icmp_seq=83 ttl=64 time=1.050 ms
64 bytes from 192.168.0.2: icmp_seq=84 ttl=64 time=1.078 msA

Proudarse wrote

Is this how you were pinging the RE650 or were you doing it using some other command line tool?

Your ping looks OK.

I use a tool called MTR (on Mac/Linux) or WinMTR (on Windows). Ping shows the final results (% packet loss) only after you terminate the ping. MTR shows it continuously, while it's measuring, allowing you to run it for hours or days without interruption.

With regards to the problems I experienced:
- They happened only on the 5Ghz network. (2.4Ghz is fine.)
- They require longer measurements to detect. (I don't recall exactly, as I've given up on the issue, but it would happen for 5 minutes every hour or so. You'll have to run the mtr or ping for at least two hours if you want to see if you suffer the same issue.)

Wow, I was actually doubting all the other network equipment for the packet loss so the culprit is RE650.

 

I face the same issue MacBook Pro 2018 with RE650 connected as an access point to extend my wired network to wireless. Here is the log where there is a definite ~50% packet loss for internet packets and ~15% loss while pinging the router.

 

I run the latest firmware version in RE650

 

Traceroute to google.com https://pastebin.com/3Qch3guB

Traceroute to main router https://pastebin.com/fD2vbw06