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!

  • tofubl@discuss.tchncs.de
    link
    fedilink
    English
    arrow-up
    1
    ·
    4 months ago

    Had similar behaviour last night. Turned out UnboundDNS had crashed in my opnsense firewall and took “internet connectivity” with it. Restarting the service fixed it in one click after I found it.

    • tofubl@discuss.tchncs.de
      link
      fedilink
      English
      arrow-up
      0
      ·
      edit-2
      4 months ago

      Terrible opsec sharing your WiFi SSID, by the way. I can’t find one right now, but I’ve seen global “wardriving” maps of all broadcast WiFi SSIDs that allow to pinpoint a somewhat unique SSID or at least narrow down to a few options. A list of SSIDs around you pretty much gives away your precise location.