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!

  • socphoenix@midwest.social
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    2 months ago

    The only thing I see linking those devices are loosely speaking being Linux based.

    Does the local connection work? Or are you unable to ping other devices on the lan?

    I would guess it’s a switch issue assuming they can’t talk on the lan to each other.

    • Sunny' 🌻@slrpnk.netOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      2 months ago

      Not tried pinging (when it’s not working). However I’m unsure this is a problem with the switch if my wireless devices are also having the issue? Unless you mean the AP itself is being affected by this?

      • socphoenix@midwest.social
        link
        fedilink
        English
        arrow-up
        1
        ·
        2 months ago

        Whatever you are using that provides the brains of the network (like dhcp) in your setup probably the router or controller? I’ve never needed to move past an all in one but it seems like an intermittent routing issue. Have you u checked device logs to see if part of your network equipment is crashing or rebooting during these outages?