101010.pl is one of the many independent Mastodon servers you can use to participate in the fediverse.
101010.pl czyli najstarszy polski serwer Mastodon. Posiadamy wpisy do 2048 znaków.

Server stats:

519
active users

#dhcp

0 posts0 participants0 posts today

Jakiś czas temu (5d? 7d? jakoś tak) zmieniłem lokalizację - w sensie przeniosłem na inny serwer. Co za tym idzie, zmienił się IP. Co za tym idzie, nauczyłem grzecznie że ma rozsyłać nowy serwer , a jako że lease time mam ustawiony na dobę, to dzień później nic już nie powinno pytać starego serwera, prawda? PRAWDA?

No. 3 sprzęty miały mnie w dupie. 2x (tuner, głośnik) i odkurzacz. Ale dzisiaj przyszła kryska na matyska, upierdoliłem im wszystkim prund. I okazało się że jednak umieją z DeHaCePem pogadać i dostać nowy adres serwera DNS...

I don’t usually rant, but this deserves one. I upgraded my BOG STANDARD Pi-hole from version 5.x to 6.x, and IT BROKE EVERYTHING. DNS stopped working, the DHCP settings page lost its static lease section (and no button to add them), and the new web interface crawled like molasses on my Raspberry Pi 3. My setup wasn’t customized – everything was configured through the web interface.

Fail guys..fail

#linux#pihole#dhcp

So I recently used a #sledgehammer where a #scalpel was needed.

I've got an #HP DL80 Gen9 with the iLO license, but without the #FlexibleLOM card... so to access the iLO I have to have an ethernet cable plugged into the first ethernet port.

Problem is, no matter what I tried in #Webmin or #NetworkManager, every reboot would re-enable that port... which would then get a IP via DHCP (even when I'd disabled it in nm...), which would mean #Zabbix would pick it up as a client and add it.. meaning every time a disk got a little "backed up", I'd get two alerts, and this machine has 12 very old SATA drives in it.

Tired of messing with the damned thing, I finally got out the sledgehammer....
....and blacklisted HP's #OUI from the #DHCP server.

No IP, no extra client created in Zabbix, and only the normally-annoying amount of alerts.

I'll #fsck with it for real, later...

I finally shut down my last remaining Windows 2003 R2 server that was serving as my DHCP and primary DNS server (the secondary DNS server, also Win 2K3 R2, was shut down a few weeks ago).

Goodbye old friend. You were flawless for many years. I've moved onto Kea.

#windows#dhcp#dns
Replied in thread

As I was writing that last post, I might actually write code to load a table with IP records and then layer data on top of that. That table will be populated when a network is created and, if the gateway is included, that IP will be reserved right away. I'm going to need that data anyways, so I might as well have a way to manage it.

For a given IP and subnet mask, I'll be able to know all the usable IPs thanks to functions from the ip_network python library I'm using. It will be easy to add/remove the IP data when the network is created, destroyed, or the gateway is changed. Oh look, I just wrote some code for that - making this change easier.

Devices in the inventory will be able to claim 0..n IP addresses and I could even have it claim a static IP (outside any DHCP range) or association with a given DHCP range.

This has an additional benefit of being able to calculate DHCP range utilization. If a DHCP range has 10 IPs and 5 devices associated with it, it's 50% used.