Issues with TP link Deco m9

[yahyoh]

I bought a deco 2 days ago with 3 nodes: and it seemed wokring find and easy to setup then i had issues:
1s issue : ive tried everything to get the ipv6 to work but it wont work, it was working fine on Openwrt and on stock isp modem, ive
tried everything but no hope...its on the latest updated btw.

thats all im getting under ipv6 setting : https://i.imgur.com/mOJvgDY.png

i tried to change connection type to 6to4 and to PPPoe , tried to change all the setting under ipv6 and nothing worked so far, im already using lastes frimware update.
i even tried mac cloning and it didnt do much.

2nd issue : the ping almost 3-5 ms higher on the 3rd node which should not happen with triple-band mesh system no? ive tried to ping the the node on ip : 192.168.68.1 and i never got less than 3-5 ms which kinda high for local network.
now in games like apex legends i used to get 94-96ms ping now its almost 104-105 ms ugh.

and the most annoying thing of the main node isnt connected to internet you cant even acess the setting not even via bluetooth WTF tp link!! so if you misscounfgure something which kills your internet then you cant fix till you reset all you nodes to factory setting ugh.
i paid almost 350$ and i feel like i wasted my money.

 

[yahyoh]

I got IPv6 to work setting it to PPPoe, i think its weird as it should work as Dynamic Ip address, any way now the issue i have is the High ping after each node it gets 2-3 ms higher which shouldn't happen as the system has wifi backhaul network no?

pinging the main node/router :


Reply from 192.168.68.1: bytes=32 time=8ms TTL=64
Reply from 192.168.68.1: bytes=32 time=12ms TTL=64
Reply from 192.168.68.1: bytes=32 time=5ms TTL=64
Reply from 192.168.68.1: bytes=32 time=6ms TTL=64
Reply from 192.168.68.1: bytes=32 time=5ms TTL=64
Reply from 192.168.68.1: bytes=32 time=6ms TTL=64
Reply from 192.168.68.1: bytes=32 time=8ms TTL=64
Reply from 192.168.68.1: bytes=32 time=5ms TTL=64

 

[yahyoh]

hmmm something is up.

i tried to ping the main node while connected to it still kinda high


Pinging 192.168.68.1 with 32 bytes of data:
Reply from 192.168.68.1: bytes=32 time=4ms TTL=64
Reply from 192.168.68.1: bytes=32 time=6ms TTL=64
Reply from 192.168.68.1: bytes=32 time=4ms TTL=64
Reply from 192.168.68.1: bytes=32 time=4ms TTL=64
Reply from 192.168.68.1: bytes=32 time=44ms TTL=64
Reply from 192.168.68.1: bytes=32 time=4ms TTL=64
Reply from 192.168.68.1: bytes=32 time=1ms TTL=64
Reply from 192.168.68.1: bytes=32 time=12ms TTL=64
Reply from 192.168.68.1: bytes=32 time=4ms TTL=64
Reply from 192.168.68.1: bytes=32 time=4ms TTL=64
Reply from 192.168.68.1: bytes=32 time=3ms TTL=64
Reply from 192.168.68.1: bytes=32 time=3ms TTL=64

pinging via ethernet from the main node :

Reply from 192.168.68.1: bytes=32 time<1ms TTL=64
Reply from 192.168.68.1: bytes=32 time<1ms TTL=64
Reply from 192.168.68.1: bytes=32 time<1ms TTL=64
Reply from 192.168.68.1: bytes=32 time<1ms TTL=64



Reply from 192.168.68.1: bytes=32 time<1ms TTL=64
Reply from 192.168.68.1: bytes=32 time<1ms TTL=64
Reply from 192.168.68.1: bytes=32 time<1ms TTL=64
Reply from 192.168.68.1: bytes=32 time<1ms TTL=64
Reply from 192.168.68.1: bytes=32 time<1ms TTL=64
Reply from 192.168.68.1: bytes=32 time<1ms TTL=64
Reply from 192.168.68.1: bytes=32 time<1ms TTL=64
Reply from 192.168.68.1: bytes=32 time<1ms TTL=64

 

[Greg72]

64 is not bad. If your ISP provides IPv6, set for Passthrough. Also with a Mesh network, you may see your TTL at 64, because of how the nodes are designed to move traffic.