view the rest of the comments
Selfhosted
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:
-
Be civil.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
Good points there.
For 1. The ISP router is a Fritz one set to bridge mode running over a PoE adapter from the same UPS the firewall is using. It stayed up all the time (looking back at the logs)
Not sure what happened here, but the firewall is the DNS resolver and when everything else powered back up, nothing got an IP address. Now, whether thw service failed or the WAPs took longer to start than the devices could wait, I'm not sure, but as Scotty said: it's dead Jim.
Good point. I don't need it ALL to be redundant.
Also good. The UPS is directly connected to the firewall (which has NUT in), but it doesn't inform anything else... I'll look into that too.
Nice mental reset for me about over thinking it... thanks
My hunch here is that you MIGHT be using a named host as your DNS resolves instead of an IP address in your network, OR, for some reason your DNS resolves doesn't have a static address. Never use named hosts to point to network services, and all network services need a static IP, so go and check all of that.
Yep, all good with DHCP vs DNS.. just my grammer was terrible.
Nothing was getting an IP from the DHCP, when the wifi returned...and... DNS was also not working for the few devices that still had an IP.
Sry bout the confusion there.
So then as a next step, I'd set Wireshark up on one of your regularly hosts, set it to filter for DHCP traffic, confirm you're seeing regularly advertisements first, then reboot the device that's responsible for DHCP and make sure it resumes sending those advertisements when it comes back.
If it's the same device handling DNS, make sure it's also immediately returning responses after the reboot as well with
digornslookup.Wireshark*
Oops, yup