PabloAbonia
Regular Contributor
I am running native IPV6 on Time Warner, and I am running into problems of prolonged
DNS lookup times when checked with netalyzr (170ms), along with problem of upload buffer bloat times (upto 1 s on DSL Reports). While QOS will improve my downloads, nothing clearly fixes the download nothing I've done has corrected the upload latency issue regularly.
I have grown suspicious of the IPV6 DNS settings, as on Time Warner I have fe80 addresses for my gateway addresses:
IPv6 Connection Type: Native with DHCP-PD
WAN IPv6 Address: 2605:NATIVE_ADD/128
WAN IPv6 Gateway: fe80::GATEWAY <--- CAN ONLY PING ON eth0
LAN IPv6 Address: 2605:ROUTER::1/64
LAN IPv6 Link-Local Address: fe80::INTERNAL_ROUTER/64 ping on br0
DHCP-PD: Enabled
LAN IPv6 Prefix: 2605
REFIX/64
DNS Address: fe80::INTERNAL_DNS_SERVER
Traceroute to anywhere, and from any device (including the router) fails on the first hop.
Traceroute to the WAN IPV6 fe80 Address fails, however I can still ping the address
via eth0 on the router.
One >>key<< point about that pinging the fe80 WAN IPV6 address, is that it takes up to 8 ms on a CAT6 cable from the router to the modem. All the other internal devices typically ping in the <1ms range regularly.
I think the use of fe80 addresses as gateways may be responsible for some of
the delays.
Thoughts,
Pablo
DNS lookup times when checked with netalyzr (170ms), along with problem of upload buffer bloat times (upto 1 s on DSL Reports). While QOS will improve my downloads, nothing clearly fixes the download nothing I've done has corrected the upload latency issue regularly.
I have grown suspicious of the IPV6 DNS settings, as on Time Warner I have fe80 addresses for my gateway addresses:
IPv6 Connection Type: Native with DHCP-PD
WAN IPv6 Address: 2605:NATIVE_ADD/128
WAN IPv6 Gateway: fe80::GATEWAY <--- CAN ONLY PING ON eth0
LAN IPv6 Address: 2605:ROUTER::1/64
LAN IPv6 Link-Local Address: fe80::INTERNAL_ROUTER/64 ping on br0
DHCP-PD: Enabled
LAN IPv6 Prefix: 2605
REFIX/64DNS Address: fe80::INTERNAL_DNS_SERVER
Traceroute to anywhere, and from any device (including the router) fails on the first hop.
Traceroute to the WAN IPV6 fe80 Address fails, however I can still ping the address
via eth0 on the router.
One >>key<< point about that pinging the fe80 WAN IPV6 address, is that it takes up to 8 ms on a CAT6 cable from the router to the modem. All the other internal devices typically ping in the <1ms range regularly.
I think the use of fe80 addresses as gateways may be responsible for some of
the delays.
Thoughts,
Pablo
