Every month or so all my devices lose internet and the only way to connect them all back is to disconnect them from the DNS server that Pihole is running.

I set my Pihole to have a static IP but for some reason after around a month or maybe longer, it just fails. This has happened 4 times over the last while and the only fix is to essentially uninstall everything on my Pihole, disable it, and then reconfigure it from scratch again.

I’m not sure what’s going on so any help would be appreciated.

  • PerogiBoi@lemmy.caOP
    link
    fedilink
    English
    arrow-up
    7
    arrow-down
    10
    ·
    1 year ago

    I’m not able to log into my router in order to edit any of my dhcp settings 😭 little caveat there.

    • ArbiterXero@lemmy.world
      link
      fedilink
      English
      arrow-up
      24
      ·
      1 year ago

      Then that’s likely your issue.

      Your router occasionally gives out the ip of your pihole to someone else, and everything shuts the bed.

      Try picking x.x.x.254 as the pihole address or x.x.x.2

      Often routers won’t use either the top end or low end of the available addresses.

      The machines on your network that are dhcp, do they go below 100? Do they go above 200?

      You’re going to be guessing a little here.

      What is your “net mask”

      • PerogiBoi@lemmy.caOP
        link
        fedilink
        English
        arrow-up
        8
        arrow-down
        1
        ·
        1 year ago

        Ya I’m pretty sure you’re correct here and this is my issue. Since I’m not able to log into my router and define my dhcp range, I’ve picked an IP near the end of the range (254).

        All my other devices are assigned .23, .25, etc.

        Fun learning experience haha

        • ArbiterXero@lemmy.world
          link
          fedilink
          English
          arrow-up
          7
          ·
          1 year ago

          Your ip-mask will tell you what IPs are accessible on the network

          Likely goes nowhere because it’s probably 255.255.255.0 but it’s possible to be something else.

          • PerogiBoi@lemmy.caOP
            link
            fedilink
            English
            arrow-up
            4
            ·
            1 year ago

            Ya it’s the 255 one. Thanks to all the help on the thread I’ve managed to set my server IP outside of the DHCP range (I think) so in theory my issue should be fixed. I’ll know in 90 days when the IP addresses are renewed.

    • Osirus@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      6
      ·
      1 year ago

      Are you on the same subnet as your router or are you on the subnet that your custom dhcp server is handing out? If your router is 192.168.1.1 and your ip is on the 192.168.2.x range, they aren’t going to be able to communicate.

          • PerogiBoi@lemmy.caOP
            link
            fedilink
            English
            arrow-up
            1
            ·
            1 year ago

            Nah http://. Tried both but none worked. Probably going to need to factory reset my router to ensure there aren’t any unlisted networks that may be the admin one. I have a sneaking suspicion my current network setup is actually on a secondary network (which could be why I can’t log into it)

            • Osirus@sh.itjust.works
              link
              fedilink
              English
              arrow-up
              1
              ·
              1 year ago

              Isolate a pc with the router and download advanced ip scanner. It will list all active ips and there should only be 2