Resolving Limited Accessibility to Google Services on Specific ISP Networks (Starlink/Launtel)

Resolving Limited Accessibility to Google Services on Specific ISP Networks (Starlink/Launtel)

24 Reply
Re:Resolving Limited Accessibility to Google Services on Specific ISP Networks (Starlink/Launtel)
Friday

 I noticed a failure this morning with my network (running this beta firmware on BE63 v2) and the full system seemed to crash and reboot to re-establish connectivity with the xfinity modem. I am not sure what caused the network failure, since the logs are not long enough to show the event. I took a look at the logs and the troubling finding is that the log indicates the router reverted back to the auto-DNS provided by Xfinity, as opposed to my manual cloudflare settings. 

 

It seems there is some critical network failure, and upon reboot the manual dns settings are not appropriately applied.

  2  
  2  
#22
Options
Re:Resolving Limited Accessibility to Google Services on Specific ISP Networks (Starlink/Launtel)
Yesterday

  @Aeasy I'm also getting random system (individual but random) node crashing. I have a Deco BE65 v2 however. Attempting for a remote sessions with an Engineer is proving to be difficult, I've responded to the Engineer 3 times now and no response. 

  0  
  0  
#23
Options
Re:Resolving Limited Accessibility to Google Services on Specific ISP Networks (Starlink/Launtel)
Yesterday

  @ToneAU have you tried the beta firmware in the first post of this thread? That solved it for me for the most part it seems.

  0  
  0  
#24
Options
Re:Resolving Limited Accessibility to Google Services on Specific ISP Networks (Starlink/Launtel)
Yesterday

  @Aeasy Yes I sure have, and that has introduced other bugs. Others also have some issues too on the beta firmware, but that's in another thread.I have tried to organise a remote session with a Senior Engineer 3 times now, and no response from the engineer, or TP Link.

  1  
  1  
#25
Options