Update: It was DNS… its always DNS…

Hello there! I’m in a bit of a pickle… I’ve recently bought the full budget Tp-link omada stack for my homelab. I got the following devices in my stack:

  • ER605 Router
  • OC200 Controller
  • SG2008P PoE Switch
  • EAP610 Wireless AP
  • EAP625 Wireless AP (getting soon)

I’ve set it all up and it was working fine for the first few days of using it. However, last few days it’s been working very much on and off randomly(?) . Basically devices will state they are connected to WiFi/Ethernet, but they are not actually getting it. (As seen in the picture). This is happening with our phones(Pixel7+S23U) and my server(NAS:Unraid), have not noticed any problems on our desktop PCs. So it is happening on both wired and wireless, as my server and desktop PC is connected to the switch.

I haven’t done many configurations in the omada software yet, but am assuming it’s something I have done that causes this… Would greatly appreciate any advice to solve/troubleshoot this!

  • 69420@lemmy.worldEnglish
    391·
    4 months ago
    It’s not DNS.
There’s no way it’s DNS.
It was DNS.

    -SSBroski

    • 667@lemmy.radioEnglish
      6·
      4 months ago

      A buddy experienced the exact same issue as OP just the other day. We ran diagnostics and it turns out his computer was running deprecated DNS IPs for a popular ad-blocking DNS provider.

      It was DNS.

    • Sunny' 🌻@slrpnk.netOPEnglish
      5·
      3 months ago

      omg i cant believe it actually was DNS… hahahah

      I had it at default settings - but all of my devices are connected over Tailscale which uses NextDNS. Somehow when connected to the WiFi i guess things weren’t compatible…? Anyway i changed my Omada system to use NextDNS and voila! all devices connects flawlessly!