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.

You are viewing a single thread.
View all comments View context
33 points

Irrelevant, unless your pihole is running on your DHCP server. Does the server running pihole have a statically assigned IP that is within the DHCP range being assigned to other devices?

Static addresses should be outside of your DHCP range, ideally. If you can’t change the range, and assuming sequential handouts of IPs from your router among other things, you can try setting the server’s static IP to a bigger number.

permalink
report
parent
reply
21 points

Are we getting a repeat of the guy who’s wifi didn’t work because of a smart bulb?

permalink
report
parent
reply
2 points

Oh my, I didn’t catch that one but will be searching for it!

I love* solving wonky user issues. People do the darndest things.

*Subject to tolerance and patience levels of both user and self

permalink
report
parent
reply
2 points

That sounds horrible.

permalink
report
parent
reply
12 points

Wait, smart bulbs run rogue dhcp servers now?

permalink
report
parent
reply
7 points

Haha not quite. Sounds like an interesting post though. I’ll have to look that one up. From all the help given to me here though it looks like my “static” ip is within dhcp range so my router is giving everyone else my key to the castle and therefore invalidating my key.

permalink
report
parent
reply
15 points

They’re called too-smart bulbs, now.

permalink
report
parent
reply
9 points

I assume the issue was the bulb was getting assigned by DHCP the same address that was supposed to be reserved for their PC, thus their wifi appearing not to work for their PC.

permalink
report
parent
reply
11 points

Hm interesting. Basically my server is a windows computer (ya windows is not a good server OS I know, was lazy and experimenting) and in the windows network settings I assigned it a static IP that was within my DHCP range.

I wasn’t aware you could set it outside the range but this makes sense that it should be outside of the range so that my router doesn’t give my servers IP address to something else.

As you can tell I’m not super knowledgeable about networking but your help is making things make more sense. I appreciate it!

permalink
report
parent
reply
6 points

windows network settings

permalink
report
parent
reply
4 points

Haha yeah a big strong network person would be running proxmox or Ubuntu server or Debian or something and having a better time. I’m my defense, I’m both lazy and stupid so while (almost) everything is working, I’m keeping windows

permalink
report
parent
reply
6 points

That definitely sounds like you’ve found the issue, hopefully changing the IP solves it!

permalink
report
parent
reply
17 points

The static address should be assigned from the dhcp server.

Assigning a static address on the nic is a recipe for issues.

Set up a static assignment in your dhcp server.

permalink
report
parent
reply
-3 points

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

permalink
report
parent
reply
3 points

That sucks, it’s be good if you could disable DHCP overall and do it on the PiHole.

permalink
report
parent
reply
24 points

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”

permalink
report
parent
reply
6 points

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.

permalink
report
parent
reply

Selfhosted

!selfhosted@lemmy.world

Create post

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.

Rules:

  1. Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

Community stats

  • 3.4K

    Monthly active users

  • 3.3K

    Posts

  • 71K

    Comments