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.
Comment on I’m about to throw my entire Pihole out the window
whynotzoidberg@lemmy.world 8 months agoIrrelevant, 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.
ArbiterXero@lemmy.world 8 months ago
PerogiBoi@lemmy.ca 8 months 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 8 months 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.ca 8 months 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
Osirus@sh.itjust.works 8 months 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.
neoney@lemmy.neoney.dev 8 months ago
That sucks, it’s be good if you could disable DHCP overall and do it on the PiHole.
PerogiBoi@lemmy.ca 8 months ago
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!
NaibofTabr@infosec.pub 8 months ago
PerogiBoi@lemmy.ca 8 months ago
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
whynotzoidberg@lemmy.world 8 months ago
Nothing wrong with a Windows box as your server. Use what you know. Windows skills are a great asset in the world.
This issue is OS-independent, meaning you would have the same problem on a Raspberry Pi as you did on your Windows box.
GLHF
NaibofTabr@infosec.pub 8 months ago
It’s definitely more difficult when you don’t have control over the DHCP server. Is it part of a router provided by your ISP?
MangoPenguin@lemmy.blahaj.zone 8 months ago
That definitely sounds like you’ve found the issue, hopefully changing the IP solves it!
Xanthrax@lemmy.world 8 months ago
Are we getting a repeat of the guy who’s wifi didn’t work because of a smart bulb?
RajaGila@feddit.nl 8 months ago
Wait, smart bulbs run rogue dhcp servers now?
Xanthrax@lemmy.world 8 months ago
They’re called too-smart bulbs, now.
Sharpiemarker@feddit.de 8 months ago
Lol
moody@lemmings.world 8 months ago
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.
PerogiBoi@lemmy.ca 8 months ago
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.
RajaGila@feddit.nl 8 months ago
Yea, duplicate IP addresses lead to some funny business. Toss a coin to see if a network packet will arrive basically.
The solution is to adjust the DHCP range or use static DHCP on the router. The latter just means that the router will assign the same IP to the specified computer every time.
whynotzoidberg@lemmy.world 8 months ago
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
CazRaX@lemmy.world 8 months ago
That sounds horrible.