Afternoon strangers,
I had to take my Asus router out of the mix so they could see a strange issue that was stopping the router getting the correct IPv6 prefix (/64 but should be /48). Previously router was asking the exchange for a internal 100.x.y.z allocation so the ISP patched a fix in order to give me a proper external IP allocation (86.x.y.z).
The IPv4 issue and fix may have caused the previous IPv6 connection issue but the ISP isn't confirming this either way.
I've used the RT-N66U and RT AC68U with @RMerlin firmware beforehand with stability issues.
Should I do the nuclear reset recommended by @L&LD before reemploying the router or is there something more serious?
The router discussed above is a Asus RT AC86U with AsussWRT-Merlin 384.19 flashed. WiFi mesh supplied a number of Plume SuperPods.
Regards, K.
I had to take my Asus router out of the mix so they could see a strange issue that was stopping the router getting the correct IPv6 prefix (/64 but should be /48). Previously router was asking the exchange for a internal 100.x.y.z allocation so the ISP patched a fix in order to give me a proper external IP allocation (86.x.y.z).
The IPv4 issue and fix may have caused the previous IPv6 connection issue but the ISP isn't confirming this either way.
I've used the RT-N66U and RT AC68U with @RMerlin firmware beforehand with stability issues.
Should I do the nuclear reset recommended by @L&LD before reemploying the router or is there something more serious?
The router discussed above is a Asus RT AC86U with AsussWRT-Merlin 384.19 flashed. WiFi mesh supplied a number of Plume SuperPods.
Regards, K.